Verified history
Sentry doubled event attachment limits
Sentry's attachments documentation now allows at most 40 MB per compressed request and 200 MB of uncompressed attachments per event including the crash report (previously 20 MB / 100 MB). No effective date is published.
Larger crash reports and diagnostics fit without splitting.
Sentry attachment retention now follows the plan retention period
The attachments page states attachments are retained for 30 or 90 days depending on the plan's data retention period, replacing a single 30-day figure. No effective date is published.
Plans with 90-day retention keep attachments three times longer than the old figure implied.
Current monitored baseline
HyperObserve currently monitors 2 scoped observations for Sentry. The baseline covers attachment request size, attachment retention. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| 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 |
Tracked constraints and impact
Event attachment request, uncompressed payload, retention, and quota behavior. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
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.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current Sentry baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
40 MB compressed request, 200 MB uncompressed attachments, 30 or 90 day retention