How do I raise my game's crash-free rate?

Fix the crashes affecting the most sessions, since those move the number the most. Capture crashes from the field, rank them by occurrence, and fix the top offenders, each high-impact fix removes a chunk of crashing sessions and raises the crash-free percentage. A few well-chosen fixes can lift the rate substantially, far more than fixing many rare crashes.

What is a good crash-free rate to aim for?

For most indie games, 99% of sessions crash-free is a reasonable baseline and 99.5% or higher indicates a polished game, but the right target varies by genre and platform. More important than hitting a specific number is the trend: a crash-free rate that climbs release over release, as you fix the top crashes, shows your stability is genuinely improving.

How to Improve Your Game's Crash-Free Rate

Q: How do I track whether my crash-free rate is improving?

Track it over time and across versions using version-tagged crash data. Each release should show the rate climbing as fixes land, and version comparison reveals whether a release improved or degraded stability. A fixed crash's occurrences dropping to zero on the new build confirms the fix worked, and a release that lowers the rate flags a regression to investigate.

Quick answer: Your crash-free rate, the percentage of sessions without a crash, improves when you fix the crashes affecting the most sessions, since those move the number the most. Capture and rank crashes by occurrence, fix the top offenders, and track the rate across versions to confirm it's climbing. A few high-impact fixes can lift the rate substantially.

Crash-free rate is one of the clearest measures of your game's stability, and unlike a vague sense that 'the game is buggy,' it's a number you can deliberately move. Improving it isn't about heroics; it's about targeting the specific crashes dragging it down and confirming the number rises as you fix them.

Find What's Dragging the Rate Down

Your crash-free rate is lowered by crashes in proportion to how many sessions they affect. So a handful of high-occurrence crashes usually account for most of the gap between your current rate and a higher one. To improve the rate, you first need to see which crashes are doing the most damage, which means capturing crashes from the field and ranking them by occurrence.

Bugnet's crash grouping and occurrence data show you exactly which crashes affect the most sessions, connecting the aggregate metric (your crash-free rate) to the specific crashes behind it. The top of that ranked list is where your crash-free rate is leaking, and where fixing has the most effect.

Fix the High-Impact Crashes

Because the rate is moved most by the most frequent crashes, fix from the top of the occurrence list. Each high-occurrence crash you resolve removes a chunk of crashing sessions, raising the percentage that are crash-free. Fixing one crash that hits 5% of sessions does more for your rate than fixing ten crashes that each hit 0.1%.

Use the stack trace and device context to fix each top crash, and remember that hardware-specific crashes (clustered on a GPU or OS) can be a big slice of the rate on affected configurations. Knocking out the dominant crashes is the direct lever on the metric.

Track the Rate Across Versions

Improving the rate is only meaningful if you can confirm it's rising, which means tracking crash-free rate over time and across versions. Each release should show the rate climbing as your fixes land, and version comparison reveals whether a release improved or degraded stability. A fixed crash's occurrences dropping to zero on the new version is the proof your fix worked.

Version-tagged crash data lets you watch the rate per release and catch regressions (a new release that lowers the rate is a regression to investigate). Treating crash-free rate as a tracked metric you move release over release, by fixing the top crashes and verifying the climb, is how you steadily and measurably improve your game's stability.

Crash-free rate rises fastest when you fix the crashes affecting the most sessions. Rank by occurrence, fix the top, and track the rate by version to confirm it's climbing.