# Sentry for Crashpad

> Collect native crash events in your issue stream & group them accordingly with Sentry for Crashpad. Learn how to get started for free here.

**URL:** https://sentry.io/for/crashpad/

---

Your apps are crashing everywhere, but you can easily capture all that crash data thanks to the magic of Crashpad.

**Documentation:** [https://docs.sentry.io/platforms/native/guides/crashpad/](https://docs.sentry.io/platforms/native/guides/crashpad/)

## Install

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](https://docs.sentry.io/platforms/native/guides/crashpad/), use a higher-level SDK for platforms with built-in support for native crashes like [Cocoa](https://docs.sentry.io/platforms/apple/) or [Electron](https://docs.sentry.io/platforms/javascript/guides/electron/), and use them to triage issues with C++.

See the [Crashpad docs](https://docs.sentry.io/platforms/native/guides/crashpad/) for full setup options.

## Features

### Stop Guessing

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.)

### See The Big Picture

Event trails detail what the app was doing before any error occurred. Is the problem actually outside of your code? Was it caused by something another team wrote that broke the API you're using? Sentry can tell you that too.

### No WiFi? No Problem.

Record events even when devices are offline or in airplane mode, then send errors as soon as connection is regained.

---

*Source: [sentry.io/for/crashpad/](https://sentry.io/for/crashpad/)*