Platform hub

Render limits

Build, deploy, free-instance, response, workflow, cron, and storage limits. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  Render 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
maximum build durationOnly one build is active for a service at a time.120 minutesBuild pipelineRenderAug 22, 2026
pre-deploy durationPre-deploy runs after build and before the new service version starts.30 minutesEligible servicesRenderAug 22, 2026
maximum HTTP response durationClient, proxy, and application timeouts can still be shorter.Up to 100 minutesWeb servicesRenderAug 22, 2026
free web service allowanceThe filesystem is ephemeral and spin-up latency follows idle suspension.750 hours/month; spins down after 15 idle minutesFree web servicesRenderAug 22, 2026
free database allowanceBackups and connection pooling are not included on the free database.1 GB; expires after 30 days with 14-day graceFree PostgresRenderAug 22, 2026

How to apply Render limits safely

The monitored baseline covers maximum build duration, pre-deploy duration, maximum HTTP response duration, free web service allowance, free database allowance. 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 Render 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 Render change history