Promoting a preview deployment to production
Use this guide to verify a preview deployment and promote it to production. You'll find the right deployment, test it, and promote it to serve production traffic.
Use this block when you already know what you're doing and want the full command sequence. Use the steps below for context and checks.
# 1. Find preview deployments
vercel list --status READY
# 2. Inspect the target deployment
vercel inspect <deployment-url>
# 3. Test the preview deployment
vercel curl /api/health --deployment <deployment-url>
vercel httpstat / --deployment <deployment-url>
# 4. Check for errors
vercel logs --deployment <deployment-url> --query 'level:error' --limit 50
# 5. Promote to production (--yes skips confirmation prompt)
vercel promote <deployment-url> --yes
vercel list --environment production
# 6. Verify production
vercel logs --environment production --query 'level:error' --since 5m
vercel httpstat /List recent deployments that have finished building and are ready to serve traffic:
vercel list --status READYThis shows all READY deployments with their age, URL, environment, build duration, and creator. Find the preview deployment you want to promote.
To filter by a specific environment:
vercel list --environment previewConfirm that the deployment built successfully and check its metadata:
vercel inspect <deployment-url>This shows the deployment ID, target environment, status, URL, creation time, and build duration. Verify that it is the deployment you expect to promote.
To check the build logs for any warnings:
vercel inspect <deployment-url> --logsUse vercel curl to send requests to the preview deployment. This automatically handles deployment protection, so you can test protected preview deployments:
vercel curl /api/health --deployment <deployment-url>Check the response status and body. For critical routes, test multiple endpoints:
vercel curl / --deployment <deployment-url>
vercel curl /api/users --deployment <deployment-url>To check response timing and verify there are no performance regressions:
vercel httpstat / --deployment <deployment-url>Review the deployment's logs for any errors that occurred during testing or from other traffic:
vercel logs --deployment <deployment-url> --query 'level:error' --limit 50The vercel logs command prints full error messages and stack traces by default.
If the output is clean, the deployment is safe to promote.
Promote the preview deployment to production. This triggers a new production build using the same source code:
vercel promote <deployment-url>For non-interactive environments (CI/CD or automation), add --yes to skip the confirmation prompt:
vercel promote <deployment-url> --yesCheck the status of the new production deployment:
vercel list --environment productionThe new production deployment is the first row in the list. Wait until its status is Ready.
When you promote a preview deployment, the CLI creates the new production deployment and exits. It does not wait for the build to complete. The --timeout option applies only when you promote a deployment that was built for the production environment. In that case, the CLI waits up to three minutes by default for the promotion to complete. To change the timeout:
vercel promote <deployment-url> --timeout 5mAfter the promotion completes, confirm that production is serving traffic correctly:
vercel logs --environment production --query 'level:error' --since 5mCheck that the production domain responds with the expected content:
vercel httpstat /If you discover a problem after promoting, roll back by pointing production at a previous deployment:
vercel rollback <previous-deployment-url-or-id>This restores the deployment you specify. See Rolling back a production deployment for a full recovery workflow.
Was this helpful?