Current documented limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| Hobby function memoryThis is the documented function allocation for the Hobby plan. | 2 GB and 1 vCPU | Hobby | VercelSep 17, 2026 |
| Function maximum durationDefault and maximum are both 300 seconds in the documented Fluid compute table. | 300 seconds | Hobby; Node.js/Python with Fluid compute | VercelSep 17, 2026 |
| Function maximum durationGenerally available maximum; the default stays 300 seconds and maxDuration must be raised per function. | 800 seconds | Pro and Enterprise | VercelSep 17, 2026 |
| Function extended maximum duration (Beta)Beta; values above 800 seconds need function-level configuration and are not supported with Secure Compute or Static IPs during the beta. | 1,800 seconds (30 minutes) | Pro and Enterprise | VercelSep 17, 2026 |
| Function request or response bodyPayloads over the documented limit return FUNCTION_PAYLOAD_TOO_LARGE with status 413. | 4.5 MB | Vercel Function request and response | VercelSep 17, 2026 |
| Function memoryDocumented default and maximum for Vercel Functions. | 2 GB / 1 vCPU | Hobby | VercelSep 17, 2026 |
How to apply Vercel limits safely
The monitored baseline covers Hobby function memory, Function maximum duration, Function extended maximum duration (Beta), Function request or response body, Function memory. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.
- Match the production workload to the exact scope printed beside each value and confirm it in the active Vercel console, configuration, or response headers.
- Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
- Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.
Specific limit pages
These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.
Vercel Function Memory Limit
Vercel Function Memory Limit, verified against Vercel's official documentation with scope, implementation impact, caveats, and a direct check.
Vercel function duration
Current Vercel Function maximum durations, Fluid compute requirements, runtime caveats, configuration, and timeout error linkage.
Vercel payload limit
The current Vercel Function request and response body limit, failure behavior, and safer large-file architecture.
Errors linked to these limits
Compare alternatives
Vercel vs Netlify Function Limits
Vercel vs Netlify Function Limits using the same verified structured observations as each underlying limit page, with scope and comparability caveats.
Google Cloud Run vs Vercel Limits
Google Cloud Run vs Vercel Limits using the same verified structured observations as each underlying limit page, with scope and comparability caveats.
AWS API Gateway vs Vercel Payload & Timeout Limits
AWS API Gateway vs Vercel Payload & Timeout Limits using the same verified structured observations as each underlying limit page, with scope and comparability caveats.
Vercel vs Cloudflare Workers
Compare current function duration, CPU, memory, and payload constraints without treating unlike execution models as identical.
Vercel vs AWS Lambda
Compare current execution duration and payload constraints across Vercel Functions and AWS Lambda by invocation mode.