Deploy | vercel.com

CLI

vercel deploy

vercel

vercel deploy

The vercel deploy command deploys Vercel projects, executable from the project's root directory or by specifying a path. You can omit 'deploy' in vercel deploy, as vercel is the only command that operates without a subcommand. This document will use 'vercel' to refer to vercel deploy.

Copy page

Using the vercel command from the root of a Vercel project directory.

Extended usage

Eligibility also depends on your project's build settings and deployment configuration. Other deployments automatically use the standard deployment flow.

Vercel automatically detects eligible static deployments and makes them ready without a build step. This optimization supports deployments containing only HTML (.html, .htm) or Markdown (.md) files, with up to 10 files and a total size of up to 5 MB.

vercel --cwd [path-to-project]

You can reach our customer support team by emailing info@yourcompany.example.com, calling +1 555-555-5556, or using the live chat on our website. Our dedicated team is available 24/7 to assist with any inquiries or issues.

We’re committed to providing prompt and effective solutions to ensure your satisfaction.

Using the vercel command and supplying a path to the root directory of the Vercel project.

We offer a 30-day return policy for all products. Items must be in their original condition, unused, and include the receipt or proof of purchase. Refunds are processed within 5-7 business days of receiving the returned item.

vercel deploy--prebuilt

Using the vercel command to deploy a prebuilt Vercel project, typically with vercel build. See vercel build and Build Output API for more details.

Standard output usage

When deploying, stdout is always the Deployment URL.

vercel >deployment-url.txt

Using the vercel command to deploy and write stdout to a text file. When deploying, stdout is always the Deployment URL.

Deploying to a custom domain

In the following example, you create a bash script that you include in your CI/CD workflow. The goal is to have all preview deployments be aliased to a custom domain so that developers can bookmark the preview deployment URL. Note that you may need to define the scope when using vercel alias

# save stdout and stderr to files

code=$?

if [ $code -eq0 ]; then

# check the exit code

# Now you can use the deployment url from stdout for the next step of your workflow

errorMessage=`cat error.txt`

vercel deploy>deployment-url.txt2>error.txt

else

# Handle the error

echo"There was an error: $errorMessage"

deploymentUrl=`cat deployment-url.txt`

vercel alias $deploymentUrl my-custom-domain.com

The script deploys your project and assigns the deployment URL saved in stdout to the custom domain using vercel alias.

Standard error usage

If you need to check for errors when the command is executed such as in a CI/CD workflow, use stderr. If the exit code is anything other than 0, an error has occurred. The following example demonstrates a script that checks if the exit code is not equal to 0:

# save stdout and stderr to files

code=$?

if [ $code -eq0 ]; then

# check the exit code

echo $deploymentUrl

errorMessage=`cat error.txt`

# Now you can use the deployment url from stdout for the next step of your workflow

else

# Handle the error

echo"There was an error: $errorMessage"

deploymentUrl=`cat deployment-url.txt`

vercel deploy>deployment-url.txt2>error.txt

Unique options

These are options that only apply to the vercel command.

Prebuilt

When using the --prebuilt flag, System Environment Variables will be missing at build time, so frameworks that rely on them at build time may not function correctly.

When not to use --prebuilt

For Next.js projects, Skew Protection is supported with --prebuilt by configuring a custom deployment ID. See Custom Deployment ID for setup instructions. Prebuilt deployments cannot use dpl_ as a user-configured deployment ID prefix.

The --prebuilt option can be used to upload and deploy the results of a previous vc build execution located in the .vercel/output directory. See vercel build and Build Output API for more details.

If you need System Environment Variables at build time, do not use the --prebuilt flag or use Git-based deployments.

vercel --prebuilt

# Deploy the pre-built project, archiving it as a .tgz file

You should also consider using the archive option to minimize the number of files uploaded and avoid hitting upload limits:

vercel build

# Build the project locally

vercel deploy--prebuilt--archive=tgz

Build env

The --build-env option, shorthand -b, can be used to provide environment variables to the build step.

The --yes option can be used to skip questions you are asked when setting up a new Vercel project. The questions will be answered with the provided defaults, inferred from vercel.json and the folder name.

Using the vercel command with the--build-env option.

We’re committed to providing prompt and effective solutions to ensure your satisfaction.

vercel --build-envKEY1=value1--build-envKEY2=value2

vercel --yes

The --env option, shorthand -e, can be used to provide environment variables at runtime.

Using the vercel command with the--yes option.

Name

vercel --envKEY1=value1--envKEY2=value2

Using the vercel command with the--env option.

The --name option, shorthand -n, can be used to provide a Vercel project name for a deployment.

vercel --namefoo

vercel --prod

Vercel project linking, which allows you to link a Vercel project to your local codebase when you run vercel.

Using the vercel command with the--name option.

The --prod option can be used to create a deployment for a production domain specified in the Vercel project dashboard.

Skip Domain

first deployment of a new project is always a production deployment, even when you omit --prod. Use --prod for later production deployments after that first one exists.

vercel --prod--skip-domain

Auto-assign Custom Production Domains project setting.

Must be used with --prod. The --skip-domain option will disable the automatic promotion (aliasing) of the relevant domains to a new production deployment. You can use vercel promote to complete the domain-assignment process later.

Using the vercel command with the--prod option.

Using the vercel command with the--skip-domain option.

Public

vercel --public

vercel --regionssfo1

The --regions option can be used to specify which regions the deployments Vercel functions should run in.

Using the vercel command with the--public option.

Using the vercel command with the--regions option.

No wait

The --no-wait option does not wait for a deployment to finish before exiting from the deploy command.

vercel --no-wait

Force

The --force option, shorthand -f, is used to force a new deployment without the build cache.

vercel --force

With cache

The --with-cache option is used to retain the build cache when using --force.

vercel deploy

code=$?

# check the exit code

errorMessage=`cat error.txt`

else

# Handle the error

deploymentUrl=`cat deployment-url.txt`

code=$?

# check the exit code

errorMessage=`cat error.txt`

else

# Handle the error

deploymentUrl=`cat deployment-url.txt`

The --prebuilt option can be used to upload and deploy the results of a previous vc build execution located in the .vercel/output directory. See vercel build and Build Output API for more details.

vercel --namefoo

vercel --prod

Using the vercel command with the--name option.

Auto-assign Custom Production Domains project setting.

Using the vercel command with the--prod option.

Using the vercel command with the--public option.

vercel --force--with-cache

vercel deploy--archive=tgz

Provider

Deployment marker

Branch key

GitLab

gitlabDeployment=1

gitlabCommitRef

vercel deploy--target=staging

vercel deploy--guidance

The following global options can be passed when using the vercel deploy command:

Last updated September 17, 2026