01 · Scope
AI output creates extraction problems, not production certainty
What automation can accelerate
Finding visibly separated islands, proposing crop regions, removing a consistent background, generating names, normalizing canvases, and packaging a review set.
What a person must decide
Whether a fragment belongs to a character, whether transparency removed intentional detail, whether poses are consistent, and whether the asset is legally and visually safe to publish.
02 · Workflow
A safer cleanup sequence
- Preserve the originalKeep the untouched source and record the generation context outside the exported asset folder. Do not overwrite the only copy.
- Extract a reversible first passRun detection, inspect proposed regions, restore cleaned areas when uncertain, and redraw boxes around touching subjects.
- Normalize only approved objectsUse explicit filenames, transparent padding, alignment, and canvas rules after deciding which objects are usable.
- Review the delivery, not only previewsInspect exported PNG files on light and dark backgrounds, compare the contact sheet with the source, and record rejected or repaired assets.
03 · Decision guide
Common AI-art defects and the response
| Defect | What to inspect | Recommended response |
|---|---|---|
| Touching characters or props | Merged detection region | Redraw separate regions manually |
| Floating fragments | Accessories, effects, noise, shadows | Restore intentional detail; exclude unrelated fragments |
| Background-color fringe | Light and dark preview backgrounds | Adjust cleanup or repair in an image editor |
| Inconsistent character scale | Contact sheet and fixed canvas preview | Normalize carefully; do not hide genuine pose differences |
| Malformed details | Hands, faces, weapons, typography | Reject or edit; extraction cannot repair authored anatomy |
04 · Quality gate
Human approval gate
- Every object maps to an intended source subject.
- No important detached detail was removed.
- Alpha edges work on light and dark backgrounds.
- Filenames describe the approved production role.
- Licensing and generation records are retained separately.
- Rejected variants cannot enter the shipping folder accidentally.
05 · Questions
What to confirm before you ship
- Does SpriteSplitter generate or repair artwork?
- No. It extracts, cleans backgrounds, normalizes, and packages existing pixels. Detailed visual repair belongs in an image editor.
- Why keep a contact sheet?
- It provides a fast visual inventory for checking omissions, duplicates, order, inconsistent scale, and accidental exports.
- Will the generated image be uploaded?
- No. The current image workflow runs in the browser. Analytics must never include the source image, filenames, or exported image content.
06 · Sources
Scope and references
Product behavior described on this page refers to SpriteSplitter version 0.3.0 and the built-in sample workflow.