Crashpad

Crashpad is an open-source client library for capturing crash data inside software and sending it to a server chosen by the embedding team. It best suits developers who need control over collection, report contents, and infrastructure rather than a turnkey monitoring service. The tradeoff is substantial integration and privacy responsibility, especially when reports can contain process memory.

Overview

Crashpad installs as part of a client application. After a registered process fails, its handler snapshots the process, writes a crash dump, and can transmit it upstream when configured. Applications can also request process-state dumps on demand, which makes Crashpad useful for targeted diagnostics as well as unexpected failures.

This is a client-side component, not a complete crash-reporting backend. The application supplies the collection-server URL, while a separate processor is planned without a stated completion timeline. Teams therefore need to operate or select the receiving and analysis side themselves.

Key features

Reports generally contain loaded modules, thread registers and stack memory, selected operating-system state, and memory referenced by registers and stacks. That breadth can expose the context needed to investigate difficult faults, but it also increases the chance of capturing sensitive information. The application must obtain and honor user consent before uploading.

Key/value annotations and custom minidump streams let developers add release, account, or workflow context specific to their application. Crashpad uses the Windows minidump format with extensions for those additions. Its handler reads client address spaces through accessors intended to validate pointers and enforce access bounds.

Uploads use the Breakpad wire protocol in MIME multipart requests, optionally gzip-compressed. The embedding client chooses 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, while retry behavior is expected to change. Crashpad will not upload an unregistered process, although child processes can inherit registration on some operating systems.

Pricing

Crashpad is open source and free. The Crashpad plan costs free, with no published seat, storage, event, or retention limits. That price covers the client software; infrastructure for receiving, processing, storing, and securing reports remains part of the implementer's responsibility.

Platforms

Crashpad supports Android, iOS, Linux, macOS, and Windows. Project status describes completed clients for macOS, Windows, Fuchsia, and Linux, including Android and Chromium OS. iOS work has begun with important differences: 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.

Outside Chromium, integration depends on mini_chromium; Chromium builds use Chromium's base library. Build instructions are provided, and Crashpad Buildbot performs automated builds and tests.

Who it's for

Crashpad fits application and game teams that can embed native client code, run a collection service, and define a clear consent and data-retention policy. It is particularly appropriate when custom metadata, on-demand dumps, and control over the upload destination matter more than a hosted dashboard.

It is a poor fit for teams seeking an immediately managed monitoring product, built-in report processing, or a simple no-code integration. iOS teams should also account for the handler's in-process design and crash categories it cannot capture.

Pros and cons

Pros

• Free and open source: there is no software license charge or stated usage cap.
• Rich diagnostic context: dumps include stack, register, module, and selected memory data, with on-demand capture available.
• Extensible reports: annotations and custom minidump streams support application-specific investigation.
• Deployment control: the embedding team selects the collection server and transport.
• Broad reach: clients cover major desktop and mobile platforms.

Cons

• Backend is yours to provide: Crashpad does not deliver a finished processor or hosted analysis service.
• Privacy work is unavoidable: process memory may contain sensitive data, so consent and handling policies are integration requirements.
• Upload behavior is constrained: the documented one-per-hour limit and aborted failed uploads may not suit high-volume or unreliable environments.
• iOS coverage has gaps: some crash groups are not catchable and conversion occurs after intermediate dump creation.

Alternatives

For a self-built, self-hosted crash-reporting library and tool suite, choose Breakpad instead. Choose Backtrace if a freemium service with a free developer tier, monthly error allowance, retention, and storage is preferable. BugSplat is a better match for hosted crash management with a free tier offering user logins, storage, monthly crash capacity, and retention. Choose BugSnag for a freemium monitoring product with a free plan, trial, broad platform coverage, and integrations. AccelByte Development Toolkit suits game teams wanting freemium build, playtest, and issue-reporting workflows. GameAnalytics is aimed at game analytics dashboards and reporting rather than a client crash library. Tombstack is another freemium option for teams operating within its listed concurrency and retention limits. Embrace targets mobile teams wanting hosted errors, crashes, and basic performance monitoring on a usage-based free tier. Browse Game Crash Reporting Software for the wider category.

Verdict

Choose Crashpad when your team wants a no-license-cost, embeddable capture layer with customizable diagnostics and control of where reports travel. Look elsewhere when you need hosted processing, dashboards, managed retention, or less responsibility for consent, infrastructure, and platform-specific edge cases.