How to Add Bug Reporting to Your Unity Game

Most Unity games ship with zero in-game bug reporting. Players find something broken, maybe post about it in Discord or Reddit, and you piece together what happened from a screenshot and a vague description — if you’re lucky.

This guide covers your options for adding proper in-game bug reporting to a Unity project: what’s actually available, what each approach requires, and when each makes sense.

Option 1: Unity’s Built-in Bug Reporter

Unity includes a crash reporter through Unity Cloud Diagnostics (formerly Unity Game Backend / UGS). It catches unhandled exceptions and crashes automatically, no form required.

What it captures:

• Stack traces on crash/exception
• Device info (OS, GPU, CPU, RAM)
• Unity version and build target

What it doesn’t do:

• Let players describe what happened
• Capture video or screenshots
• Handle feature suggestions or gameplay feedback
• Give players any confirmation their report was received

If your main concern is catching crashes silently, this does the job. If you want players to actually submit feedback — and have any context around it — you’ll need something else.

Option 2: Build Your Own Form

A custom UI form that POSTs to your own backend or a Google Sheet. Gives you full control, no third-party dependency.

What you’ll need to handle yourself:

• The UI (form fields, submit button, validation)
• Screenshot capture (ScreenCapture.CaptureScreenshotAsTexture)
• Log collection (Application.logMessageReceived)
• A backend to receive and store submissions
• Duplicate detection (manual or none)
• Some way to triage and prioritize reports

Totally doable for a solo dev or small team. The hidden cost is maintenance — your submission endpoint breaks, your backend goes down, your spreadsheet gets unmanageable at 500+ reports. It also doesn’t scale well once you have an active community sending in dozens of reports a day.

When it makes sense: Very early prototype, internal QA only, or when you have specific data requirements that no existing tool handles.

Option 3: BetaHub Unity Plugin

BetaHub is a bug tracking platform built specifically for game developers. The Unity plugin adds an in-game reporting form that automatically captures video, screenshots, and logs — and sends everything to a dashboard where you can triage, assign, and track issues.

The plugin is free and open source (MIT license) on GitHub. BetaHub’s free plan covers the basics; paid plans start at $26/developer/month.

What gets captured automatically on each report:

• Video — last 60 seconds of gameplay before submission (configurable)
• Screenshot — taken at the moment the form opens
• Unity logs — full log file attached
• Geolocation and latency (optional components)

Players fill in a description and optionally steps to reproduce. If the title is left blank, it’s generated by AI along with priority and tags.

Setup

Requirements:

• Unity 2022.3 or later
• FFmpeg (for video recording — install via Window > BetaHub > Download FFmpeg in the Unity editor)
• A BetaHub account and Project ID

Install the plugin:

Open Package Manager > click + > Add package from git URL:

https://github.com/betahub-io/unity-plugin.git

Add to your scene:

Drag the BugReportingFormCanvas prefab into your scene hierarchy. In the Inspector, enter your Project ID (format: pr-xxxxxxxxxxxxxxxx, found in your BetaHub project settings).

Test it:

Press F12 in Play mode. You should see the bug report form overlay your game, with a video recording indicator if FFmpeg is installed correctly.

Get your Project ID and API token:

In BetaHub: Settings > Integrations > Auth Tokens tab. Generate a token and enter it in the plugin inspector to link submissions to your project.

IL2CPP builds

If you’re building with IL2CPP as your scripting backend, video recording requires extra steps:

1. Add ENABLE_BETAHUB_FFMPEG to your Scripting Define Symbols (Player Settings)
2. Make sure the native library libbetahub_process_wrapper is in your build’s Plugins directory for your target platform (e.g., Plugins/macOS/, Plugins/Linux/)

If you skip this, video recording will be disabled in IL2CPP builds and you’ll see a warning in the console at runtime. Mono builds don’t need any of this.

IL2CPP performance note

If you’re seeing excessive file I/O from the logger in performance-sensitive scenarios, add DISABLE_BETAHUB_LOGGER to your Scripting Define Symbols to stop BetaHub from capturing Unity logs.

What happens after a report is submitted

Reports land in your BetaHub dashboard with everything attached. The platform runs duplicate detection automatically — if 15 players report the same inventory crash, they get merged into one issue with a heat score based on duplicate count, watchers, recency, and priority. You can push issues to Jira, GitHub, Asana, or other tools from there.

If you have a Discord community, BetaHub’s bot can also collect bug reports directly from Discord channels and merge them with in-game submissions in the same dashboard. Players don’t have to leave Discord to report.

Honest comparison

If you’re in early prototype and need crash data only — Unity’s built-in tools are fine. If you have players actively testing and you want real feedback with context, the BetaHub plugin is the least work to set up and covers most of what you’d build yourself anyway.

Resources

• BetaHub Unity Plugin on GitHub
• Full setup documentation
• BetaHub free plan
• BetaHub Discord — plugin support and questions