How to Fix Shader Variant Explosion (Long Builds, Big Size)

Shader variant explosion is too many keyword combinations. Cutting them fixes build time and size. Here is how.

How to fix it

1. Reduce keywords

Every multi_compile keyword doubles the variant count, so several keywords multiply into thousands of variants. Remove keywords you do not need and combine or simplify the ones you keep.

2. Strip unused variants

Use variant stripping to remove combinations your project never uses, so the build only compiles and ships variants you actually render. This cuts both compile time and build size dramatically.

3. Move static choices out of keywords

If a choice is fixed per material rather than toggled at runtime, make separate shaders or material properties instead of a keyword, so it does not multiply the variant count.

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 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.