Quick answer
Sentry documents attachment request size as 20 MB compressed request; 100 MB uncompressed per event. The crash report, when present, counts in the uncompressed event total.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| attachment request sizeThe crash report, when present, counts in the uncompressed event total. | 20 MB compressed request; 100 MB uncompressed per event | Events with attachments | SentryAug 22, 2026 |
Why does this limit matter?
Compression can make the transport fit while the expanded event still exceeds the second ceiling.
This value is scoped to Events with attachments; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Measure both compressed envelope bytes and total uncompressed attachments.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Uploads over the limit return 413 and the data is dropped immediately.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related