01 · Scope
The tools begin at different pipeline stages
SpriteSplitter begins with a composite
Its primary job is to find visually separated objects, let a person correct the regions, clean the background, and produce separate reviewable files.
TexturePacker begins with sprite inputs
Its documented workflow collects individual sprites, packs them efficiently into sheets, exports framework metadata, and can run from a command line or build process.
02 · Workflow
Use them together when the source is messy but delivery is automated
- ExtractUse SpriteSplitter to turn irregular boards into transparent, predictably named PNG files.
- ReviewCheck the contact sheet, alpha edges, canvas alignment, and intended sequence before packing.
- PackFeed the approved PNG folder into TexturePacker when advanced formats, compression choices, or build integration are required.
- RebuildKeep extraction presets and packer settings under version control so later asset changes can follow the same contract.
03 · Decision guide
Task-based comparison
| Task | SpriteSplitter | TexturePacker |
|---|---|---|
| Detect objects inside one irregular image | Primary workflow | Not the primary documented input workflow |
| Manually correct extraction regions | Built into the browser workspace | Use prepared sprite inputs |
| Generate a simple local atlas | Available for lightweight delivery | Core product workflow with extensive settings |
| Framework formats and build automation | Focused Unity/Godot manifest output | Broad formats and command-line integration |
| Source-image privacy | Local browser processing | Desktop / local command-line workflow |
04 · Quality gate
Decision signals
- Start with the actual input format, not the feature list.
- Separate PNG review is required before packing.
- The target engine needs a format beyond the simple manifest.
- The pipeline must rebuild atlases automatically.
- The source contains touching objects needing manual judgment.
- The team needs a browser-only extraction step.
05 · Questions
What to confirm before you ship
- Is SpriteSplitter a replacement for TexturePacker?
- No. SpriteSplitter emphasizes extraction and correction from composite artwork. TexturePacker emphasizes atlas construction and production integration.
- Can SpriteSplitter pack an atlas?
- Yes, it can create a local PNG atlas and JSON metadata for a straightforward workflow. Use a specialized packer when advanced packing or framework output is the main requirement.
- What is the most reliable combined workflow?
- Extract and approve separate PNG files first, then pack the approved folder. This keeps visual cleanup and packing decisions independently reviewable.
06 · Sources
Scope and references
Primary references: TexturePacker command-line documentation · TexturePacker atlas settings. Product behavior described on this page refers to SpriteSplitter version 0.3.0.