---
description: >-
  A crash reporter like BugSplat is a software program that captures the state
  of a software application at the time of a crash to help developers understand
  and fix the underlying issue.
---

# What is a crash reporter?

A **crash reporter** is a software program that helps developers identify when, where, and how often a software application crashes to help diagnose and fix the underlying problem causing the crash.

Crash reporters are a valuable part of the software development lifecycle as they greatly simplify and improve developers' processes to fix bugs, defects, or other exceptions that cause application crashes.

They perform this task automatically, capturing an application's state during the crash. This 'snapshot' often includes the collection of a minidump file, including the runtime stack of each active thread during the crash.

Access to this information allows developers to identify the underlying issue causing the application to crash without seeing it in real-time or recreating the issue on their own computers.

Most people interact with a crash reporter via the [**dialog box**](../how-tos/customize-the-crash-dialog) (shown below) or the window that appears after an application crashes. This box provides basic information about what happened and gives the user a chance to provide additional details about the events leading up to the crash event.

<figure><img src="https://976110677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LBMgmIcgkIXSUfnXDSv%2Fuploads%2F5KYD3k2PBbwsA1HDm1T7%2Fcrash-reporter-dialog-bugsplat.png?alt=media&#x26;token=9522d656-c6da-4d8d-b24a-0edbbc27868e" alt=""><figcaption><p>Example BugSplat Crash Dialog</p></figcaption></figure>

### A Critical Tool for Support

Crash reporters have become an increasingly common tool for developers and QA teams supporting deployed software applications.

With a crash reporter, teams can automatically record every instance of their application's crash history, ensuring that their dev and support teams have the best data to work with as they endeavor to support their application.

Crash reporters often remove the need to review every crash manually as they intelligently group crashes that are similar or crashed because of the same defects into [crash groups](../../introduction/development/web-services/api/crash-groups). This allows people supporting the application to identify which crashes are happening more frequently, helping them to prioritize fixes based on impact to application performance.

This means crash reporters can decrease the time and energy a team has to spend on support while also ensuring that they are improving the performance and stability of their application for their users.

Crash reporters also serve the critical role of an early warning system for critical issues that users may encounter while using an application. Many tools have the ability automatiaclly send customized alerts to via email or to messaging tools (e.g., [Slack](../../introduction/development/integrating-with-tools/messanger-apps/slack), [Teams](../../introduction/development/integrating-with-tools/messanger-apps/microsoft-teams), [Discord](../../introduction/development/integrating-with-tools/messanger-apps/discord)) that let developers know about critical issues before users can report them.

### A Boost to Development

As crash reporters have become increasingly common as support tools, they have also become more popular as a part of the pre-release development process.

Teams that take advantage of crash reporting during development can effectively identify and address defects in their code pre-launch.

Crash reporters help teams automate identifying, logging, and fixing more crashes during testing. Often crash reporter tools - like [BugSplat](https://www.bugsplat.com) - integrate directly with a team's defect tracking tool (e.g., [Jira](../../introduction/development/integrating-with-tools/issue-trackers/jira) or [Github Issues](../../introduction/development/integrating-with-tools/issue-trackers/github-issues)) to further streamline the process of fixing bugs pre-launch.

Because bugs are cheaper and easier to fix during development, leveraging a crash reporter to help identify and fix bugs before they're shipped effectively lowers development costs and improves the stability of shipped software.

### Final Thoughts

Developers and support teams use crash reports like [BugSplat](https://www.bugsplat.com) to:

* Understand the health of their software applications.
* Improve the stability of their code
* Get early warnings when there's an issue that needs their attention
* Spend less time and energy fixing defects

Start using [BugSplat for free](../../administration/billing/free-trial). BugSplat works cross-platform ([25+ SDKs](../../introduction/getting-started/integrations)), is [simple to setup](../../introduction/getting-started) and configure, and our [support team](../../administration/contact-us) is top-notch.
