Not a pitch, a workflow tip — and there's a free pack at the end if you want one.
If you keep your game art as loose PNGs, every new asset means another manual step: open the image, hand-place it on the canvas, guess the pivot, and later re-do all of that when you change the resolution.
Shipping a sprite sheet plus a frame-coordinate JSON removes the guessing:
- One sheet image — every frame in a single file. One import, one draw call for a whole set.
- A JSON with each frame's rectangle — so the atlas can be sliced by code, not by eye.
The JSON is the part people skip, and it's the part that actually pays off. It lets you slice automatically at build time, re-pack a subset of frames without re-exporting the art, merge someone else's sheet with yours, or drive a runtime atlas in a tool like Godot or Unity.
Two things that matter more than they sound:
Filter mode is not optional. Pixel art needs Point / Nearest. Soft vector art needs Linear / Bilinear. This is the single most common reason an asset "looks wrong" in-engine, and it isn't the art — it's the filter.
Keep the grid uniform. Sheets only slice cleanly if every frame sits on the same cell with the same margins and the same baseline. If it isn't uniform, the JSON is what keeps you honest — it exposes the inconsistency instead of hiding it.
The free 12-icon pack below is built exactly this way (12 icons at 64x64, combined sheet, frame JSON, Godot + Unity import notes), so you can see the format before committing to anything:
https://yangjuejue.itch.io/pixel-icon-starter
Two larger sets use the identical structure if you need more:
https://yangjuejue.itch.io/pixel-icon-set-36 (36 icons, $9)
https://yangjuejue.itch.io/soft-icon-set-12 (12 soft-vector icons, $5)
If your engine or setup isn't covered by the README, say which one and I'll write it up.
Curious what other people are using for atlas generation — if there's a better pipeline than hand-rolled JSON, I want to know about it.