docs(limits): Update docs to match new size limits for events/attachments

develop-docs/sdk/data-model/envelopes.mdx

@@ -341,10 +341,10 @@ SDKs should not rely on Envelope header authentication to retain backward compat
 Event ingestion imposes limits on the size and number of Items in Envelopes.
 These limits are subject to future change and defined currently as:
 
-- *20MB* for a compressed envelope request
-- *100MB* for a full envelope after decompression
-- *100MB* for all attachments combined
-- *100MB* for each attachment item
+- *40MB* for a compressed envelope request
+- *200MB* for a full envelope after decompression
+- *200MB* for all attachments combined
+- *200MB* for each attachment item
 - *1MB* for event (errors and transactions), span, log, and metric (statsd, buckets, meta) items.
 - *100KB* for monitor check-in items
 - *50MB* for profile items

docs/concepts/data-management/size-limits.mdx

@@ -13,7 +13,7 @@ The following describes how Sentry treats size limits:
 - Events, attachments, and requests exceeding payload size limits are immediately dropped with a `413 Payload Too Large` error.
 - Sentry allows compressed content encoding, and applies separate limits before and after decompression.
 - Events that exceed 200KB compressed or 1MB decompressed will be rejected.
-- Minidump uploads that exceed 20MB compressed or 100MB decompressed (for all files combined) will also be rejected.
+- Minidump uploads that exceed 40MB compressed or 200MB decompressed (for all files combined) will also be rejected.
 - Event fields exceeding the individual size limits are trimmed and truncated afterwards.
 - The number of events rejected due to size limits is counted towards the _Dropped_ category in [usage stats](/product/stats/#usage-stats).
 

docs/platforms/android/enriching-events/attachments/index.mdx

@@ -57,7 +57,7 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/apple/common/enriching-events/attachments/index.mdx

@@ -59,7 +59,7 @@ Adding attachments to crashes is currently not supported.
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/dart/common/enriching-events/attachments/index.mdx

@@ -53,7 +53,7 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/dart/guides/flutter/enriching-events/attachments/index.mdx

@@ -49,7 +49,7 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/dotnet/common/enriching-events/attachments/index.mdx

@@ -59,7 +59,7 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/go/common/enriching-events/attachments/index.mdx

@@ -17,7 +17,7 @@ Sentry can enrich your events for further investigation by storing additional fi
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/godot/enriching-events/attachments/index.mdx

@@ -51,7 +51,7 @@ You can add attachments that will be sent with every event using <PlatformIdenti
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/java/common/enriching-events/attachments/index.mdx

@@ -55,7 +55,7 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/javascript/common/enriching-events/attachments/index.mdx

@@ -18,7 +18,7 @@ You'll first need to import the SDK, as usual:
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/attachments/index.mdx

@@ -55,7 +55,7 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/native/common/enriching-events/attachments/index.mdx

@@ -19,7 +19,7 @@ To receive symbolicated stack traces, you have to upload debug information to Se
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 Usually, native crash reports range from a few kilobytes to a few megabytes. This leaves sufficient space to add custom attachments. In case your application generates particularly large crash reports, consider to limit or avoid adding additional attachments in the SDK.
 

docs/platforms/native/guides/minidumps/index.mdx

@@ -119,10 +119,10 @@ If your minidump's size exceeds the [limits](#size-limits) in the next section,
 Event ingestion imposes limits on the size and number of fields in multipart
 uploads. These limits are subject to future change and defined currently as:
 
-- _20MB_ for a compressed minidump request
-- _100MB_ for the full body after decompression
-- _100MB_ for all files combined
-- _100MB_ for each file individually
+- _40MB_ for a compressed minidump request
+- _200MB_ for the full body after decompression
+- _200MB_ for all files combined
+- _200MB_ for each file individually
 - _1MB_ for event payloads
 
 ## Store Minidumps as Attachments

docs/platforms/native/usage/crashes.mdx

@@ -19,7 +19,7 @@ The size of Minidumps can vary between a few kilobytes and many megabytes.
 Contributing factors are the number of threads, size of stack space, and the
 number of heap memory regions referenced from the stack. As Minidumps often
 contain large regions of empty memory, the SDK compresses Minidumps before
-uploading. Sentry drops requests with a body larger than _20MB_, or if they
-contain files larger than _100MB_.
+uploading. Sentry drops requests with a body larger than _40MB_, or if they
+contain files larger than _200MB_.
 
 </Alert>

docs/platforms/powershell/enriching-events/attachments/index.mdx

@@ -53,7 +53,7 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/python/enriching-events/attachments/index.mdx

@@ -11,7 +11,7 @@ Sentry can enrich your events for further investigation by storing additional fi
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/react-native/enriching-events/attachments/index.mdx

@@ -15,7 +15,7 @@ You'll first need to import the SDK, as usual:
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/ruby/common/enriching-events/attachments/index.mdx

@@ -11,7 +11,7 @@ Sentry can enrich your events for further investigation by storing additional fi
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/unity/enriching-events/attachments/index.mdx

@@ -53,7 +53,7 @@ Unity features a global <PlatformLink to="/enriching-events/scopes/">scope</Plat
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/platforms/unreal/configuration/setup-crashreporter/index.mdx

@@ -202,8 +202,8 @@ see [Debug Information Files](/platforms/unreal/data-management/debug-files/).
 Event ingestion imposes size limits on UE crash reports. These limits
 are subject to future change and defined currently as:
 
-- _20MB_ for a compressed request
-- _100MB_ for the full crash report after decompression
+- _40MB_ for a compressed request
+- _200MB_ for the full crash report after decompression
 
 ## Issues With the Crash Reporter
 

docs/platforms/unreal/enriching-events/attachments/index.mdx

@@ -103,7 +103,7 @@ The same result can be achieved by calling the corresponding function in bluepri
 
 <Alert>
 
-Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
+Sentry allows at most 40MB for a compressed request, and at most 200MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 </Alert>
 

docs/product/relay/operating-guidelines.mdx

@@ -125,7 +125,7 @@ Depending on the SDK or client, requests to these endpoints are performed with c
 
 <Alert>
 
-Proxies often set a default maximum body size for requests. Especially native crash reports and attachments can exceed these limits. We recommend to configure a maximum client body size of _100MB_.
+Proxies often set a default maximum body size for requests. Especially native crash reports and attachments can exceed these limits. We recommend to configure a maximum client body size of _200MB_.
 
 </Alert>
 

platform-includes/enriching-events/add-attachment/native.minidumps.mdx

@@ -1,5 +1,5 @@
 To send attachments directly to Sentry, add more files to the multipart form
-body. Note that the entire request must not exceed **20MB** in size, even with
+body. Note that the entire request must not exceed **40MB** in size, even with
 compressed content encoding. Sentry will use the provided file names and mime
 types and list those files in the _Event Attachments_ section at the bottom of
 the _Issue Details_ page: