> 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.
Upload a Crash via Drag and Drop
---
# 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/manually-post-crash-reports-to-bugsplat.md?ask=&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.
