Sprite Sheet Unpacker

Start with atlas image files, then choose config parsing, auto detect, or grid slicing depending on what metadata you have. The tool normalizes frame rectangles, resolves multipack page references, and previews each frame directly on the atlas before export.

Once the frame list looks correct, export a ZIP with one PNG per sprite plus a frames.json manifest. That makes it practical to hand extracted assets to game engines, QA workflows, or atlas-debug sessions.

Atlas recovery often involves production art that teams do not want to upload into a third-party service. Running locally in the browser keeps that privacy boundary intact while still giving you metadata parsing, confidence feedback, and download packaging.

Compared with manual screenshot cropping or ad hoc scripts, the workflow stays more consistent across atlas formats and makes failure cases easier to inspect.

The biggest value is having several recovery paths in one place. Metadata-driven extraction handles known exports, auto detect covers transparent atlases without config, and grid/custom slicing gives deterministic control when heuristics are not enough.

Whether your query is sprite sheet unpacker, atlas to sprites, or reverse texture packer, the goal is the same: recover clean frame images with predictable output and minimal setup.

ToolBuddy combines metadata parsing, preview overlays, and local ZIP export so teams can recover atlas frames without writing one-off scripts or using upload-first tools.

Config-driven extraction preserves names and page mapping when metadata exists.

Auto detect and grid slicing provide fallback paths when config is missing or broken.

Multipack-aware page resolution reduces manual atlas matching during recovery.