How do I know if my game has hidden crashes?

If you don't have crash reporting, you have hidden crashes by definition, and even with it, watch for the gap between reports and reality. The most definitive sign is meta: if you don't have crash reporting, you can't see your crashes, so they're hidden, a game without field crash capture is almost certainly crashing for players without your knowledge, since most crashes go unreported, making the absence of crash reporting a guarantee of hidden crashes. Other signs (if you're relying on reports): churn and negative reviews you can't fully explain (the loss and complaints have a cause you're not seeing, hidden crashes), and a gap between how many players seem to hit problems (from churn, reviews, indirect signals) and how few report (since most crashing players don't report, a large gap means hidden crashes). The way to eliminate hidden crashes is to capture crashes automatically from the field, which records every crash with full context regardless of whether players report, turning hidden crashes into visible data, when you do, you typically discover crashes you had no idea about affecting many players, confirming that hidden crashes were the norm. So if you don't have crash reporting, you have hidden crashes (almost certainly); if you rely on reports, the gap between problems hit and reported (and unexplained churn/reviews) signals hidden crashes. The reliable way to know, and to eliminate the hiddenness, is automatic crash capture, which makes the hidden crashes visible. The key insight is that hidden crashes are the default without field capture (since most crashes go unreported), so the question isn't really whether you have hidden crashes but whether you've made them visible, and if you haven't (no crash reporting), you have hidden crashes you need to surface.

Why are most crashes hidden from developers?

Because most players who crash never report it, so if you rely on reports (or have no crash reporting), the large majority of crashes are invisible to you. A player who hits a crash is already frustrated, and reporting requires effort (finding how to report, describing the problem) that most won't expend, especially when they doubt it'll lead to a fix, so they just stop playing (and maybe leave a review) rather than reporting. This means the typical crash goes unreported, the player experiences it and leaves or complains, but you get no direct evidence, so the crash is hidden. Crashes are also frequently device- or condition-specific (happening on players' hardware and in real-world conditions you don't have), so you can't reproduce them yourself, hidden from your testing too. The combination, most crashes unreported and many unreproducible, means crashes happen in a blind spot if you don't capture them directly: players experience them, churn or complain, but you can't see what's crashing or for how many players. This is why hidden crashes are the norm: the reporting rate is low (most players don't report) and your own testing can't reproduce many field crashes, so without automatic field capture, you see only the small, unrepresentative fraction of crashes that players bother to report, while the majority, often including the ones affecting the most players, are hidden. The solution is automatic crash capture from the field, which doesn't depend on players reporting or on you reproducing: every crash is recorded with full context (stack trace, device, version, breadcrumbs) the moment it happens, so the crashes that would otherwise be hidden become visible. So most crashes are hidden from developers because most players don't report crashes (the reporting rate is low) and many crashes can't be reproduced in your own testing (they're field-specific), so without automatic field capture you're blind to the majority of your crashes, which is why hidden crashes are the default and why capturing crashes from the field, which removes the dependence on reports and reproduction, is essential to seeing your real crash situation rather than the tiny reported tip of it.

How do I find crashes players don't report?

Capture crashes automatically from the field, which records every crash regardless of whether players report it, surfacing the unreported majority. This is the only reliable way to find crashes players don't report, since by definition they're not telling you, so any approach that depends on reports will miss them. With automatic capture, when a crash happens on any player's device, it's recorded with full context (stack trace, device, OS, version, breadcrumbs) and sent to you without the player doing anything, so you learn about the crash even though the player said nothing and simply moved on (or left). This typically reveals that crashes you had no idea about are affecting many players, since the silent majority becomes visible, when developers first add crash reporting, they're often surprised by how many crashes were happening that they never saw, confirming that hidden crashes were the norm. Once captured, the crashes are organized for action: grouped by signature (so many reports of the same crash collapse into one issue with a count), ranked by affected players (so the high-impact crashes surface), and tagged with version (so you can see regressions and verify fixes), turning the previously-hidden crashes into actionable data you can prioritize and fix. So you find crashes players don't report by capturing them automatically from the field, which removes the dependence on player reporting (the reason the crashes were hidden) and records every crash with the context needed to diagnose it, making the unreported majority visible. This is foundational, you can't fix crashes you can't see, and since most crashes go unreported, automatic field capture is what gives you visibility into your real crash situation (rather than the small reported fraction), revealing the hidden crashes that are silently driving churn and bad reviews so you can fix them. The contrast is stark: relying on reports shows you a tiny, unrepresentative slice of your crashes (and misses the ones affecting the most players, who churn silently), while automatic capture shows you all of them, with the context and impact ranking to act, which is why capturing crashes from the field is the essential first step to addressing crashes that players don't report, it turns the hidden majority into visible, fixable problems.

Signs Your Game Has Hidden Crashes

Quick answer: Watch for unexplained churn and bad reviews, a gap between problems hit and reports, and, most tellingly, having no crash reporting, which guarantees hidden crashes. Most crashing players never report.

Hidden crashes, crashes happening to players that you can't see, are the norm rather than the exception, since most crashing players never report. Here are the signs your game has hidden crashes.

Churn and Bad Reviews You Can't Fully Explain

A sign is churn and negative reviews you can't fully explain by what you can see, players leaving or complaining about the game being buggy or crashing, while your visible crash data (if any) doesn't account for it. Unexplained technical churn and reviews point at hidden crashes driving them invisibly.

Bugnet captures crashes from the field, removing the hiddenness. Churn and bad reviews you can't explain are a sign of hidden crashes, since the loss and complaints have a cause you're not seeing, and capturing crashes from the field reveals the hidden crashes behind them, turning the unexplained into the explained.

A Gap Between Problems Hit and Reports

A telling sign is a gap between how many players seem to be hitting problems (from churn, reviews, indirect signals) and how few actually report, since most crashing players don't report. A large gap means crashes are happening that aren't being reported, hidden from you if you rely on reports.

Bugnet captures crashes from all affected players, revealing the true number versus the few who report. The gap between problems hit and reports is a sign of hidden crashes, and it's only visible if you capture crashes automatically (showing the true affected-player count versus the small fraction who report), which exposes how many crashes are hidden when you rely on reports alone.

Not Having Crash Reporting at All

The most definitive sign is meta: if you don't have crash reporting, you have hidden crashes by definition, you can't see your crashes, so they're hidden. A game without field crash capture is almost certainly crashing for players without your knowledge, since most crashes go unreported, making the absence of crash reporting a guarantee of hidden crashes.

Bugnet captures crashes automatically from the field, eliminating the hiddenness. Not having crash reporting is the definitive sign of hidden crashes, since without it you can't see your crashes and most go unreported, so the crashes are hidden by definition, the fix is simply to capture them, which turns hidden crashes into visible, actionable data.

Watch for unexplained churn and bad reviews, a gap between problems hit and reports, and, most tellingly, having no crash reporting, which guarantees hidden crashes. Most crashing players never report.