Unity Bug Reporting Tools Compared — Engine-Built-In to In-House

Search "Unity bug reporting" and you'll land on tools from completely different categories — crash reporters, error monitoring, mobile SDKs, recording tools. Line them up without sorting by category first and you get the illusion that they're all roughly the same thing competing for the same job. This post sorts by five forks and sticks to what's actually confirmed for each category.

The comparison criteria

Five things actually decide which category fits a given team.

1. Does it run in builds? Editor-only tools are off the table for QA builds and production.
2. Can you capture after the fact? Do you have to see the bug and then press a button, or does recording need to already be on?
3. Is there video? A screenshot and a playable clip carry very different amounts of information.
4. Does it sync with game state? Can you tell which scene and which log line a given second of footage corresponds to?
5. Does it lead into an issue tracker? How many steps stand between a capture and a ticket?

The categories

Engine built-in — Unity Cloud Diagnostics / User Reporting

Unity Cloud Diagnostics is being folded into Unity 6.2+'s built-in Diagnostics. It ships Crash and Exception Reporting plus User Reporting (com.unity.cloud.userreporting), whose reports carry metadata, events, sampled metrics, screenshots, and attachments. Being bundled with UGS means no extra cost. There's no video capture, though. What to check when this transition forces a re-evaluation gets its own post.

General-purpose error monitoring — Sentry

Sentry's Unity SDK has a free tier and attaches breadcrumbs and context around each exception. Screenshots exist; video doesn't. Console log support is gated to the Enterprise plan. Sentry solves "aggregate and trend production exceptions," not "collect evidence for a bug a human just watched happen." That boundary gets its own post too.

Mobile app SDKs — Bugsee, Instabug

Bugsee runs Lite (free), Pro ($99/mo), and Custom tiers, keeps a dedicated Unity landing page, and captures video, network traffic, and logs together — the broadest feature set on this list. Instabug (rebranded to Luciq in 2026) doesn't publish pricing — demo booking only — and is built for mobile apps generally, not games specifically.

Crash-only — BugSplat, Backtrace

BugSplat starts free and scales into paid plans, though specific numbers aren't published. Backtrace (Sauce Labs) ships a dedicated backtrace-unity SDK, also without public pricing. Both are strong at "why did it crash" — bugs that never throw (broken UI, balance issues, physics glitches) are outside what they're built for.

Free combo — Unity Recorder, OBS

Unity Recorder is a free editor package, but editor-only — it can't ship in a build. OBS's replay buffer is free and records continuously outside the game, but there's no way to sync it with logs or game state. Combined, the two carry a QA team surprisingly far; where that stops paying off depends on team size and report frequency.

In-house

Capturing inside the game process is the only way to satisfy all four technical forks at once — runs in builds, captures after the fact, has video, syncs with game state — at the cost of implementation difficulty. We covered the recording approaches themselves in Recording Unity gameplay: 4 approaches compared, a starting point in the minimal implementation guide, and our own build-out in building an in-game bug reporter.

The comparison table

Summary

There's no single answer — the category itself is the decision most of the time. Already on UGS and only need crash reporting at no extra cost? Cloud Diagnostics is enough. Want trends on production exceptions? Error monitoring like Sentry is the right category. Mobile app that also needs video? Bugsee-class SDKs are the proven pick. Small team with no budget? Recorder + OBS carries you further than expected. Only once you need logs, game state, and video on one timeline does in-house work — or paying someone who already built it — become the actual question. What to check during the Cloud Diagnostics transition, where the free-combo math breaks even, and where error monitoring ends and QA capture begins are each covered on their own.

Rekon is the option that pays the "in-house" cost for you — a Unity 2022.3+ plugin that, on one hotkey (Ctrl/Cmd + Shift + B) in Play Mode, captures roughly the last 60 seconds of video, logs, and game state on one timeline, then connects straight into a Jira issue from the dashboard. If you're not sure which category fits yet, start by checking whether what your current tool is missing is crashes, video, or a shared timeline.