> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/education/faq/how-do-i-download-crash-attachments-in-bulk.md).

# How Do I Download Crash Attachments in Bulk?

BugSplat stores each crash report as a zip file that contains the crash file, such as a minidump, along with every attachment that was posted with it. If you need those files outside of BugSplat, you can grab them a row at a time from the app, fetch them programmatically with the API, or have BugSplat push every crash to you as it arrives with a [Webhook](https://docs.bugsplat.com/guides/integrating-with-tools/messanger-apps/webhook.md).

## Download from the app

The **Download** column contains a link that downloads a crash and its attachments as a single zip file. The column is available on the [Crashes](https://app.bugsplat.com/v2/crashes) page and the Crash Group page, and it's hidden by default. To show it:

1. Click the **Column Visibility** control above the top right corner of the table.
2. Check **Download**.
3. Click **DOWNLOAD** on any row to save that crash's zip file.

<figure><img src="https://976110677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LBMgmIcgkIXSUfnXDSv%2Fuploads%2Fgit-blob-9c9cebb65dd2d4f18cf9c22aa1bb71384d866adf%2Fdownload-crash-attachments-column.png?alt=media" alt="Enabling the Download column with the Column Visibility control"><figcaption><p>Enabling the Download column on the Crash Group page</p></figcaption></figure>

Narrow the table with [Searching](https://docs.bugsplat.com/guides/searching/search.md), [Grouping](https://docs.bugsplat.com/guides/searching/grouping.md), or the **Timeframe** filter before you start, so the rows you download are the ones you care about.

If you only need one file rather than the whole zip, open the crash and use the **Attachments** tab described in [Using the App](https://docs.bugsplat.com/guides/using-the-app.md#previewing-attached-files).

## Download with the API

{% hint style="danger" %}

#### 🚨 Do not call the Crash API more than once per second 🚨

**One request per second is a hard ceiling.** Put a delay between requests and never fan them out in parallel. Scripts that hammer the Crash endpoint will be throttled.

**Need more than one crash per second?** Do not raise the rate. Use the [Webhook](https://docs.bugsplat.com/guides/integrating-with-tools/messanger-apps/webhook.md) instead, as described [below](#get-every-crash-with-a-webhook).
{% endhint %}

To pull attachments for a set of crashes, script it against BugSplat's API:

1. Call the [Crashes](https://docs.bugsplat.com/api-reference/api/crashes.md) endpoint to list the crashes you're interested in. It supports [paging, filtering, and grouping](https://docs.bugsplat.com/api-reference/paging-filtering-and-grouping.md), so you can limit the results to a specific application, version, or date range.
2. For each `id` in the response, call the [Crash](https://docs.bugsplat.com/api-reference/api/crash.md#get-crash) endpoint, **waiting at least one second between calls**.
3. Download the zip from the pre-signed URL in the `dumpfile` property of the response. The zip contains the crash file and all of its attachments. Pre-signed URLs are short lived, so download the file shortly after you request the crash details.

{% hint style="info" %}
API access requires an [OAuth2](https://docs.bugsplat.com/api-reference/oauth2.md) token with the **restricted** scope, and is available on the Business and Enterprise [plans](https://www.bugsplat.com/pricing/).
{% endhint %}

## Get every crash with a webhook

If you want a copy of every crash BugSplat receives, don't poll the API for it. Configure a [Webhook](https://docs.bugsplat.com/guides/integrating-with-tools/messanger-apps/webhook.md) instead. BugSplat calls your webhook once per new report, and the payload includes a `crashFileUrl` pre-signed URL you can use to download the crash file. Webhook notifications have no maximum throughput limitation, so this scales with your crash volume in a way that polling does not.

{% hint style="warning" %}
Your endpoint receives one call per crash and **BugSplat does not retry failed deliveries**. Anything your webhook drops, rejects, or times out on is not sent again. Make sure it can handle your peak crash volume, and prefer acknowledging the request immediately and downloading `crashFileUrl` from a background queue.
{% endhint %}

If you're not sure how to get started, or you need to export more data than these options allow, please send us a note at <support@bugsplat.com>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugsplat.com/education/faq/how-do-i-download-crash-attachments-in-bulk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
