Current documented limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| attachment request sizeThe crash report, when present, counts in the uncompressed event total. | 40 MB compressed request; 200 MB uncompressed attachments per event | Events with attachments | SentrySep 17, 2026 |
| attachment retentionAttachments stop storing when the included storage quota is exceeded. | 30 or 90 days, based on the plan's data retention period | Stored event attachments | SentrySep 17, 2026 |
How to apply Sentry limits safely
The monitored baseline covers attachment request size, attachment retention. 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.
- Match the production workload to the exact scope printed beside each value and confirm it in the active Sentry console, configuration, or response headers.
- Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
- 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.
Sentry Event Attachment Size Limits
Sentry Event Attachment Size Limits, verified against Sentry's official documentation with scope, implementation impact, caveats, and a direct check.
Sentry Attachment Retention & Quota
Sentry Attachment Retention & Quota, verified against Sentry's official documentation with scope, implementation impact, caveats, and a direct check.