4 min read

Understand how the build step works when creating a Vercel Deployment.

Table of Contents

When you create a new project or push a new commit to a project on Vercel, you initiate a deployment. A deployment is made up of a few steps:

This guide is focused on the build step, where Vercel validates and builds your source code, outputting all assets into storage.

For any of the supported frameworks, Vercel will automatically configure the build settings with the most common configurations for the framework. If you have specific settings, you can configure the build, output, and environment variables when you create a new Vercel project or within your project's settings.

If your project does not require building, for example, a website with only static source files, you can choose to skip the build step.

You can initiate a Vercel deployment in two ways: with Vercel CLI or by pushing changes to a connected Git repository on GitHub, GitLab, or Bitbucket. It's also possible for deployments to be initiated through an integration using Vercel REST API.

Depending on how you initiate the build, Vercel may put it in a queue to ensure we build things in the right order and only build the most recent deployment.

A deployment from CLI triggers a build in the build container which provisions resources and updates the deployment's status

  1. Once you trigger a deployment, the build container will receive a request that there is a job available. The build container is a Docker container that uses an Amazon Linux based image and includes some pre-installed packages. The build container runs in a few regions on our Edge Network⁠—you can determine which one by viewing your build logs.

  2. Vercel first authenticates and inspects the request to confirm its authenticity and your permission to create the deployment to protect against unauthorized access and loss of integrity. At this point, Vercel also validates the Vercel configuration in the vercel.json file.

  3. Depending on whether your plan allows for concurrent builds, Vercel may queue your build until other builds from your team have been completed.

  4. If you use Git to initiate your deployment, Vercel performs a shallow clone on your Git repository to fetch the most recent Git commit history. CLI deployments won't do this step—they'll follow the flow in the next step.

  5. If you use Vercel CLI to initiate your deployment, the following flow will happen. Git deployments won't go through this flow:

    • A POST request is made containing the project’s files to be uploaded (without these ignored files) to a scalable, secure, and highly durable data storage service
    • Once the source files have been uploaded, another POST request is made to start the build and deployment process.
  6. Vercel will check for an existing build cache key. If it finds one, it will restore the previous build cache. For more information on the build cache, see the "Caching process" docs.

  7. Now that the build container has your source files, it installs any necessary tools and then will do the actual build by running the build command.

    During this phase, the build step transforms the project into a Vercel deployment by executing a builder (or multiple builders, depending on the frameworks) on the source code. The builder can be an internal one provided by Vercel (for example, Next.js builder) or a custom builder that requires installation from an npm registry. If this npm registry is private, see "Private npm packages".

  8. Concurrently, while the build container processes the file, it pings an API endpoint that keeps track of the deployment’s status. Vercel will then use this endpoint to update you on the dashboard, in the CLI, or in your pull request about the live status of the build.

  9. The build container creates a build output that runs on one of Vercel's supported runtimes and provisions resources such as:

    You can check the detailed output from your build on the deployment summary.

  10. Finally, once the resources have been created and provisioned, Vercel uploads them to a dedicated static storage, along with metadata that is used to route the user to the correct location on the network. To learn more about what happens when a user requests these resources, see "Behind the scenes of Vercel's infrastructure - Request phase".

The maximum duration of the build is 45 minutes. When the limit is reached, the build will be interrupted and the deployment will fail. For more information, see "Cancelled Builds due to limits".

The build container is created with a specific amount of resources that cannot be increased.

Each build's cache can be a maximum of 1 GB and applies at the level of each build cache key. The build cache is retained for one month and currently you cannot configure which files are cached.

This section details our improved infrastructure pricing. On April 25, 2024, these changes will apply to all new Pro customers. Starting May 25, 2024, current Pro customers will see these changes take effect on their next billing cycle. The Hobby tier remains free.

Manage and Optimize pricing
Build TimeThe amount of time your Deployments have spent being queued or buildingAdditional concurrent buildsLearn More
Number of BuildsHow many times a build was issued for one of your DeploymentsNoN/A
Last updated on June 21, 2024