> 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/manually-post-crash-reports-to-bugsplat.md).

# Manually Upload Crash Reports to BugSplat

BugSplat's [Crash Upload](https://app.bugsplat.com/v2/upload) page allows users to upload a BugSplat crash report manually.

Uploading a report manually can be necessary, for example, when a crash occurs on a computer not connected to the Internet. When BugSplat can't upload the file automatically, the zip file containing the crash report data is displayed in the BugSplat crash report dialog.

To manually upload a crash report, browse for the zip file using the **Select files** link or drag and drop the file on the [Crash Upload](https://app.bugsplat.com/v2/upload) page.

<figure><img src="/files/uR5F5vzV1INLe5BVZp7U" alt=""><figcaption><p>Upload a Crash via Drag and Drop</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bugsplat.com/education/faq/manually-post-crash-reports-to-bugsplat.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.