Platform hub

Google Cloud Functions limits

Generation-specific function duration, memory, payload, and API quotas. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  Google Cloud Functions 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
generation-specific maximumThe maximum depends on generation and invocation type.1st gen: 540s; 2nd gen HTTP: 60m; scheduled: 30m; event: 540sCloud Run functionsGoogle CloudAug 22, 2026
maximum function memoryProject and regional quotas also govern aggregate memory use.1st gen: 8 GiB; 2nd gen: 32 GiBGeneration specificGoogle CloudAug 22, 2026
request and event payloadHTTP request/response, event, and streaming paths have different documented ceilings.Generation and invocation-type specificCloud Run functionsGoogle CloudAug 22, 2026
control-plane API ratesDeployment and management API quotas are separate from requests to deployed functions.Read and write quotas vary by generation and regionPer projectGoogle CloudAug 22, 2026

How to apply Google Cloud Functions limits safely

The monitored baseline covers generation-specific maximum, maximum function memory, request and event payload, control-plane API rates. 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 Google Cloud Functions 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.

Official sources

View Google Cloud Functions change history