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
| Limit | Value |
|---|---|
| Reserved slugs | mcp, api, www, preview, ip — never available |
| Slug matching | Trimmed 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
| Limit | Value | On exceeding |
|---|---|---|
| Domains per distribution | 10 | Attach fails |
| Domain creations per workspace | 10 per hour | 429 |
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
| Limit | Value | On exceeding |
|---|---|---|
| Inline content per file | 100,000 bytes | That item's error is object exceeds 100000 bytes. Other items in the same call can still be written. |
| Content written in one call | 2,000,000 bytes | Each item that does not fit has error call total exceeds 2000000 bytes. Items already written in that call stay written. |
| Upload URL lifetime | 3,600 seconds | The PUT is rejected. Open a new deployment to get a new URL. |
| One bundle PUT | 5,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
| Limit | Value | On exceeding |
|---|---|---|
| Exact rules per distribution | 5,000 | 422 |
Pattern (*) rules per distribution | 100 | 422 |
from path, once percent-encoded | 493 bytes | 422 |
to target | 900 bytes | 422 |
Hosts in redirect_hosts | 20 | 422 |
| Redirect hops checked for loops | 10 | A chain that does not end within 10 hops is rejected as a loop |
| Import source | 1 MiB | 422; 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
| Limit | Value |
|---|---|
Earliest at | 60 seconds from now |
Latest at | 366 days from now |
| Pending schedules per distribution | 20 |
| Schedules per distribution in one minute | 1 |
| Precision | Runs within about a minute of at |
| Late schedules | Not run if Edge reaches them more than 24 hours late; marked failed |
Analytics
| Limit | Value |
|---|---|
| Data retention | 91 days |
| Custom properties per event | 2,048 bytes |
| Explore path depth | 4 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
| Limit | Value |
|---|---|
| Recent log retention | 7 days |
| Older logs | Not 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
| Limit | Value |
|---|---|
| Cache TTL range | 0 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.
| Limit | Value |
|---|---|
| Proxy endpoints per distribution | 100 |
| Encrypted proxy credentials per distribution | 5 |
| Data objects per distribution | 1,000 |
| Data object key depth | 8 levels |
| Data object key length | 256 characters |
| Collect request body | 256 KiB |
| Submit request body | 256 KiB |
| API request body | 1 MiB |
| Proxy timeout | 10 seconds |
| Default API cache TTL | 60 seconds |
| Session cookie lifetime | 24 hours |
Rate limits, per distribution:
| Path | Limit |
|---|---|
| Collect | 60 requests per minute |
| Submit | 30 requests per minute |
| API reads | 120 requests per minute |
| API writes | 30 requests per minute |
Exceeding any of these returns 429.
Function runtimes
| Limit | Value |
|---|---|
| Source per function runtime | 256 KiB |
| Compiled WebAssembly artifact | 32 MiB |
| Native precompiled module | 96 MiB |
| Fuel per invocation | 10,000,000 |
| Memory | 64 MiB |
| Guest deadline | 5 seconds |
| Build timeout | 180 seconds |
| Request body, or text response body | 1 MiB |
| Binary response body (decoded) | 4 MiB |
| Captured stdout and stderr | 8 KiB per stream |
Build log returned by edge_function_get | 32 KiB |
| Log retention | 7 days |
| Host calls per invocation (data objects, key-value and SQL together) | 8 |
Keys returned per env.document.list page | 50 |
| Prefix grants per distribution | 32 |
| Scripts listed on one sidecar grant | 32 |
Bytes per env.file call (put, get, read, append) | 4 MiB |
One file, written with create / append / commit | 5 GiB |
| File bytes written, and read, per invocation | 512 MiB (5 GiB on a background route) |
| File prefix grants per distribution | 32 |
| Function files per distribution | 50 GiB and 100,000 files |
env.file.link lifetime | 60 to 3,600 seconds |
File served directly by a file route | 4 MiB (larger files redirect) |
| Background run | 300 seconds, 30× fuel, 256 MiB memory |
| Background request body | 192 KiB |
| Background runs active per distribution | 5 |
| Background result kept | 7 days, 1 MiB |
Background jobs
A function runtime run as a background job uses the background runner, not the limits above.
| Limit | Value |
|---|---|
| Guest deadline | 300 seconds by default; set background_timeout_seconds from 1 to 840 |
| Fuel | Scales with the deadline |
| Memory | 256 MiB |
| Outbound HTTPS calls | 100 per run, 15 seconds each, 2 MiB response |
| Captured stdout and stderr | 64 KiB per stream |
| Jobs running at once per organization | 4 |
| Job run history | 30 days |
Crons
| Limit | Value |
|---|---|
| Crons per distribution | 20 |
| Shortest interval | 1 minute; Edge checks every minute |
| Retries after a failed run | 0 to 3 (30 seconds, 2 minutes, then 10 minutes apart) |
| Late runs | A run Edge reaches more than 24 hours late is recorded as missed and not run |
| Missed slots | Run once when Edge catches up, not once per slot |
Queues
| Limit | Value |
|---|---|
| Queues per distribution | 10 |
| Message body | 128 KiB of JSON |
| Messages per send | 100, at most 1 MiB together |
| Waiting and in-batch messages per queue | 100,000; a send past it fails with queue_full |
| Send rate per distribution | 100 messages a second, bursts up to 1,000; past it, rate_limited |
delay_seconds | 0 to 604,800 (7 days) |
| Batch size | 1 to 100 messages (default 10), at most 1 MiB of bodies |
batch_wait_seconds | 0 to 60 (default 5) |
| Batches running at once per queue | 1 to 10 (default 2) |
max_attempts | 1 to 10 (default 3) |
| Waiting messages kept | retention_days, 1 to 14 (default 4); then dead with expired |
| Dead messages kept | 14 days |
| Webhook consumer timeout | 30 seconds per batch |
| Retry delay | min(2^attempt × 10 s, 1 h) ± 20 %, or the consumer's delay_seconds |
idempotency_key | Up to 128 characters; deduplicates while its message is in the queue |
env.queue messages per invocation | 10 on a visitor request, 100 in a background job |
Workflows
| Limit | Value |
|---|---|
| Running, sleeping or waiting runs per distribution | 1,000; a start past it fails with limit_reached |
| Steps per run | 200 |
| Run lifetime | 90 days; then the run fails with expired |
| Step input, output and signal payload | 256 KiB of JSON each |
sleep and wait | Up to 30 days each |
| Retries per step | 0 to 5 (default 2), min(2^attempt × 5 s, 10 min) ± 20 % apart |
| Signals kept before the run waits for them | 10 |
Step history in edge_workflow_get | Job runs, kept 30 days |
env.workflow calls per invocation | 10 on a visitor request, 50 in a background job |
Scripts in one function's workflow_starts | 50, or ["*"] |
Key-value and SQL
| Limit | Value |
|---|---|
| Key-value value size | 64 KiB |
| Key-value keys per distribution | 10,000 |
| Key-value key length and depth | 256 characters, 8 segments |
Keys per env.kv.getMany call | 25 |
Keys per env.kv.list page | 100 (default 50) |
Key-value expiry (ttl) | 60 seconds to 1 year |
| SQL statement text | 64 KiB |
| SQL parameters per statement | 100 |
SQL statements per env.sql.batch | 20 |
| SQL rows returned per call | 1,000 |
| SQL result per call | 1 MiB |
| SQL database size | 100 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
| Limit | Value | On exceeding |
|---|---|---|
| Forms with uploads per distribution | 20 | 422 |
| Upload fields per form | 10 | 422 |
Files per field (max_files) | 1 to 10 | 422 |
One file (max_bytes) | 1 byte to 5 GiB; default 100 MiB | Ticket 400 invalid_upload, reason size |
| One submission | 10 files and 10 GiB in total | 422 |
| File name | 255 characters | Ticket 400 invalid_upload, reason name |
| Single-request upload | Up to 100 MiB; larger files use 16 MiB parts | — |
| Part URLs per call | 100 | Ask /parts for more |
| Single ticket lifetime | 10 minutes | Storage refuses the post |
| Part URL lifetime | 1 hour | Storage refuses the PUT |
| Tickets per IP address | 20 per minute | 429 rate_limited |
| Tickets per visitor session | 50 per day | 429 rate_limited |
| Uploads per organization | 100 GiB and 50,000 files per month | 403 quota_exceeded |
| Unattached uploads | Deleted after 1 day | — |
| Extracted text | From PDF, Word, text and CSV files up to 200 MiB; up to 1 MiB of text | No text; has_text is false |
See Endpoints.
Visitor uploads from a function
These apply to uploads a function signs with env.upload.
| Limit | Value | On exceeding |
|---|---|---|
| One file | 1 byte to 5 GiB | too_large |
| Single-request upload | Up to 100 MiB; larger files use 16 MiB parts | — |
Part URLs per sign or parts call | 100 | Call parts for more |
| Single ticket lifetime | 10 minutes | Storage refuses the post |
| Part URL lifetime | 1 hour | Storage refuses the PUT |
Bytes per env.upload.read call | 4 MiB | too_large |
sign, parts, complete, status and keep | Share the 8 host calls per invocation with env.document and env.file | budget_exhausted |
| Uploads per organization | 100 GiB and 50,000 files per month, shared with form uploads | quota_exceeded |
| Uploads never kept | Deleted after 1 day | — |
See Function runtimes.
Form submissions
These apply to reading submissions and their files.
| Limit | Value |
|---|---|
| Submissions per list page | 50 |
| Default list window | The last 30 days |
| Preview in a list | 200 characters |
| Extracted text per page | 100,000 characters |
File returned inline (content) | Images and PDF up to 10 MiB |
Agent download link (link) | 15 minutes |
| Download redirect | 60 seconds |
Webhook download_url | 7 days from the event |
| Submission reads per day | 1,000 per person for agents, per token for personal access tokens |
| File reads per day | 200 per person for agents, per token for personal access tokens |
| Daily reset | 00:00 UTC |
| Access log entries per read | 100, newest first |
| Access log retention | 365 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
| Limit | Value |
|---|---|
| Webhook subscriptions per workspace | 25 |
| Event patterns per subscription | 32 |
| Delivery timeout | 10 seconds per attempt |
| Delivery attempts | 9, over about 22.7 hours |
| Subscription turned off after | 10 consecutive failed deliveries, or one 410 Gone |
| Previous secret valid after rotation | 24 hours |
| Event, delivery and attempt history | 30 days |
| Hooks per distribution | 20 |
| Hook request body | 256 KB (413) |
| Idempotency key | 255 characters (400) |
| Hook receipts | 7 days |
| Hook rate | 600 requests per 5 minutes per client IP |
Cache paths per invalidate action | 15 |
See Events, webhooks, and hooks.
Visitor access
| Limit | Value |
|---|---|
| Session length | 1 hour to 24 hours; default 8 hours |
| Access rules per distribution | 200 |
| Access rules per workspace | 500 |
| Active sign-outs per distribution | 1,000 |
| Sign-in completion code | 30 seconds, single use |
See Access control.
Network rules
| Limit | Value |
|---|---|
| Network rules per distribution | 200 |
| Network rules per workspace | 200 |
| Rules per request | 200 |
| IP ranges per distribution, after its own and the workspace's rules are merged | 250 |
| Widest range | /8 for IPv4, /16 for IPv6 |
| Note | 200 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
| Limit | Value |
|---|---|
| Active tokens per person, per organization | 50 |
| Tokens created per person, per hour | 20 |
| Name length | 64 characters |
| Longest expiry other than never | 365 days |
| Default expiry | 30 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
- Upload content — inline write or bundle, and which error means which
- Errors — the status codes these limits produce
- Endpoints
- Distribution types
- Permission scopes
- HTTP API