Get started

Conceived initially by Microsoft for crash reports on Windows, minidumps have become an accessible format for all sorts of native crashes. You can generate and upload minidumps yourself using Crashpad or Breakpad, use a higher-level SDK for platforms with built-in support for native crashes like Cocoa or Electron, and use them to triage issues with C++.

Don’t bother guessing


A minimalist illustration of a user interface that alludes to the Crashpad & Breakpad error tracking information features of Sentry.

Collect native crash events in your issue stream, grouped by their crash location.


See detailed stack traces with resolved function names, file location, and CPU register values.


Assign issues to the engineers — or teams — who wrote the code that broke everything. (Obviously that would never, ever be you.)

Bugs are dumb. You probably aren’t.


Record environment and state details so you can recreate bugs, whether you’re targeting Windows, macOS, Linux, iOS, or Android.

Use Sentry’s tag distribution graph to isolate and prioritize any error by seeing how often it occurs in context.

  • “How actionable is this error? Can I (please) just ignore it?”
  • “Is the error isolated to users on Windows 10?”
  • “How many splines were being reticulated?”
  • “Was the power level over 9000?”
  • “Did the waxing gibbous cause the problem?”

See the big picture And the little pictures. Unless you need glasses,
in which case you should see an optometrist.


Event trails detail what the app was doing before any error occurred.

An illustration depicting a sequence of events. A user types F, Ü, N, scrolls down, clicks a checkbox, then an error happens due to encoding problems.
A computer screen showing a modal window with the text “Everything is not fine,” indicating you are debugging an error.

No WiFi? No problem-fi. Record events even when devices are offline or in airplane mode, then send errors as soon as connection is regained.

Learn more

Is the problem actually not in your code at all, but instead maybe caused by something another team wrote that broke the API you’re using? Sentry can tell you that too.

An illustration of email, text, and chat notification. In the center is a flame icon representing alerts from exception handling.

Is your data secure?
You better believe it.


Just look at all the high-quality security features all accounts get, regardless of plan.

  • Two-Factor Auth
  • Single Sign On support
  • Organization audit log

Learn more about Security

  • Privacy Shield certified
  • PII data scrubbing
  • SSL encryption

Learn more about Privacy

Crashpad & Breakpad debugging that looks nice too Have some self-respect while you monitor errors

A screenshot of the Sentry crash reporting dashboard
1,000,000 developers at over 30,000 companies already use Sentry. Why don’t you?