Deploying Projects from Vercel CLI

The vercel command is used to deploy Vercel Projects and can be used from either the root of the Vercel Project directory or by providing a path.

vercel

You can alternatively use the vercel deploy command for the same effect, if you want to be more explicit.

vercel [path-to-project]

When deploying, stdout is always the Deployment URL.

vercel > deployment-url.txt

• deploy

By default, when you promote a deployment to production, your domain will point to that deployment. If you want to create a production deployment without assigning it to your domain, for example to avoid sending all of your traffic to it, you can:

1. Turn off the auto-assignment of domains for the current production deployment:

vercel --prod --skip-domain

2. When you are ready, manually promote the staged deployment to production:

vercel promote [deployment-id or url]

• promote
• deploy

To deploy a locally built Next.js app or another Vercel project, run vercel build followed by vercel deploy --prebuilt. You can build on your computer or in your own CI environment, inspect the output, and upload the build artifacts to Vercel without a remote build of your source code.

First, run vercel pull to download the project's settings and environment variables, then build:

vercel pull --environment=preview
vercel build

This produces .vercel/output in the Build Output API format. You can review the output, then deploy with:

vercel deploy --prebuilt

See more details at Build Output API.

• build
• deploy