Platform hub

Vercel limits

Function duration, payload, memory, runtime, and plan constraints. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  Vercel has multiple independent constraints. Match the exact plan, model, runtime, invocation mode, or server configuration shown in each row.

Current documented limits

ConstraintCurrent valueScopeVerified source
Hobby function memoryThis is the documented function allocation for the Hobby plan.2 GB and 1 vCPUHobbyVercelAug 22, 2026
Function maximum durationDefault and maximum are both 300 seconds in the documented Fluid compute table.300 secondsHobby; Node.js/Python with Fluid computeVercelAug 22, 2026
Function maximum durationBeta above 800 seconds, requires Fluid compute, and requires maxDuration opt-in.1,800 seconds (30 minutes)Pro and EnterpriseVercelAug 22, 2026
Function request or response bodyPayloads over the documented limit return FUNCTION_PAYLOAD_TOO_LARGE with status 413.4.5 MBVercel Function request and responseVercelAug 22, 2026
Function memoryDocumented default and maximum for Vercel Functions.2 GB / 1 vCPUHobbyVercelAug 22, 2026

How to apply Vercel limits safely

The monitored baseline covers Hobby function memory, Function maximum duration, 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.

  1. Match the production workload to the exact scope printed beside each value and confirm it in the active Vercel console, configuration, or response headers.
  2. Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
  3. 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.

Compare alternatives

Official sources

View Vercel change history