Quick answer
Vercel documents hobby function memory as 2 GB and 1 vCPU. This is the documented function allocation for the Hobby plan.
Verified Aug 22, 2026Official source
Current 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 | VercelAug 22, 2026 |
Why does this limit matter?
Large in-memory transforms can fail before the function's duration or payload ceiling.
This value is scoped to Hobby; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Inspect the deployed plan and function metrics for memory peaks and out-of-memory termination.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Plan, runtime, and Fluid compute settings affect available resources.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related