Texture Atlas Extractor [patched] May 2026

A texture atlas extractor (also known as a sprite sheet unpacker) is a utility designed to reverse the process of texture packing. While a texture atlas combines multiple smaller images into a single large file to improve GPU performance and reduce draw calls, an extractor identifies and separates these sub-images back into individual files for editing, modding, or asset reuse. Top Texture Atlas Extractor Tools (2026)

Choosing the right tool depends on whether you have the original data file (XML/JSON) or just the image itself.

TextureAtlas Toolbox: A comprehensive, open-source solution that supports over 15 atlas formats. It features batch processing, smart cropping, and specific support for engines like Friday Night Funkin'. texture atlas extractor

ShoeBox Texture Ripper: Highly recommended for "ripping" textures from images without metadata. It allows users to define textures by clicking four corner points and can even flatten perspective or curved textures.

TextureAtlas Extractor (Hans5958): A lightweight, experimental web-based tool for quick unpacking. It is compatible with major formats like Cocos2D, Godot, Phaser, and Unreal Engine. A texture atlas extractor (also known as a

RenderDoc: While primarily a graphics debugger, it is used by advanced users to capture and save live textures directly from running 3D games. Key Features to Look For

When selecting an extractor, prioritize tools that offer these specific functionalities: Performance: Reduces texture swaps and draw calls in

1. Why Texture Atlases Exist

• Performance: Reduces texture swaps and draw calls in rendering engines by packing many small images into one large GPU texture.
• Memory and IO: Fewer files to load and less overhead for file I/O and GPU state changes.
• Animation & UI: Spritesheets make frame-based animation and UI element grouping straightforward.

2. Alferd Spritesheet Unpacker (Free & Open Source)

• Best for: No-metadata, evenly spaced grid sheets (classic pixel art).
• Method: Drag and drop an image. Tell it the grid size (e.g., 5 columns, 4 rows). It auto-exports.
• Verdict: Essential for retro game ripping. Fast, but fails on irregular packing.

8. Metadata Formats

• Common formats a pipeline should support or export:
  • JSON (custom schema): easy, portable.
  • TexturePacker .atlas and .plist (used in many engines).
  • Spine, Spine-like JSON for animations.
  • Unity SpriteAtlas import metadata.
• Stored fields:
  • name, frame rect (x,y,w,h), rotated (bool), trimmed (bool), sourceSize (w,h), spriteSourceSize (x,y,w,h), pivot
• Extractor should preserve or generate consistent IDs and ordering for animations (e.g., frame_000.png).

How Does a Texture Atlas Extractor Work?

Under the hood, most extractors follow a simple four-step pipeline:

1. Parse the metadata – Read the atlas descriptor (LibGDX .atlas, Cocos2d .plist, Unity SpriteAtlas, generic JSON/XML).
2. Locate each sub-image – Extract coordinates, width, height, rotation flags, and optional trimming data.
3. Read the master image – Load the PNG, JPEG, or WebP file.
4. Crop & save – For each entry, cut out the rectangle (apply rotation if needed) and save as a separate PNG, preserving original names and folder structures.

Advanced extractors also handle:

• Packed rotation – Some atlases rotate sprites 90° for tighter packing; the extractor automatically rotates them back.
• Trimmed sprites – If the original had transparent borders removed, the extractor can restore original canvas dimensions.
• Padding & bleeding – Ignoring separator pixels used to prevent texture bleeding.

3. The "Invisible" Problem: How to Extract Without a Data File?

This is the most common issue users face. You have a PNG atlas, but you do not have the .json or .txt file describing where the sprites are located.

Standard extractors will fail here. In this scenario, you need a different category of tool: