> 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/how-tos/remove-crashes.md).
# Remove Crashes
Remove mistakes and other clutter by deleting crashes in your BugSplat database.
When working with new tools, it can take a few rounds of trial and error before you get things exactly right. In BugSplat, sometimes this means posting a crash from a test application or otherwise creating clutter in your workspace. Never fear! BugSplat allows you to batch remove clutter from your database.
{% hint style="danger" %}
Removing crashes is a destructive action that can't be undone. Tread carefully!
{% endhint %}
### Steps 🥾
1. Navigate to the [Crashes](https://app.bugsplat.com/v2/crashes) page and select your BugSplat database
2. Filter and sort to a list of crashes that you would like to remove
3. Carefully review the list of crashes in your current view, then check the box next to each crash you want to remove. Only the crashes you select will be removed from your database.
4. Click the **🗑️ Delete** button to load a confirmation modal
5. Click **Delete** in the confirmation modal to delete your crashes
**Note:** deleting crashes should be done sparingly in the case of mistakes. If you'd like to stop processing crashes for a specific version, consider using the retire crashes feature or create a new database instead.
Deleting Invalid Crash Reports
---
# 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/how-tos/remove-crashes.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.
