Frequently Asked Questions

The tool supports both extraction and generation workflows:

For Extraction (Extract tab)

• Image files: PNG, BMP, DDS, JPEG/JPG, TGA, TIFF, WebP
• XML metadata: Starling/Sparrow XML, TexturePacker XML
• JSON metadata: JSON Hash/Array, Phaser 3, Aseprite JSON, Egret2D
• Text metadata: Spine Atlas, Simple TXT, Cocos2d Plist, UIKit Plist
• Engine-specific: Godot (.tpsheet/.tpset), Paper2D, Unity (.tpsheet), CSS Spritesheet
• Adobe Animate: Animation.json + spritemap.json pairs with matrix transforms
• FNF files: JSON or XML character data from Friday Night Funkin' engines
• No metadata: PNG/JPEG atlases using chroma key extraction

For Generation (Generate tab)

• Input: Loose PNG/JPEG frames or frame sequences
• Output metadata: Sparrow/Starling XML, TexturePacker XML, JSON hash/array, Aseprite JSON, Spine Atlas, Phaser 3, CSS, TXT, Plist, UIKit Plist, Godot, Egret2D, Paper2D, Unity

• Lower the scale: Change from 1.0 to 0.75 or lower.
• Reduce FPS: Lower the frames per second.

GIFs can only use whole numbers for frame timing. When converting FPS to milliseconds, numbers with decimals get rounded.

Example: 24 FPS = 41.67 ms per frame, which gets rounded to 42 ms. This slight difference can make animations appear faster or slower.

• Lower Alpha Threshold: Decrease the transparency threshold; it may cause some frames to get skipped.
• Check your sprite sheet: Make sure all frames are properly defined in your metadata file.

Try different cropping options:

• No crop: Keeps the original full image size for each frame.
• Frame-based: Crops around each individual frame (PNG exports only).
• Animation-based: Crops consistently across all frames to keep alignment.

• Files are saved in folders named after your animations.
• Frame images go in a subfolder called [animation_name]_frames.
• GIFs/WebP files are saved as [animation_name].gif or .webp.
• Check the output directory you selected in the program.

Adobe Animate spritemaps require significantly more memory and CPU than other formats.

• Close other applications: Free up as much RAM as possible.
• Reduce worker threads: Lower the thread count in settings.
• Use an SSD: Faster disk access helps with intermediate frame caching.
• Process smaller batches: Extract one or two spritemaps at a time.
• Upgrade RAM: 16 GB+ recommended; 32 GB+ for large Adobe atlases.

• Increase CPU Threads: Increase the number in the settings menu. (This may have the opposite effect if you don't have enough memory.)
• Close other programs: Free up your computer's memory.
• Use an SSD: Processing is faster if your files are on an SSD.

• Reduce CPU Threads: Lower the number in the settings menu.
• Make images smaller: Use a lower scale setting (like 0.5).
• Close preview windows: They use up memory.

• Temporarily disable antivirus: It might be scanning each file as it's created.
• Use your local drive: Don't save to network or cloud drives.
• Adjust CPU Threads: Sometimes fewer threads work better when memory-limited.

• Make sure your character JSON or XML file is correct.
• The image path in your file should match your actual sprite sheet file.
• Your file must match the format for your engine (Kade/Psych/Codename).

For more details, see the Friday Night Funkin' Guide.

GPU texture compression stores image data in a format that GPUs can decompress directly during rendering, reducing VRAM usage and improving performance. Use it when generating atlases for game engines:

• BC1/BC3/BC7 for desktop games (DirectX, Vulkan)
• ETC1/ETC2 for mobile games (OpenGL ES)
• ASTC for modern mobile and cross-platform (Vulkan, Metal)
• PVRTC for legacy iOS (PowerVR GPUs)

If you're just extracting sprites for galleries or web use, you don't need GPU compression.

ASTC requires the astcenc command-line tool and PVRTC requires PVRTexToolCLI. These are not bundled with the application. Download them from:

• astcenc: ARM's GitHub
• PVRTexToolCLI: Imagination Technologies

BC and ETC formats work out of the box via the included etcpak package.

GPU compression works on fixed-size blocks (typically 4×4 pixels). If padding between sprites is smaller than the block size, adjacent sprites can bleed into each other after compression. The tool automatically increases padding to at least the block size to prevent this.

1. In the Extract tab, use the menu bar and choose "Select files."
2. Select the metadata file for your sprite sheet.
3. Select the image file containing the sprite sheet.
4. Adjust your settings using global settings, or double-click an animation entry to configure per-animation overrides.
5. Click Start process to begin extraction.

1. Switch to the Generate tab in the main window.
2. Add your loose frame images (PNG/JPEG).
3. Choose your packing algorithm and output metadata format.
4. Configure options like padding, power-of-two sizing, and deduplication.
5. Click the generate button to create your atlas.

Use "Select files" from the menu bar to add individual files. Anything you add with "Select files" will be added to the processing list regardless of folder location.

The application handles large collections automatically. You can adjust FPS for each individual animation entry. Note: if an error occurs on a CPU worker thread, the app continues processing on other threads while pausing the affected one until you confirm to continue.

• Test with smaller files: Try smaller sprite sheets first; you may be having memory problems.
• Reduce CPU threads: More threads result in more simultaneous images and more memory usage.
• Free up memory: Close other programs.
• Check your files: Your sprite sheet or metadata might be corrupted.

• Lower Alpha Threshold: Try setting it to 0.1 or lower.
• Check image size: Make sure your sprite sheet dimensions match what's in the XML.
• Check coordinates: Make sure frame coordinates aren't outside the image.

• Make sure the "Use regex" checkbox is set if you're using pattern matching.
• Verify your search patterns are correct.
• Uppercase and lowercase letters are treated differently.
• Rules are applied in the order they appear in the list.

• Make sure you have permission to write to the program's folder.
• Check that the config file path exists.
• Try closing and reopening the program.
• If all else fails, delete app_config.cfg to reset everything.

• Check your internet connection.
• Download the latest version manually from the download page.
• Replace all files with the manually downloaded update.