- General Limits
- Included usage
- Additional resources
- Pro trial limits
- Routes Created per Deployment
- Build Time per Deployment
- Build container resources
- Build cache maximum size
- Environment Variables
- Proxied Request Timeout
- Web Analytics
- Speed Insights
- Cron Jobs
- Vercel Functions
- Connecting a Project to a Git Repository
- Reserved Variables
- Rate Limits
- Rate Limit Examples
To prevent abuse of our platform, we apply the following limits to all accounts.
Deployments Created per Day
Serverless Functions Created per Deployment
Proxied Request Timeout (Seconds)
Deployments Created from CLI per Week
Team Members per Team
Build Time per Deployment(Minutes)
Disk Size (GB)
Serverless Function Execution
Edge Function Execution Units
Edge Middleware Invocations
For Teams on the Pro plan, you can pay for additional usage as you go.
For members of our Pro plan, we offer a pay-as-you-go model for additional usage, giving you greater flexibility and control over your usage. The typical monthly usage guidelines above are still applicable, while extra usage will be automatically charged at the following rates:
$40 per 100 GB increment
Serverless Function Execution
$40 per 100 GB-Hrs increment
$2.00 per 1,000,000 increment
$0.65 per 1,000,000 increment
$5 per 1000 increment
$0.50 per incremental GB
$9.00 per 1 million data points
$0.65 per 10,000 data points
$14.00 per 100,000 additional events
Edge Config (Read, Write)
$3.00 per additional 1 million reads
$5.00 per additional 500 writes
Vercel KV (Databases, Requests, Storage, Data transfer)
$1.00 per additional database or read replica
$0.35 per 100,000 additional requests
$0.25 per additional GB
$0.10 per additional GB
See the Pro trial limitations section for information on the limits that apply to Pro trials.
The limit of "Routes created per Deployment" encapsulates several options that can be configured on Vercel:
- If you are using a
vercel.jsonconfiguration file, each rewrite, redirect, or header is counted as a Route
- If you are using the Build Output API, you might configure routes for your deployments
Note that most frameworks will create Routes automatically for you. For example, Next.js will create a set of Routes corresponding to your use of dynamic routes, redirects, rewrites and custom headers.
The maximum duration of the Build Step is 45 minutes. When the limit is reached, the Build Step will be interrupted and the Deployment will fail.
Every Build is provided with the following resources:
This cannot be increased. For more information on troubleshooting these, see Build container resources.
The maximum size of the Build's cache is 1 GB. It is retained for one month and it applies at the level of each Build cache key.
There are two types of logs: build logs and runtime logs. Both have different behaviors when storing logs.
Build logs are stored indefinitely for each deployment.
The total size of your Environment Variables, names and values, is limited to 64KB for projects using Node.js, Python, Ruby, Go, Java, and .NET runtimes. This limit is the total allowed for each deployment, and is also the maximum size of any single Environment Variable. For more information, see the Environment Variables documentation.
If you are using System Environment Variables, the framework-specific ones (i.e. those prefixed by the framework name) are exposed only during the Build Step, but not at runtime. However, the non-framework-specific ones are exposed at runtime. Only the Environment Variables that are exposed at runtime are counted towards the size limit.
Domains per Project
Although there is no upper limit for output files created during a build, you can expect longer build times as a result of having many thousands of output files (100,000 or more, for example). If the build time exceeds 45 minutes then the build will fail.
We recommend using Incremental Static Regeneration (ISR) to help reduce build time. Using ISR will allow you pre-render a subset of the total number of pages at build time, giving you faster builds and the ability to generate pages on-demand.
The amount of time (in seconds) that a proxied request (
routes with an external destination) is allowed to process an HTTP request. The maximum timeout is 30 seconds.
If the external server does not reply until the maximum timeout is reached, an error with the message
ROUTER_EXTERNAL_TARGET_ERROR will be returned.
Check out the Limits and Pricing section for more details about the limits of Vercel Web Analytics.
Check out the Limits and Pricing doc for more details about the limits of the Speed Insights feature on Vercel.
Check out the Cron Jobs limits section for more information about the limits of Cron Jobs on Vercel.
The limits of Vercel functions are based on the runtime that you use.
Vercel does not support connecting your Personal Account's Projects to Git repositories owned by Git organizations. You can either switch to an existing Team or create a new one.
The same limitation applies in the Project creation flow when importing an existing Git repository or when cloning a Vercel template to a new Git repository as part of your Git organization.
See the Reserved Environment Variables docs for more information.
Rate limits are hard limits that apply to the platform when performing actions that require a response from our API.
The rate limits table consists of the following four columns:
- Description - A brief summary of the limit which, where relevant, will advise what type of plan it applies to.
- Limit - The amount of actions permitted within the amount of time (Duration) specified.
- Duration - The amount of time (seconds) in which you can perform the specified amount of actions. Once a rate limit is hit, it will be reset after the Duration has expired.
- Scope - Who the limit applies to:
ownerrefers to the Personal Account Owner or Team Owner,
userrefers to a Team Member.
Below are five examples that provide further information on how rate limits work.
You are able to delete up to
60 domains every
60 seconds (1 minute). Should you hit the rate limit, you will need to wait another minute before you can delete another domain.
You are able to delete up to
20 teams every
3600 seconds (1 hour). Should you hit the rate limit, you will need to wait another hour before you can delete another team.
You are able to change your username up to
6 times every
604800 seconds (1 week). Should you hit the rate limit, you will need to wait another week before you can change your username again.
You are able to build
32 Deployments every
3600 seconds (1 hour). Should you hit the rate limit, you will need to wait another hour before you can build a deployment again.
You are able to deploy
100 times every
86400 seconds (1 day). Should you hit the rate limit, you will need to wait another day before you can deploy again.