This page outlines all relevant limits and limitations present when using the ZEIT Now platform.
This section highlights two areas relating to pricing plans, Usage Allowances, and Plan Limits.
Usage Allowances are the maximum limits provided by each pricing plan. They specify a limit for the amount of resources available for use under that plan before deployments are blocked (Free plan) or additional costs are incurred.
Build Time (Hours)
Execution Time (Hours)
Plan Limits are limitations that apply to specific plans that cannot be increased, the only way to do so is to upgrade to a higher tier pricing plan.
Deployments (per day)
Execution Duration (Seconds)
Both log types – build time and runtime – are stored for 20 days only. It is not possible to retrieve either of these log types beyond the age of 20 days.
For Serverless Functions, each log output is limited to 4kb. For log outputs greater than 4kb, only the last 4kb will be retained.
The total size of environment variables is limited to 4kb.
The maximum amount of domains that can be applied to a single project, either from the ZEIT Dashboard or by using the
alias key in a
now.json file is 50.
It is not possible to add more than 50 domains to a project using the ZEIT Dashboard.
The maximum number of files that can be uploaded when making a deployment is 10,000.
Deployments made that contain more than 10,000 files will fail at the build step.
The ZEIT Now platform does not currently support HTTP/2 Push.
For security reasons, the ZEIT Now platform blocks outgoing SMTP connections.
As a result of this, we recommend using a third-party service to enable email functionality for deployments.
The maximum number of concurrent executions for a Serverless Function is
If you require a limit above
1000, you should contact our enterprise department to discuss custom limits available on an enterprise plan.
When attempting to deploy Serverless Functions to multiple regions on the Free plan, the deployment will fail before entering the build step.
ZEIT Now does not support streaming responses from Serverless Functions due to an upstream limitation from AWS.
The following environment variable names are reserved and therefore unavailable for use:
Rate limits are hard limits that apply to the platform when performing actions that require a response from an 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 account owner,
userrefers to an individual user on a Team account.
Below are three examples that provide further information on how the rate limits work.
Taking the domains deletion rate limit as an example, you are allowed 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 deleting another domain.
With the team deletion rate limit, 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 deleting another team.
For the username update rate limit, 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 changing your username again.