Reference
1 min read
Vercel Functions Limitations
Learn about the limitations and restrictions of using Vercel Functions for both Node.js and Edge runtimes.Table of Contents
The limitations on a function are dependant on the runtime you choose. See the Choosing a Runtime doc for information on all the limitations of each runtime.
Some common limits you may wish you be aware of:
| Limit | Node.js | Edge |
|---|---|---|
| Maximum memory | Hobby: 1024 MB, Pro and Ent: 3009 MB | 128 MB |
| Maximum duration | Hobby: 10s (default) - configurable up to 60s, Pro: 15s (default) - configurable up to 300s, Ent: 15s (default) - configurable up to 900s | 25s (to begin returning a response, but can continue streaming data.) |
| Size (after gzip compression) | 250 MB | Hobby: 1 MB, Pro: 2 MB, Ent: 4 MB |
| Concurrency | Auto-scales up to 30,000 (Hobby and Pro) or 100,000+ (Enterprise) concurrency | Unlimited concurrency |
| Cost | Pay for wall-clock time | Pay for CPU time |
| Regions | Executes region-first, can customize location. Enterprise teams can set multiple regions | Executes global-first, can specify a region |
| API Coverage | Full Node.js coverage | Limited API support |
The following limits apply to the function's name when using Node.js runtime:
- Maximum length of 128 characters. This includes the extension of the file (e.g.
apps/admin/api/my-function.jsis 29 characters) - No spaces are allowed. Replace them with a
-or_(e.g.api/my function.jsisn't allowed)
Last updated on May 10, 2024
Was this helpful?