Getting Started
Learn how to use bulk redirects to manage thousands of redirects that do not require wildcard or header matching functionality.
- Create a redirect file in one of the supported formats (CSV, JSON, or JSONL)
- Configure the property in your file
- Deploy your project
You can create fixed files of redirects, or generate them at build time as long as they end up in the location specified by
bulkRedirectsPathbefore the build completes.Add the property to your file, pointing to your redirect file. You can also point to a folder containing multiple redirect files if needed.
Deploy your project to Vercel. Your bulk redirects will be processed and applied automatically.
Any errors processing the bulk redirects will appear in the build logs for the deployment.
Each redirect supports the following fields:
| Field | Type | Required | Description |
|---|---|---|---|
| Yes | An absolute path that matches each incoming pathname (excluding querystring). Max 2048 characters. | ||
| Yes | A location destination defined as an absolute pathname or external URL. Max 2048 characters. | ||
| No | Toggle between permanent (308) and temporary (307) redirect. Default: . | ||
| No | Specify the exact status code. Can be 301, 302, 303, 307, or 308. Overrides permanent when set, otherwise defers to permanent value or default. | ||
| No | Toggle whether source path matching is case sensitive. Default: . | ||
| No | Toggle whether to preserve the query string on the redirect. Default: . |
In order to improve space efficiency, all boolean values can be the single characters (true) or (false) while using the CSV format.
For complete configuration details and advanced options, see the configuration reference.
Was this helpful?