This page's audience our own tag's counts — open to see them

Period

–Visits

–Page views

–Clicks to vendors

–Time on page

–Reading now

Clicks to vendors, by tool

Top countries

Devices

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

PLCrashReporter

Free#11 of 25 in Game Crash Reporting Software

PLCrashReporter: A focused, open-source library for detailed iOS and macOS crash reports. Ranked #11 of 25 in Game Crash Reporting Software by our editors (7.2/10); pricing: Open source; best for open-source Apple crash-report collection.

7.2/10Editor score

Try PLCrashReporter

PLCrashReporter7.2 Try PLCrashReporter

At a glance

Editor score
7.2 / 10
Pricing
Open source
Best for
Open-source Apple crash-report collection
Paid from
Free
Founded
2008
Facts checked
22 Sep 2026

Where it wins
- Captures all-thread backtraces and full crashed-thread register state
- Supports DWARF and Apple Compact Unwind stack unwinding
- Integrates through CocoaPods, Carthage, Swift Package Manager, or manually
Where it doesn't
- Focused on iOS and macOS rather than broad platform coverage
- Requires local decoding and text-formatting workflows
- It is a library, not a hosted crash analytics service

Our verdict on PLCrashReporter

PLCrashReporter is an open-source in-process crash-reporting library for iOS and macOS applications. It detects crashes and records application, system, process, and thread information, including backtraces for all active threads and the full register state for the crashed thread. Its output is protobuf-encoded, giving developers a detailed report format for downstream handling. The library is suited to teams that want direct control over crash collection and decoding rather than a hosted crash analytics service.

Its strongest technical advantage is the depth of the captured report. PLCrashReporter supports DWARF and Apple Compact Unwind stack unwinding, local crash-report decoding, and text formatting. The included plcrashutil utility can convert crash reports, while Apple’s atos tool can symbolicate the resulting output. This makes the product a practical fit for teams building their own Apple crash-report pipeline and needing more than a basic exception message or single-thread trace.

Integration is available through CocoaPods, Carthage, Swift Package Manager, or manual inclusion in an Xcode project. The published positioning also reflects a mature open-source project, founded in 2008, with Microsoft identified as the vendor. Choose PLCrashReporter when detailed in-process collection, local processing, and Apple-specific integration are priorities. Choose another option when you need a hosted dashboard, broader platform coverage, event quotas, or game-engine integrations as part of the crash-reporting product.

Your product? Our editors can test PLCrashReporter in depth and publish a review, labelled as paid · from $149/mo →

PLCrashReporter pricing

Plans Open sourceFree Free to use — no paid tier required for the core job.

See plans on github.com

PLCrashReporter fact sheet

Free plan	Not verified
Paid from	Free
Monthly event limit	Not verified
Unity support	Not verified
Unreal support	Not verified
Source maps	Not verified
Breadcrumbs	Not verified
Player context	Not verified
Crash-free users metric	Not verified
Deployment	Mobile, Desktop
Platforms	iOS, macOS
Built for	Solo, Small business, Mid-market, Enterprise (editorial estimate)
Integrations	3 integrations: CocoaPods, Carthage, Swift Package Manager
Pricing	Open source
Website	github.com
Facts checked	22 Sep 2026

PLCrashReporter integrations

PLCrashReporter lists 3 integrations on its own site.

CocoaPods
Carthage
Swift Package Manager

Alternatives to PLCrashReporter

See all PLCrashReporter alternatives →

Used PLCrashReporter? Be the first to review it

The editor score above is our own research. What this page doesn't have yet is a reader's view — what you used PLCrashReporter for, what worked and what didn't. No stars are seeded and no review is paid for; an editor reads every one before it appears.

Write a reviewTwo minutes · verified accounts only · read by an editor before it appears

Reviews come only from verified accounts. Sign in or create an account first — your e-mail is never shown.

Title

Your review

0 characters · at least 80, up to 3,000

Pros (optional · one per line)

Cons (optional · one per line)

Your name (shown with your review)

Role (optional)

Company (optional)

How long have you used it?

I've used PLCrashReporter myself and this is my honest opinion — nobody paid or asked me to write it.

Posted from your verified account. Reviews appear after an editor reads them, usually within two working days.

Featured on iTechGuides

PLCrashReporter is listed in our Game Crash Reporting Software directory. Add the badge to your site — it links back to this page.

<a href="https://www.itechguides.com/products/plcrashreporter/"><img src="https://www.itechguides.com/best/badge/plcrashreporter.svg" alt="Featured on iTechGuides" width="230" height="46"></a>

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated 7 Oct 2026 · How we research and update