Console & profiler
Both ship with the panel and need zero code. This page is what they do, and which settings shape them.
Console
The console tab shows everything that goes through Unity's log -
Debug.Log, warnings, errors, exceptions - on the device,
without a cable.
- Capture starts before your code runs. The log hook is installed at subsystem registration, so startup messages - plugin init, early errors - are already in the buffer the first time you open the console. Logs from worker threads are captured too.
- It stays smooth at scale. The list is virtualized over a ring buffer; tens of thousands of retained entries scroll without hitching. The buffer keeps the newest entries and drops the oldest past the Console Max Entries limit (10,000 by default).
- Filter and search. Severity toggles with live counts, plus a text search over the retained entries. A clear button resets the view.
- Rows preview safely. Each row shows the message
over its top stack frame. Rich-text messages are truncated without
ever cutting a tag in half, so a long
<color>log can't bleed its formatting into the rest of the list. - Tap for detail. The detail pane shows the full untruncated message, the stack trace, the timestamp - and a copy button.
- The list follows the tail while you're scrolled to the bottom, and stops following the moment you scroll up.
Exporting the log
Export, next to Clear, saves the console to a text file - the quickest way to get a log off a test device and into a bug report. A prompt first shows what will be written:
- Its own copy of the severity filters, starting as the console has them. Changing them in the prompt leaves the console alone.
- The active search, if any: the export holds exactly the entries the list shows. Clear search in the prompt exports everything instead, and leaves the console's own search as it is.
- A label for the file name, prefilled with the
product name - type something like
checkout-crashto find the file again later. - How many entries, and about how big the file is, updated as the filters change.
Every entry is written with its time, severity, full message and full stack trace, under a header naming the app, its version, the device and the filters used. While the file is written a progress bar shows and the panel takes no other input; large logs are written off the main thread, so the game keeps running.
Where the file goes:
| Platform | Saved to | Afterwards |
|---|---|---|
| Android 10 and later | The device's Downloads, in a Debug MD folder | Share opens the system share sheet |
| Android 9 and earlier | The app's own folder (the prompt shows the path) | No share button |
| iOS | The app's own folder | Share opens the system share sheet |
| Desktop and the editor | A DebugMD Exports
folder under Application.persistentDataPath |
Show in folder |
If the file can't be written - a full disk, a missing permission - the prompt says why. Export is not offered in WebGL builds, which have no file system to write to.
The error signal
Errors are easy to miss with the panel closed, so Debug MD can say so without you opening anything: when an error, assert or exception is logged, a red exclamation mark pulses in a screen corner for four seconds (configurable), then fades away.
- Where it appears. The trigger corner, when the panel opens from a corner gesture - the warning and the way in share a place. With the three-finger tap or no touch trigger, it uses the top-left corner. It always stays inside the safe area.
- It never takes input. The badge ignores touches entirely, so it cannot swallow a trigger tap underneath it.
- It stays out of the way. Nothing pulses while the panel is open - the console is right there - and opening the panel clears a pulse in progress. Errors logged before the overlay exists stay in the console but don't fire the signal, so a noisy startup doesn't flash on every launch.
- Further errors restart the pulse rather than queueing, so a stream of errors keeps the mark alive without piling up.
- Warnings can signal too. Turn on Warning Signal (off by default) and a logged warning pulses an amber mark in the same corner, for the same time. An error always wins: one logged during a warning takes over at once, while a warning logged during an error is simply dropped, not queued for later.
Turn it off in the settings asset (Console › Error Signal), or per device from the panel's About page under Device Settings - handy when a build is expected to log errors and the pulsing becomes noise. How long it pulses is set the same two ways (Error Signal Seconds, 1-30), and applies to the warning signal as well.
Profiler
The profiler tab is a lightweight, always-available view of how the build is running - deliberately simple, and honest about being approximate. For precise numbers, attach the Unity Profiler; for "why did the framerate just tank on this phone", this is enough.
- Frame-time graph over the last few hundred frames, split into main-thread update, render-thread and GPU time where the platform reports them, with markers on frames where a garbage collection ran.
- FPS, smoothed over a half-second window, and the last frame's duration in milliseconds.
- Memory: managed heap used and reserved, native memory allocated and reserved, and the number of GC runs this session.
- Pinnable. A mini profiler can ride the pinned dock, keeping frame time on screen while you play with the panel closed.
Turning it off
The profiler samples every frame from the moment Debug MD starts, so the graph already has history when you open it. The cost is small, but if you would rather pay none of it, tick Disable Profiler in the settings window's Profiler section before building:
- Nothing samples frame timings or memory, and the mini profiler cannot be pinned (a pin saved on the device is left alone, and comes back if the profiler is turned on again).
- The profiler button stays in the header, dimmed. Tapping it shows a short note that the profiler is turned off in the settings.
- It is a project setting with no per-device override: a build made with it ticked has no way to turn the profiler on.
- In the editor, sampling and the button follow the setting at once, even while playing; the pinnable mini profiler comes or goes the next time play starts.
Settings that matter here
| Setting | Effect |
|---|---|
| Console Max Entries | How many log entries are retained (default 10,000; clamped 256-200,000). More entries cost memory on device. |
| Error Signal | Whether a logged error pulses the corner badge (default on). Also overridable per device. |
| Warning Signal | Whether a logged warning pulses an amber badge (default off). Also overridable per device. |
| Error Signal Seconds | How long the badge pulses after an error or warning (default 4, 1-30). Also overridable per device. |
| Poll Frequency | Refresh rate of visible readouts, the profiler's included. |
| Disable Profiler | Turns the profiler off (default off, so the profiler runs). See Turning it off. |
| Destroy On Close | Destroys the panel UI on close to save memory. Console history is unaffected - the capture buffer lives outside the UI, so everything is still there when the panel reopens. |