Fix: Unity Shadow Flickering and Z-Fighting

Here is how to fix Unity shadow flickering z fighting. Shadows shimmer on surfaces that should be still. Two adjacent walls flash between their textures. These are shadow flickering and z-fighting — related but distinct depth precision problems that stem from the GPU running out of numerical precision when deciding what is in front of what.

The Symptom

Shadow acne shows up as a shimmering pattern on lit surfaces, especially at grazing angles to the light. It crawls as the camera moves. Z-fighting is different: two overlapping surfaces rapidly alternate visibility in flickering stripes. Both worsen at distance and with very small near clip values.

What Causes This

1. Shadow bias too low. The shadow map self-intersection test fails due to floating-point rounding, causing surfaces to shadow themselves in a noisy pattern.

2. Near clip plane too close to zero. The depth buffer distributes precision logarithmically. A near clip of 0.001 wastes most precision on the first few centimeters, leaving almost none for distant objects.

3. Overlapping coplanar geometry. Two triangles at the exact same position produce unpredictable depth test results that flicker each frame.

4. Shadow cascade boundaries. At cascade transitions, shadow resolution changes abruptly. Surfaces on the boundary see flickering as the camera moves and the boundary shifts.

5. Shadow resolution too low. When texels are large, shadow edges produce visible staircase patterns that shimmer with movement.

The Fix

Step 1: Increase shadow bias to stop shadow acne.

using UnityEngine;

public class ShadowFixer : MonoBehaviour
{
    [SerializeField] private Light _light;

    void Start()
    {
        // Start at 1.0, increase if acne persists
        _light.shadowBias = 1.0f;
        _light.shadowNormalBias = 1.0f;
        // Too much causes peter panning (shadow detachment)
    }
}

Step 2: Fix depth precision via the near clip plane.

var cam = GetComponent<Camera>();
// 0.1 for third-person, 0.3+ for top-down
cam.nearClipPlane = 0.1f;
cam.farClipPlane = 500f;
// Keep far/near ratio under 10000

Step 3: Tune cascades and fix overlapping geometry.

using UnityEngine.Rendering.Universal;

// Use 4 cascades for better shadow distribution
urpAsset.shadowCascadeCount = 4;
urpAsset.mainLightShadowmapResolution = 2048;

// For coplanar surfaces: offset one by 0.001 along its normal
// For decals: use Offset -1, -1 in the shader

Related Issues

If the visual issue is camera stutter rather than surface flickering, see Cinemachine camera jitter and stutter. If particle effects refuse to appear despite rendering looking correct, check particle system not playing.

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

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

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

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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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.

Near clip 0.001 is the single biggest source of z-fighting in Unity projects.