What causes a Unity Canvas not showing UI?

The Canvas render mode or its camera reference is wrong, the UI is positioned off-screen, or sorting order is hiding it behind something — so nothing appears even though the elements exist.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a Unity Canvas Not Showing Any UI

Quick answer: Check the Canvas render mode and assigned camera, confirm the RectTransforms are on-screen, and fix sorting order and any objects drawing over the UI.

A Canvas that shows nothing usually has a render-mode or camera misconfiguration, or its elements are off-screen. Here is the checklist to find which.

How to fix it

1. Check render mode and camera

Screen Space Overlay needs no camera; Screen Space Camera needs a valid Render Camera assigned. A wrong or missing camera reference, or the wrong mode, can make the UI invisible. Set them correctly.

2. Confirm elements are on-screen

An element with an off-screen anchored position or zero size renders nothing visible. Select it and check its RectTransform is within the canvas bounds and has a non-zero size.

3. Fix sorting and occlusion

Another canvas or 3D object with a higher sorting order can draw over yours. Check the Sort Order and Canvas layering so your UI is not hidden behind something else.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unity error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

The errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.