Crashpad

Crashpad is an open-source client library for developers who need crash capture inside applications they control. It suits teams prepared to operate or integrate a collection service and to make privacy decisions themselves. Its technical reach is broad, but it is not a finished crash-analysis product.

Overview

Crashpad embeds into an application and uses a handler to snapshot a registered process after a crash, save the resulting dump, and optionally transmit it to a configured server. It also supports on-demand process-state dumps for diagnostics. This makes it a strong foundation for teams that want ownership of capture and transport, rather than a hosted dashboard selected for them.

The important qualification is architectural: Crashpad is client-side. A crash-report processor is planned, but no completed processor is included, so teams need their own collection and processing arrangement. Outside Chromium, integration depends on mini_chromium; Chromium builds use Chromium’s base library.

Key features

Crash dumps generally contain loaded modules, thread registers and stack memory, selected operating-system state, and selected memory referenced by registers and stacks. That breadth can expose the context needed to diagnose difficult failures, while also creating a real privacy obligation because process memory may contain sensitive data.

Applications can attach key/value annotations and custom minidump streams, allowing product-specific context to travel with a report. The format is Windows minidump with Crashpad extensions. The handler reads client address spaces through accessors intended to validate pointers and enforce access bounds.

The embedding application chooses the collection-server URL. Crashpad uploads with the Breakpad wire protocol as MIME multipart requests, optionally gzip-compressed, over HTTP or HTTPS; HTTPS is the sensible choice for protecting data in transit. The documented strategy permits one upload per hour and aborts failed uploads, with retry behavior expected to change. Only processes registered with the handler are uploaded, although registration can be inherited by child processes on some operating systems.

Consent belongs to the client application: it must obtain and honor permission before sending reports. On iOS, work on a client has begun; the handler runs in-process, cannot catch some crash groups such as out-of-memory failures, and writes intermediate dumps that are converted to minidumps later. Project support is provided through the issue tracker and crashpad-dev mailing list, while Crashpad Buildbot performs automated builds and tests.

Pricing

Crashpad is free and open source. The Crashpad plan costs free. There are no stated seat, quota, trial, or renewal terms. Free licensing removes a software fee, but it does not remove the engineering and infrastructure work required for a collection server, processing pipeline, consent flow, and data governance.

Platforms

Crashpad supports Android, iOS, Linux, macOS, and Windows. Project status also describes completed crash-reporting clients for macOS, Windows, Fuchsia, and Linux, including Android and Chromium OS; iOS remains subject to the limitations of its in-process, developing client.

Who it's for

Choose Crashpad when your development team needs embedded capture, custom annotations, configurable transport, and control over where reports are sent. It is particularly appropriate for software spanning desktop and mobile platforms, or for organizations that can operate their own backend and define their own consent policy.

Look elsewhere when you need a ready-to-use crash processor, hosted retention, dashboards, or a packaged support workflow. Crashpad’s client component alone does not provide those services.

Pros and cons

Pros

• Broad platform coverage: Android, iOS, Linux, macOS, and Windows enable a common capture approach across varied applications.
• Control over report content: annotations and custom minidump streams let teams add application-specific diagnostic context.
• Flexible transport: the application selects its server and can use HTTP or HTTPS with the Breakpad protocol.
• No software charge: the open-source plan avoids per-seat or event pricing.

Cons

• No completed processor: teams must supply the service that receives and makes sense of reports.
• Privacy burden: dumps can contain arbitrary process-memory data, so consent and handling controls are the application’s responsibility.
• Limited documented upload behavior: one-upload-per-hour throttling and aborted failed uploads may not suit urgent or high-volume reporting.
• iOS gaps: the developing client misses some crash groups and uses an intermediate-dump conversion path.

Alternatives

For a broader directory of options, see Game Crash Reporting Software.

• AccelByte Development Toolkit is a freemium, multi-platform choice with unlimited basic seats and build and playtest workflows.
• Backtrace is better suited when a hosted freemium service with monthly error capacity, retention, and storage is preferable.
• BugSnag fits teams seeking a freemium service with a free tier, trial, and broad integration coverage.
• BugSplat offers a free tier with three logins, 100GB storage, 15,000 crashes per month, and one-month retention.
• GameAnalytics is an alternative for game teams wanting dashboards, funnels, cohorts, retention, and real-time reporting.
• Breakpad is the closest open-source alternative for teams wanting self-built and self-hosted crash-reporting components.
• Tombstack is a freemium option for Linux, macOS, web, and Windows applications.
• Unity Version Control is a freemium development-platform option with unlimited cloud seats and a 25GB storage allowance in its free tier.

Verdict

Crashpad is a good choice for developers who want free, embeddable crash capture and are willing to own the server, processing, and consent work around it. Its metadata controls and platform coverage are compelling. Choose a hosted alternative instead if you need finished report analysis, retention, and operational tooling without building that backend yourself.