Fix: Unity URP Post-Process Bloom Double-Applied

A scene that looks fine in the test layout becomes overexposed when the UI camera is added. Bright emissive materials — neon signs, particle effects — bloom into white blobs. Disabling the UI camera fixes it. Something about the second camera is doubling the effect.

How URP Camera Stacks Render

URP supports a Camera Stack: one Base camera plus zero or more Overlay cameras. The Base camera renders the scene, applies post-processing (bloom, color grading, tone mapping), and writes the result. Each Overlay camera then renders on top, potentially adding UI or HUD elements.

If an Overlay camera has Post Processing enabled, the bloom pass re-runs on the already-bloomed Base camera output. Bright pixels are convolved twice. The result is visibly over-glowy.

The Fix

On each Overlay camera:

1. Select the camera in the hierarchy.
2. In the Inspector, find Rendering → Post Processing.
3. Uncheck it.
4. Save the scene.

Only the Base camera should have Post Processing enabled. Confirm by selecting the Base camera and looking at its Stack list — Overlay cameras listed there now contribute geometry without re-running effects.

UI-Only Cameras Special Case

For dedicated UI cameras (UGUI Overlay), you typically don’t want bloom or any color grading on the UI text. Setting Render Type = Overlay and disabling Post Processing is the right configuration. The UI renders crisply on top of the post-processed world.

Volume Mask Isolation

For cases where you do want different post-processing on different cameras — e.g., a first-person weapon view with its own bloom — use Volume layers:

Main Camera:
  Render Type: Base
  Volume Mask: Default
  Post Processing: enabled

Weapon Camera:
  Render Type: Overlay (in main camera’s stack)
  Volume Mask: WeaponVolumes
  Post Processing: enabled (rare; usually disabled)

Place world Volume objects on Default and weapon-specific ones on WeaponVolumes. Each camera reads only its own layer.

Verifying

Take a screenshot before and after the fix. Compare bright emissive areas. After the fix, bloom should be roughly half as intense visually — the “double-applied” appearance is gone. Use the Frame Debugger (Window → Analysis → Frame Debugger) to confirm only one Bloom pass runs per frame; before the fix you’ll see Bloom listed twice.

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

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

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

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

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

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

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

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

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.

“Post-processing runs per camera with PP enabled. Stack cameras compose final output once — not once per stack entry.”

Audit Camera Stack settings whenever bloom “suddenly” got stronger after a UI change.