
Aseprite's Tag.repeats value of zero has different documented behavior in the editor and on export: it previews indefinitely in the UI but exports once. For ping-pong, that unspecified value exports once in each direction. Inspect the tag's repeat value and direction before duplicating frames to force a longer file.
Key Takeaways
- Zero means an unspecified repeat count, not an infinite exported animation.
- Repeat count and animation direction interact.
- The exported artifact still needs a playback check in its receiving environment.
Record the intended tag behavior
Write down the tag's frame range, direction and required number of passes. A tag can preview convincingly as an endless action while its export contract is different.
The Aseprite Tag API reference documents Tag.repeats and Tag.aniDir. It distinguishes Forward, Reverse, Ping-Pong and Ping-Pong Reverse, and explicitly explains the zero-repeat UI/export difference.
- Identify the intended timeline tag rather than the entire sprite.
- Record its first and last frames and animation direction.
- Inspect the repeat property through the supported tag controls or scripting workflow for the installed version.
- Set an explicit repeat count when that is the required output behavior.
- Export a separately named candidate and count its actual passes.
For a script with a variable already bound to the intended Tag object, the documented assignment tag.repeats = 3 sets the property to three. This is an API illustration, not a complete script or an executed test.
A hypothetical animated badge
Suppose a website needs three forward passes of a badge animation before stopping. An indefinite editor preview does not prove that requirement. Record the requested forward direction and three passes, then check the actual exported candidate.
For ping-pong, do not interpret “once” casually. The API documents that an explicit repeat value of one plays in only one direction, while zero's exported behavior includes each direction. Confirm the intended start and ending pose.
Separate repetition from seamlessness
The loop-boundary guide addresses whether the end joins convincingly to the beginning. Correct repeat properties cannot repair a visual jump between incompatible poses.
Likewise, a receiving website or player can impose its own playback behavior. Verify the actual format and integration rather than treating a source tag as an instruction every external player necessarily honors.
Accept when the delivered artifact has the approved direction, passes, timing and ending. If it does not, retain the source tag settings and inspect export scope and playback configuration before adding redundant frames. No export or runtime compatibility test is claimed here.
Related tasks
- How Do I Analyze a Video Loop When the Awkward Part Is Between Repeats?
- Why Does a Transparent GIF Leave Old Shapes Behind as It Moves?
- Why Does an Optimized GIF Have a Different Frame Count but the Same Playback?
Sources and scope
- Aseprite Tag API: Tag.repeats zero has different UI/export behavior; repeat counts interact with ping-pong direction; Tag.aniDir choices.
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.