Fix: Unity 2D Light Not Affecting Sprites in URP

Here is how to fix Unity 2D Lights that do not illuminate your sprites in URP. You add a Light 2D component, crank its intensity to 5, and the sprite stays at exactly the same brightness it had before. The Light 2D is real, the URP package is installed, but nothing connects. Three settings need to align: the renderer type, the sprite material, and the target sorting layers.

The Symptom

Sprites in your scene render at full brightness regardless of nearby Light 2D components. Toggling the lights off makes no visible difference. Light 2D gizmos appear in the Scene view but the rendered Game view ignores them. Sometimes the entire scene is full-bright; sometimes pitch black with no lights helping.

What Causes This

Sprite uses Sprite-Default material. The default sprite material is unlit. It outputs the sprite texture color directly without sampling any light contribution. 2D Lights have no effect on it.

URP asset uses Forward Renderer instead of 2D Renderer. The Forward Renderer ignores Light 2D components entirely; they only work with the 2D Renderer Data type.

Sorting layer mismatch. Each Light 2D has a Target Sorting Layers list. Sprites on layers not in the list are unaffected. The default list often includes only the Default layer.

No global light. The 2D Renderer does not use the Lighting window’s ambient color. With no global Light 2D, sprites fall back to whatever fallback the renderer provides, which can be black or unlit white depending on configuration.

The Fix

Step 1: Switch to the 2D Renderer. Open your URP Asset (Project Settings → Graphics → Scriptable Render Pipeline Settings). In the inspector, drag a 2D Renderer Data asset into the Renderer List. If you do not have one, create it via Create → Rendering → URP Universal Renderer (2D).

Step 2: Change sprite materials to Sprite-Lit-Default. Select all SpriteRenderers (filter the Hierarchy by component, or multi-select) and set Material to Sprite-Lit-Default.

// Bulk-update at runtime if needed
using UnityEngine;

public class PromoteSpritesToLit : MonoBehaviour
{
    [SerializeField] private Material litMaterial;

    [ContextMenu("Promote Sprites")]
    void Promote()
    {
        foreach (var sr in FindObjectsByType<SpriteRenderer>(FindObjectsSortMode.None))
            sr.sharedMaterial = litMaterial;
    }
}

Step 3: Add a Global Light 2D. Right-click in the Hierarchy: Light → 2D → Global Light 2D. Set Intensity to 1.0 and Color to white. This provides ambient illumination that makes sprites visible even without nearby point lights.

Step 4: Configure target sorting layers. On each Light 2D, expand the Target Sorting Layers list and add the layers your sprites are on (for example, Background, Default, Foreground). Lights only illuminate sprites on listed layers.

Step 5: Verify with a strong test light. Add a Spot Light 2D with intensity 5 right next to a sprite. If the sprite gets brighter, the pipeline is working — you can then dial intensity down to a normal value. If still no change, the material is still not Lit.

Shader Graph Materials

Custom 2D shaders need to be based on the Sprite Lit master node. If you started from Sprite Unlit, the shader will never sample 2D Lights regardless of how the Light 2D components are configured. Open the shader graph, change the master node, and rebuild.

Normal Maps For 2D Lights

Once Lit materials are in place, Light 2D direction can drive shading via the sprite’s secondary normal map texture. In the SpriteRenderer’s Sprite Editor → Secondary Textures, add a normal map under the name _NormalMap. The result is per-pixel directional shading from 2D Lights.

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

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

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

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

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.

“2D Renderer, Lit material, sorting layers, global light. Four checks and the sprites finally listen.”

Related Issues

For other URP rendering issues, see URP Shader Not Rendering in Build. For sorting layer problems, see Sprite Renderer Not Visible.

Sprite-Lit-Default. 2D Renderer Data. One Global Light. Layers in the list. Done.