Verified history
Eligible Vercel Functions increased to 30 minutes
Vercel announced a beta 1,800-second maximum for Pro and Enterprise Node.js and Python Functions using Fluid compute and maxDuration opt-in.
Long I/O-heavy functions can exceed the previous documented 800-second ceiling when all eligibility requirements are met.
Current monitored baseline
HyperObserve currently monitors 5 scoped observations for Vercel. The baseline covers Hobby function memory, Function maximum duration, Function request or response body, Function memory. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| Hobby function memoryThis is the documented function allocation for the Hobby plan. | 2 GB and 1 vCPU | Hobby | VercelAug 22, 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 | VercelAug 22, 2026 |
| Function maximum durationBeta above 800 seconds, requires Fluid compute, and requires maxDuration opt-in. | 1,800 seconds (30 minutes) | Pro and Enterprise | VercelAug 22, 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 | VercelAug 22, 2026 |
| Function memoryDocumented default and maximum for Vercel Functions. | 2 GB / 1 vCPU | Hobby | VercelAug 22, 2026 |
Tracked constraints and impact
Function duration, payload, memory, runtime, and plan constraints. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
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.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current Vercel baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Max duration, memory, request body, and file descriptors
Node.js and Python duration announcement