Quick answer: For most Godot 4 games, Bugnet is the easiest complete option: a single GDScript autoload that captures engine and script errors with logs, a screenshot and device details, plus an in-game report widget and a tracker. Sentry is the pick if you need native crash capture across desktop, mobile and web or already use Sentry. Codecks fits teams that plan in Codecks and want player feedback cards. Rolling your own on Godot's logging is possible but costs more than it looks.
Godot developers ask about crash reporting constantly, because the engine ships without a hosted service and many crash tools were built for Unity and Unreal first. In 2026 there are a handful of solid choices. Here is how they compare for a Godot 4 project.
At a glance
| Option | How it installs | What it captures | Player reports | Price |
|---|---|---|---|---|
| Bugnet | One GDScript file as an autoload; no GDExtension binaries | Engine, script and fatal errors with recent logs, screenshot, device and build | Built-in widget | Free for 100 reports; $19 or $79/mo flat |
| Sentry | Addon in addons/sentry | Runtime errors (script and shader errors) and native crashes on Windows, Linux, macOS, iOS, Android; web via its JavaScript SDK | Not its focus | Free for 1 user and 5,000 errors/mo |
| Codecks User Reports | Godot 4 plugin | What players submit | Yes, as Codecks cards | Part of Codecks plans |
| DIY | Your own logger and upload code | Whatever you build | Whatever you build | Your time |
Bugnet
Bugnet's Godot SDK is a single file, BugnetSDK.gd, registered as an autoload named Bugnet (a one-line installer does both). It is plain GDScript, so there are no native binaries to build for each export platform. It watches the engine log and files errors, script errors and fatal errors automatically (fatal ones as critical crashes), with recent log lines, a screenshot of the viewport when screenshot capture is on, the platform, OS, hardware, game version and the last scene's load time.
Players report everything else through a widget built from Control nodes that picks up your project's theme; you open it with Bugnet.show_widget() and can change its labels and categories. Reports land in a tracker with grouping, crash-free sessions per build, a public known-issues page and integrations with GitHub, Linear, Jira, Discord and more. Free to start; setup steps are in the Godot SDK docs.
Sentry
Sentry's Godot SDK is the strongest choice for native crash coverage: it captures Godot runtime errors such as script and shader errors and provides native crash reporting on Windows and Linux, macOS 12+, iOS 15+ and Android, with web support through Sentry's JavaScript SDK. It is a natural fit if your studio already uses Sentry. Its pricing is event-based, and player bug reporting and public pages are not its focus. See Sentry vs Bugnet.
Codecks User Reports
If your team plans in Codecks, its Godot plugin lets players send feedback that becomes a card in your deck. It is a feedback inlet rather than a crash reporter, so it does not capture errors players never mention. See Codecks vs HacknPlan.
Rolling your own
Godot writes logs to user://logs/godot.log on desktop by default, rotating old files, and recent Godot 4 versions let you register a custom Logger with OS.add_logger() to receive errors as they happen. With an HTTPRequest node you could post them to a server. The hard parts come after: grouping duplicates, attaching screenshots and hardware details, handling offline players, storing and searching reports, and giving players a form. Most teams find a hosted tool cheaper than maintaining that. Our guide to where Godot crash logs live covers the manual route.
Which should you pick?
- Most Godot indies: Bugnet, for crash capture plus player reports and a tracker in one place.
- Native crash coverage or an existing Sentry setup: Sentry.
- Teams planning in Codecks: Codecks User Reports, alongside a crash reporter.
Using C# in Godot? See crash reporting for Godot C# games.
Frequently asked questions
What is the best crash reporter for Godot?
For most Godot 4 games, Bugnet is the most complete option: a single GDScript autoload that captures engine and script errors with logs and device details and includes an in-game report widget and tracker. Sentry is the best choice for native crash coverage or teams already on Sentry.
Does Sentry support Godot?
Yes. Sentry's Godot SDK captures Godot runtime errors and provides native crash reporting on Windows, Linux, macOS, iOS and Android, with web support through its JavaScript SDK.
Does Bugnet need GDExtension binaries?
No. Bugnet's Godot SDK is plain GDScript, added as an autoload, so there is nothing to compile for each export platform.
Where does Godot write its logs?
On desktop platforms Godot writes logs to user://logs/godot.log by default, keeping a number of rotated older logs. The user:// folder lives under the user's application data directory.
Can players report bugs from inside a Godot game?
Yes. Bugnet's Godot SDK includes a themeable report widget, and Codecks offers a Godot plugin for player feedback.
Godot gives you a great engine and leaves crash reporting to you. Pick the option that leaves you time to make the game.