Firefox Crash History

Why clean Firefox Crash History?

• Old submitted crash-report receipts accumulate after repeated browser or extension crashes, so the Crash Reports folder keeps growing even though those reports were already sent and you only notice wasted AppData disk space
• Telemetry event files in the events and glean folders can build up when Firefox runs for months or spends time offline, leading to unexpectedly large Mozilla folders in Roaming\AppData
• A long history of stale submitted entries makes about:crashes harder to review because old report IDs crowd out recent failures you are actually trying to troubleshoot
• Corrupted or partially written crash event files after an unclean shutdown can leave behind diagnostic leftovers that no longer help Firefox but remain on disk and may make crash-history folders look active long after the problem passed
• Systems with frequent startup crashes or unstable add-ons can generate many report receipts in a short time, producing repeated small writes in AppData and a visibly bloated Crash Reports directory
• Cleaning older telemetry logs trims local diagnostic history without affecting bookmarks, tabs, settings, or login data, which is useful when you want to reduce stored browser diagnostics before making a support image or profile backup

Common questions about Firefox Crash History

Download Kudu and reclaim your disk space.

Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.