What causes Godot 2D lights not showing?

The lit sprites are not on a layer the light affects, the scene is fully lit by a bright canvas modulate (so the light adds nothing), or the light is disabled or has zero energy.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix 2D Lights Not Showing in Godot

Quick answer: Set the light and sprites to matching light masks, darken the ambient or canvas modulate so the light is visible, and enable the light with non-zero energy and range.

2D lights that do nothing usually are not affecting the sprites, or the scene is already fully bright. Here is how to make them show.

How to fix it

1. Match light masks

A Light2D only affects CanvasItems whose light mask overlaps the light's. If the masks do not match, the light illuminates nothing. Set the sprite's and light's masks to intersect.

2. Darken the ambient

If the scene is already at full brightness (bright canvas modulate or a bright environment), a light adds nothing visible. Darken the ambient so the light has something to brighten.

3. Enable the light properly

Confirm the light is enabled, has non-zero energy, a sensible range, and a texture. A disabled light, zero energy, or no texture produces no visible lighting.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.