Platform hub

Netlify limits

Synchronous, scheduled, background, and edge function resource limits. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  Netlify 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
synchronous function durationScheduled functions use a separate shorter maximum.60 secondsSynchronous FunctionsNetlifyAug 22, 2026
background function durationBackground functions also have a much smaller request payload allowance.15 minutesBackground FunctionsNetlifyAug 22, 2026
buffered and streamed payloadBinary payloads can reach the buffered limit at roughly 4.5 MB before base64 expansion.6 MB buffered; 20 MB streamed; 256 KB backgroundFunction-type specificNetlifyAug 22, 2026
default function memoryMemory configuration is separate from function duration and payload size.1,024 MBFunctionsNetlifyAug 22, 2026
edge resource ceilingsResponse headers must be produced within the documented 40-second window.512 MB memory; 50 ms CPU; 20 MB compressed codeEdge FunctionsNetlifyAug 22, 2026

How to apply Netlify limits safely

The monitored baseline covers synchronous function duration, background function duration, buffered and streamed payload, default function memory, edge resource ceilings. 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 Netlify 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 Netlify change history