What causes a Unity Sprite Atlas not packing?

Sprite packing is disabled in the editor settings, the sprites are not added to the atlas (or their folder is not included), or the atlas was not packed for the build.

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 a Unity Sprite Atlas Not Packing Sprites

Quick answer: Enable Sprite Packing in editor settings, add the sprites or their folder to the atlas's objects-for-packing, and pack the atlas (it packs automatically on build when enabled).

A Sprite Atlas that does not pack is usually a settings or inclusion problem. Here is how to make it gather your sprites.

How to fix it

1. Enable sprite packing

In Project Settings, Editor, set Sprite Packer mode to enabled (always for builds, or for the editor too). With packing off, the atlas never gathers sprites.

2. Add sprites to the atlas

The atlas only includes what you add to its Objects for Packing — individual sprites or a folder. Sprites not listed are not packed. Add the folder so new sprites are included automatically.

3. Pack and verify

Pack the atlas (Pack Preview in the editor; it packs on build automatically when enabled) and confirm the sprites appear. Check the atlas is actually used at runtime, not the loose sprites.

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

The errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.