> 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/bugsplat-application-uptime-data/what-are-the-upload-size-considerations-with-bugsplat-accounts..md).

# What are the upload size considerations with BugSplat accounts.

Crash reports uploaded to BugSplat are typically quite small. However, you can add additional data to each crash report, for example, many customers include log files. If you add additional data to crash reports, be aware that your BugSplat subscription has crash report size limitations. The size limitations apply to the total size of the compress (zipped) crash report.

Crash uploads are limited to **100 MB** (compressed), this includes the size of the minidump file or other crash artifacts generated by BugSplat, which are typically less than **50k**.

BugSplat allows larger upload size limits for Enterprise level users.


---

# 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/bugsplat-application-uptime-data/what-are-the-upload-size-considerations-with-bugsplat-accounts..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.
