Why does my URP 2D Light bake produce no static lighting?

2D Lights set to Volumetric or with Quality Low may not bake properly. Set the Light to Static, ensure Light Blend Style supports baking, and confirm sprites are using Sprite-Lit-Default material so they accept baked lighting.

How do I configure Light Blend Style in URP 2D?

In the 2D Renderer Data, expand Light Blend Styles. Each style has a name, blend mode (Multiply/Additive/etc), and mask channels. Lights pick a style; sprite materials must reference the same style indices to receive.

Should I bake or use real-time 2D lights?

Real-time is more flexible and looks correct as content moves. Bake only static decoration lighting where performance demands it. For most 2D games, real-time with appropriate quality is fine.

Fix: Unity URP 2D Light Bake Static Failing

Quick answer: Set the 2D Light to Static, sprites to Sprite-Lit-Default, and confirm Light Blend Style indices align between Light and material. For most games, prefer real-time 2D lights; reserve bake for performance-critical static scenes.

Here is how to fix Unity URP 2D Light static baking failing to apply lighting to sprites. Sprite material, light blend style, and light type must all align.

The Symptom

You add a Light 2D, mark it Static, expecting baked lighting. Sprites in the area are unlit or improperly lit.

What Causes This

Sprite uses unlit material. Sprite-Default does not respond to 2D Lights at all.

Wrong Light Blend Style. Lights pick blend style by index; sprites pick by name. Mismatch leaves sprite ignoring the light.

Light is volumetric. Volumetric lights interact differently and may not bake to sprites.

The Fix

Step 1: Material to Sprite-Lit-Default. Select the SpriteRenderer; assign Sprite-Lit-Default (or a custom Sprite Lit shader graph).

Step 2: Confirm Light Blend Style match. 2D Renderer Data → Light Blend Styles. Default style 0 is Multiply. Light’s Blend Style index = sprite’s Renderer Light Mask layer.

Step 3: Light Type and Static flag.

Light 2D:
  Light Type:    Point or Global
  Light Order:   0
  Color:         FFE4B5
  Intensity:     1.0
  Falloff:       0.5
  Use Normal Map: optional

Step 4: For real-time use, prefer that. Static bake in URP 2D is limited; real-time lights handle moving content cleanly and modern GPUs run them cheap. Use real-time unless profiling shows a problem.

Step 5: Verify with a Global Light 2D test. Add a Global Light 2D at intensity 1.0. If sprites get even basic lighting, the pipeline is wired up correctly. If not, sprite material or renderer data is the issue.

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

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

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

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.

“Sprite-Lit material. Matching blend style. Real-time over static unless you measure a need.”

Related Issues

For 2D Light not affecting sprites, see 2D Light URP. For ShadowCaster2D, see ShadowCaster2D.

Lit material. Matching blend style. Real-time first. Lights apply.