Skip to content

Limits ​

Every value below is enforced by Edge. Where a limit produces a specific status code, it is named.

This page lists the limits Edge checks explicitly. The absence of something here is not a guarantee that it is unbounded — it means there is no fixed number to quote.

Distributions and slugs ​

LimitValue
Reserved slugsmcp, api, www, preview, ip — never available
Slug matchingTrimmed and lowercased before comparison, so Acme and acme are the same slug

Slugs are globally unique hostname labels. Check availability with GET /v1/slugs/{slug} before creating; it does not reserve the name, so a slug can be taken between your check and your create. A create that loses that race returns 409.

Domains ​

LimitValueOn exceeding
Domains per distribution10Attach fails
Domain creations per workspace10 per hour429

The creation limit is per workspace and rolling over the past hour, not per distribution and not per calendar hour. If you are bulk-registering domains, pace them; retrying in a loop will not get you through it any faster.

Files in a deployment ​

LimitValueOn exceeding
Inline content per file100,000 bytesThat item's error is object exceeds 100000 bytes. Other items in the same call can still be written.
Content written in one call2,000,000 bytesEach item that does not fit has error call total exceeds 2000000 bytes. Items already written in that call stay written.
Upload URL lifetime3,600 secondsThe PUT is rejected. Open a new deployment to get a new URL.
One bundle PUT5,368,709,120 bytes (5 GiB)S3 rejects the PUT. The URL is a single PutObject; there is no multipart upload.

The call itself returns success. Read each item in results: status is written or error.

The two inline caps apply to edge_content_write and PUT /v1/deployments/{id}/content. They do not apply to files inside an uploaded bundle.tar.gz.

A single file larger than 2,000,000 bytes reports the call-total error, because that check runs first. That file is also over the per-file cap. It cannot be written inline.

upload_url from edge_deployment_create (or POST /v1/distributions/{id}/deployments) is a presigned S3 PUT. The file bytes go to S3. They do not pass through the MCP server or the HTTP API, so the firewall in front of those hosts does not see the upload, and the inline caps do not apply to it. PUT the gzip archive as returned — no Content-Type and no encryption headers.

There is no application byte cap below the 5 GiB single-PUT maximum. Commit reads the whole archive into memory, so an object S3 has already accepted can still fail at commit when the archive is very large.

A deployment opened with from_deployment does not read an uploaded bundle. The worker copies the previous deployment and applies inline writes. See Upload content.

Redirects ​

LimitValueOn exceeding
Exact rules per distribution5,000422
Pattern (*) rules per distribution100422
from path, once percent-encoded493 bytes422
to target900 bytes422
Hosts in redirect_hosts20422
Redirect hops checked for loops10A chain that does not end within 10 hops is rejected as a loop
Import source1 MiB422; split the file

Redirect tables share the edge's storage with every other distribution. An import that would not fit reports how many bytes it needs and how many are left. See Redirects.

Scheduled promotes and takedowns ​

LimitValue
Earliest at60 seconds from now
Latest at366 days from now
Pending schedules per distribution20
Schedules per distribution in one minute1
PrecisionRuns within about a minute of at
Late schedulesNot run if Edge reaches them more than 24 hours late; marked failed

Analytics ​

LimitValue
Data retention91 days
Custom properties per event2,048 bytes
Explore path depth4 columns

Queries can request a range up to last_91_days or all_time; beyond the retention window there is no data to return rather than an error.

Request logs ​

LimitValue
Recent log retention7 days
Older logsNot queryable yet

Logs within the last 7 days are served from the hot store and are current. Requesting a range that starts before that window returns 503. Edge does not silently return an incomplete range.

Request logs include the client IP address and country. They never include query strings, cookies, or request bodies.

Cache ​

LimitValue
Cache TTL range0 to 3,600 seconds

A TTL outside that range is rejected as 422 rather than clamped.

Endpoints ​

These apply to /_api, /_collect, /_submit and related paths on a distribution.

LimitValue
Proxy endpoints per distribution100
Encrypted proxy credentials per distribution5
Data objects per distribution1,000
Data object key depth8 levels
Data object key length256 characters
Collect request body256 KiB
Submit request body256 KiB
API request body1 MiB
Proxy timeout10 seconds
Default API cache TTL60 seconds
Session cookie lifetime24 hours

Rate limits, per distribution:

PathLimit
Collect60 requests per minute
Submit30 requests per minute
API reads120 requests per minute
API writes30 requests per minute

Exceeding any of these returns 429.

Function runtimes ​

LimitValue
Source per function runtime256 KiB
Compiled WebAssembly artifact32 MiB
Native precompiled module96 MiB
Fuel per invocation10,000,000
Memory64 MiB
Guest deadline5 seconds
Build timeout180 seconds
Request body, or text response body1 MiB
Binary response body (decoded)4 MiB
Captured stdout and stderr8 KiB per stream
Build log returned by edge_function_get32 KiB
Log retention7 days
Host calls per invocation (data objects, key-value and SQL together)8
Keys returned per env.document.list page50
Prefix grants per distribution32
Scripts listed on one sidecar grant32
Bytes per env.file call (put, get, read, append)4 MiB
One file, written with create / append / commit5 GiB
File bytes written, and read, per invocation512 MiB (5 GiB on a background route)
File prefix grants per distribution32
Function files per distribution50 GiB and 100,000 files
env.file.link lifetime60 to 3,600 seconds
File served directly by a file route4 MiB (larger files redirect)
Background run300 seconds, 30× fuel, 256 MiB memory
Background request body192 KiB
Background runs active per distribution5
Background result kept7 days, 1 MiB

Background jobs ​

A function runtime run as a background job uses the background runner, not the limits above.

LimitValue
Guest deadline300 seconds by default; set background_timeout_seconds from 1 to 840
FuelScales with the deadline
Memory256 MiB
Outbound HTTPS calls100 per run, 15 seconds each, 2 MiB response
Captured stdout and stderr64 KiB per stream
Jobs running at once per organization4
Job run history30 days

Crons ​

LimitValue
Crons per distribution20
Shortest interval1 minute; Edge checks every minute
Retries after a failed run0 to 3 (30 seconds, 2 minutes, then 10 minutes apart)
Late runsA run Edge reaches more than 24 hours late is recorded as missed and not run
Missed slotsRun once when Edge catches up, not once per slot

Queues ​

LimitValue
Queues per distribution10
Message body128 KiB of JSON
Messages per send100, at most 1 MiB together
Waiting and in-batch messages per queue100,000; a send past it fails with queue_full
Send rate per distribution100 messages a second, bursts up to 1,000; past it, rate_limited
delay_seconds0 to 604,800 (7 days)
Batch size1 to 100 messages (default 10), at most 1 MiB of bodies
batch_wait_seconds0 to 60 (default 5)
Batches running at once per queue1 to 10 (default 2)
max_attempts1 to 10 (default 3)
Waiting messages keptretention_days, 1 to 14 (default 4); then dead with expired
Dead messages kept14 days
Webhook consumer timeout30 seconds per batch
Retry delaymin(2^attempt × 10 s, 1 h) ± 20 %, or the consumer's delay_seconds
idempotency_keyUp to 128 characters; deduplicates while its message is in the queue
env.queue messages per invocation10 on a visitor request, 100 in a background job

Workflows ​

LimitValue
Running, sleeping or waiting runs per distribution1,000; a start past it fails with limit_reached
Steps per run200
Run lifetime90 days; then the run fails with expired
Step input, output and signal payload256 KiB of JSON each
sleep and waitUp to 30 days each
Retries per step0 to 5 (default 2), min(2^attempt × 5 s, 10 min) ± 20 % apart
Signals kept before the run waits for them10
Step history in edge_workflow_getJob runs, kept 30 days
env.workflow calls per invocation10 on a visitor request, 50 in a background job
Scripts in one function's workflow_starts50, or ["*"]

Key-value and SQL ​

LimitValue
Key-value value size64 KiB
Key-value keys per distribution10,000
Key-value key length and depth256 characters, 8 segments
Keys per env.kv.getMany call25
Keys per env.kv.list page100 (default 50)
Key-value expiry (ttl)60 seconds to 1 year
SQL statement text64 KiB
SQL parameters per statement100
SQL statements per env.sql.batch20
SQL rows returned per call1,000
SQL result per call1 MiB
SQL database size100 MiB

See Use key-value and SQL storage from a function.

Source must be self-contained. Edge does not resolve npm or pip dependencies during a build; bundle dependencies into the submitted source. See Function runtimes and Add an endpoint.

Mapping rules for data objects, proxies and function runtimes are in Endpoints.

Form uploads ​

LimitValueOn exceeding
Forms with uploads per distribution20422
Upload fields per form10422
Files per field (max_files)1 to 10422
One file (max_bytes)1 byte to 5 GiB; default 100 MiBTicket 400 invalid_upload, reason size
One submission10 files and 10 GiB in total422
File name255 charactersTicket 400 invalid_upload, reason name
Single-request uploadUp to 100 MiB; larger files use 16 MiB parts—
Part URLs per call100Ask /parts for more
Single ticket lifetime10 minutesStorage refuses the post
Part URL lifetime1 hourStorage refuses the PUT
Tickets per IP address20 per minute429 rate_limited
Tickets per visitor session50 per day429 rate_limited
Uploads per organization100 GiB and 50,000 files per month403 quota_exceeded
Unattached uploadsDeleted after 1 day—
Extracted textFrom PDF, Word, text and CSV files up to 200 MiB; up to 1 MiB of textNo text; has_text is false

See Endpoints.

Visitor uploads from a function ​

These apply to uploads a function signs with env.upload.

LimitValueOn exceeding
One file1 byte to 5 GiBtoo_large
Single-request uploadUp to 100 MiB; larger files use 16 MiB parts—
Part URLs per sign or parts call100Call parts for more
Single ticket lifetime10 minutesStorage refuses the post
Part URL lifetime1 hourStorage refuses the PUT
Bytes per env.upload.read call4 MiBtoo_large
sign, parts, complete, status and keepShare the 8 host calls per invocation with env.document and env.filebudget_exhausted
Uploads per organization100 GiB and 50,000 files per month, shared with form uploadsquota_exceeded
Uploads never keptDeleted after 1 day—

See Function runtimes.

Form submissions ​

These apply to reading submissions and their files.

LimitValue
Submissions per list page50
Default list windowThe last 30 days
Preview in a list200 characters
Extracted text per page100,000 characters
File returned inline (content)Images and PDF up to 10 MiB
Agent download link (link)15 minutes
Download redirect60 seconds
Webhook download_url7 days from the event
Submission reads per day1,000 per person for agents, per token for personal access tokens
File reads per day200 per person for agents, per token for personal access tokens
Daily reset00:00 UTC
Access log entries per read100, newest first
Access log retention365 days

Over a daily cap, reads return 429 rate_limited until the reset. People reading with their own sign-in are not capped. See Let an agent read form submissions.

Webhooks and hooks ​

LimitValue
Webhook subscriptions per workspace25
Event patterns per subscription32
Delivery timeout10 seconds per attempt
Delivery attempts9, over about 22.7 hours
Subscription turned off after10 consecutive failed deliveries, or one 410 Gone
Previous secret valid after rotation24 hours
Event, delivery and attempt history30 days
Hooks per distribution20
Hook request body256 KB (413)
Idempotency key255 characters (400)
Hook receipts7 days
Hook rate600 requests per 5 minutes per client IP
Cache paths per invalidate action15

See Events, webhooks, and hooks.

Visitor access ​

LimitValue
Session length1 hour to 24 hours; default 8 hours
Access rules per distribution200
Access rules per workspace500
Active sign-outs per distribution1,000
Sign-in completion code30 seconds, single use

See Access control.

Network rules ​

LimitValue
Network rules per distribution200
Network rules per workspace200
Rules per request200
IP ranges per distribution, after its own and the workspace's rules are merged250
Widest range/8 for IPv4, /16 for IPv6
Note200 characters

Overlapping and neighbouring ranges merge before the 250 count, so 192.0.2.0/25 and 192.0.2.128/25 count once. Past a limit the response is 409 NETWORK_RULE_LIMIT, and no rule from that request is added. See Access control.

Personal access tokens ​

LimitValue
Active tokens per person, per organization50
Tokens created per person, per hour20
Name length64 characters
Longest expiry other than never365 days
Default expiry30 days

A revoked or expired token does not count toward the active limit.

Streaming ​

The analytics and log streams are long-lived HTTP responses rather than permanent connections. A log stream closes after 150 poll cycles and expects the client to reconnect. Treat a closed stream as normal and reconnect rather than as an error.

See also ​