Why does my World Space Canvas not face the camera?

World Space Canvases do not billboard automatically. You have to rotate the canvas toward the camera in a script every frame with transform.LookAt or transform.rotation = cam.rotation. Without this, the canvas uses whatever rotation you set it at and stays oriented that way in world space.

How do I size a World Space Canvas correctly?

World Space Canvases default to large dimensions in world units. Scale the Canvas transform down (0.01 Scale is typical) so the canvas covers a sensible area. Reference resolution on Canvas Scaler does not apply in World Space mode — size is pure transform scale.

Does Canvas.worldCamera matter for a World Space Canvas?

Yes — it is used for UI raycasting. If worldCamera is None, pointer events on the canvas do not work. Assign your main camera (or the camera that should detect clicks) to Event Camera field.

Fix: Unity World Space Canvas Not Following Camera

Quick answer: World Space Canvas does not auto-billboard. Add a script that rotates the canvas toward the camera each frame. Assign Event Camera for raycasting. Scale the canvas transform (0.01 typical) to size the UI in world units.

Here is how to fix Unity World Space Canvas not following camera. You add a health bar above an enemy — World Space Canvas, UI Image for the fill. In play mode, the health bar is visible from the front but invisibly thin from the side, and invisible from behind. Or it appears tiny or giant, or clicks do not register. World Space UI requires explicit camera wiring that Overlay canvases handle automatically.

The Symptom

A Canvas in World Space render mode behaves incorrectly:

Does not face the camera as the camera moves
Invisible from behind (because it renders as a flat plane)
Scaled wrong — either huge or invisibly small
Clicks do not work even when hovering over buttons

What Causes This

World Space does not billboard. Unlike Screen Space Overlay or Screen Space Camera, World Space Canvases are positioned like any other GameObject. They have a fixed rotation in world space. If you want the canvas to face the camera, you must rotate it yourself.

Event Camera not set. For UI interaction (clicks on buttons, drag), the canvas’s Event Camera field must reference a camera. Without it, the Graphic Raycaster cannot compute pointer positions and raycasts miss.

Scale issues. Canvas components typically default to a width of 1000 and height of 1000 units. In World Space, this means the canvas is a 1000x1000 meter plane. Shrinking via transform.scale = 0.01 gets it to human-readable size. Easy to forget.

Canvas Scaler confusion. The Canvas Scaler component has Reference Resolution and Scale Factor options that only work in Screen Space modes. In World Space, only the transform scale matters. Adjusting reference resolution does nothing.

The Fix

Step 1: Add a billboard script. Attach to the world-space canvas so it faces the camera each frame.

using UnityEngine;

public class FaceCamera : MonoBehaviour
{
    private Camera cam;

    void Awake() { cam = Camera.main; }

    void LateUpdate()
    {
        if (cam == null) return;
        // Face away from camera so text reads correctly
        transform.rotation = cam.transform.rotation;
    }
}

Use LateUpdate so camera movement has finished before orientation is set. Using cam.transform.rotation (not LookAt) preserves consistent orientation across frames — text does not tilt up/down as the camera rotates.

Step 2: Assign Event Camera. Select the Canvas. In the Canvas component, assign the main camera to Event Camera. This enables Graphic Raycaster to work correctly in World Space.

If you have multiple cameras (minimap, main, etc.), pick the one that should handle UI input — usually the main gameplay camera.

Step 3: Scale sensibly. A canvas designed at 400x100 pixels (like a health bar) with transform.scale = 1 is a 400x100 meter sign. Scale down:

transform.localScale = new Vector3(0.01f, 0.01f, 0.01f);

Now the canvas is 4x1 meters — correct for a floating sign above a character.

Step 4: Set Canvas Sort Order / Render Queue. World Space canvases participate in depth-sorting with other geometry. If a canvas is inside a transparent object, it may render behind. Adjust Sort Order or move the canvas slightly in front.

Occluding Geometry

World Space Canvases can be occluded by geometry in front of them. A health bar behind a wall is invisible. If you want the bar to be always-visible, use a custom shader for the UI with ZTest Always, or switch to Screen Space Camera mode with a secondary camera that only renders UI.

Multi-Canvas Scenes

If your scene has many world-space UIs (floating damage numbers, nameplates, waypoints), creating a Canvas per UI is expensive. Use a pool of pre-instanced Canvases that reposition to where they are needed. Or use a shader-based approach (UI Toolkit or custom mesh) for hundreds of elements.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“World Space Canvas is a 3D object that happens to contain UI. Treat it like a billboard mesh: rotate it, scale it, depth-sort it.”

Related Issues

For Canvas Scaler issues, see Canvas Scaler UI Blurry. For raycaster blocking issues, UI Raycaster Blocking Clicks Elsewhere covers related UI event issues.

Billboard script, Event Camera assigned, scale 0.01. World Space UI works.