Learn more about how Sentry can store additional files in the same request as event attachments.

On this page, you will learn how to attach files, such as logs or config files, to your events. You'll be able to see these attachments in alongside other event details.

The simplest way to create an attachment is to use a path. The SDK will read the contents of the file each time it prepares an event or transaction, then adds the attachment to the same envelope. If the SDK can't read the file, the SDK logs an error message and drops the attachment.

import Sentry

let attachment = Attachment(path: "your/path/file.log")

Alternately, use bytes to initialize an attachment. When doing so, you also need to specify a filename.

import Sentry

let attachment = Attachment(data: data, filename: "file.log")

If your SDK supports offline caching, which is typical for mobile, each attachment is stored to disk for each event or transaction you capture when the device is offline. When using large attachments, this storage can consume the disk space if the device is offline for a longer time period. You can specify maximum attachment size to drop large attachments and avoid this issue.

In addition, you can set these parameters:


The filename is the name of the file to display in Sentry. When using bytes you have to specify a filename, whereas with a path you don't as the SDK is going to use the last path component.


The type of content stored in this attachment. Any MIME type may be used; the default is application/octet-stream.

Attachments live on the Scope. You can either add an attachment on the global scope to be sent with every event or add it on the local Scope to just send the attachment with one specific event.

Adding attachments to crashes is currently not supported.

import Sentry

let fileAttachment = Attachment(path: "your/path/file.log")

// Global Scope
SentrySDK.configureScope { scope in

// Local Scope
SentrySDK.captureMessage(message: "my message", block: { scope in

// Clear all attachments in the global Scope
SentrySDK.configureScope { scope in

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.

Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.

Learn more about how attachments impact your quota.

To limit access to attachments, navigate to your organization's General Settings, then select the Attachments Access dropdown to set appropriate access — any member of your organization, the organization billing owner, member, admin, manager, or owner.

Attachments Access

By default, access is granted to all members when storage is enabled. If a member does not have access to the project, the ability to download an attachment is not available; the button will be greyed out in Sentry. The member may only view that an attachment is stored.

Attachments display on the bottom of the Issue Details page for the event that is shown.

Attachments Access Denied

Alternately, attachments also appear in the Attachments tab on the Issue Details page, where you can view the Type of attachment, as well as associated events. Click the Event ID to open the Issue Details of that specific event.

Attachments List Example

The maximum size for each attachment is set on SentryOptions.maxAttachmentSize.

The scale is bytes and the default is 20 MiB. Please also check the maximum attachment size of Relay to make sure your attachments don't get discarded there.

import Sentry

SentrySDK.start { options in
    options.maxAttachmentSize = 5 * 1024 * 1024 // 5 MiB
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").