Skip to main content

Crashpad crash reporting

You already have Crashpad. Now get answers out of it.

Point your Crashpad handler at BugSplat and the minidumps you already capture get symbolication, grouping, alerting, and stability trends, with no new SDK to integrate.

Why BugSplat for Crashpad

Keep the Crashpad you already ship. Point it at BugSplat and your minidumps get symbolication, grouping, alerts, and stability trends.

01 · It lands

Your Crashpad handler catches a crash. You find out first.

If Crashpad is already in your app, you are most of the way there. Point the handler at BugSplat's upload URL, set four annotations, and every minidump uploads with its attachments.

  • Works with your existing Crashpad handler: change the upload URL and set four annotations
  • Annotations and attachments come through with every report
  • Windows, macOS, and Linux Crashpad clients in one dashboard
A crash report in BugSplat with application, group, exception, platform, and the user's feedback - how Crashpad reports arrive

02 · It groups and resolves

A report count is not a bug count.

BugSplat groups Crashpad reports your way: your rules decide which call stacks count as the same bug, and the list is ranked by how many people each one hit. Minidumps resolve against the symbols you upload at build time, so Crashpad's raw dumps become readable stacks with function names and line numbers.

  • Thousands of reports collapse into a short list of distinct bugs
  • Function names and line numbers, not memory addresses
  • OS, hardware, and build on every report
A symbolicated active thread in BugSplat with the faulting frame expanded to its file, line, arguments, and locals

03 · It tells you

Stay ahead of the next one.

Alerts for Crashpad reports reach Slack, Discord, or Teams the moment something spikes. Version-over-version analytics show whether each release is more stable than the last.

  • Regressions flagged when a fixed crash comes back
  • Daily and weekly digests with the highlights
A BugSplat new group alert in Discord with the crash group and stack trace

What makes BugSplat different

Crash reporting built for native code.

The part of Crashpad crash reporting that's hard is the part we've always done.

Native from the start

BugSplat has been turning minidumps into readable stacks since 2005. Symbols, PDBs, and native crashes are the core of the product.

A bill that holds still

Flat monthly plans with fixed limits. A spike in crash volume after a release doesn't change your bill.

Answered by the people who build it

Email support with a Crashpad question and you'll hear back from an engineer who builds BugSplat, usually the same day.

Crashpad setup

Wire up Crashpad and read a real stack the same day.

Add the SDK and upload symbols with each build. If you get stuck, contact support and you'll reach the engineers who build BugSplat.

By clicking "Accept", you agree to the storing of cookies on your device. View our Privacy Policy .