
Aseprite's merge-duplicates sheet option can store duplicate frames as one image region in the atlas. Fewer visible image regions therefore need not mean fewer intended animation events. Inspect the exported data and the receiving animation together instead of counting atlas rectangles alone.
Key Takeaways
- The atlas stores image regions; playback has its own frame sequence.
- Duplicate merging changes the sheet's stored representation.
- Image and metadata must come from the same export version.
Identify the export option before diagnosing loss
The Aseprite command-line reference lists merge-duplicates as merging duplicate frames into one in the sprite sheet. It separately documents sheet image output and data output for sprite-sheet information.
Record whether duplicate merging was enabled, which source frames or tags were exported and which image/data files the receiver used. Another export scope, such as a restricted tag or frame range, can also change what reaches a sheet.
- Preserve the native animation and current export settings.
- Identify repeated source drawings and the intended playback order.
- Export the sheet and its accompanying metadata as one named candidate.
- Inspect how the receiving importer reconstructs that order and timing.
- Compare a candidate without duplicate merging if the importer cannot interpret the chosen representation.
Do not manually remove timeline frames just to make the native animation's count match the atlas's visible regions.
A hypothetical held-pose atlas
Suppose a character returns to the same pose after another action. An atlas may reuse identical imagery while playback still needs that pose at both points in the story. The required check is whether the receiver shows both intended events with the approved timing.
This is a proposed acceptance scenario, not a claim about a measured JSON result. The cited option description does not establish that every engine understands the metadata or that every animation format uses the same schema.
The optimized-GIF frame-count guide discusses another representation change. Atlas reuse concerns spatial image regions and a receiving animation's mapping, rather than GIF clearing frames or combined consecutive delays.
Accept behavior and traceable packaging
Play the imported result through a distinctive start, a hold, a repeated pose and the ending. Compare its event order and duration with the native animation. Check that image and metadata have matching revision identifiers.
Accept when the receiver reproduces the approved sequence, regardless of whether every logical event has a unique atlas region. If the importer loses events or timing, correct its mapping or use a supported non-merged export. A smaller sheet is not sufficient evidence of a successful delivery.
Related tasks
- Why Does an Optimized GIF Have a Different Frame Count but the Same Playback?
- Why Does My Image Sequence Skip Frames or Play at the Wrong Speed?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- Aseprite Command Line Interface: merge-duplicates merges duplicate frames into one sheet region; sheet and data are separate export outputs.
Documentation-based guidance. Scenarios, worksheets and acceptance procedures are proposed or hypothetical; no hands-on test, benchmark, search-volume measurement or AI-citation ranking is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.