Export a Lottie as a numbered PNG sequence in a ZIP, or as a single sprite sheet with the CSS to play it. Every frame keeps its full alpha channel, which is the reason to use PNG rather than GIF — GIF has one bit of transparency and fringes at every soft edge. Frames are stepped one at a time rather than captured during playback, so nothing is dropped if the tab is busy, and the filenames are zero-padded so they import in the right order. Choose any output size and frame rate. Everything renders in your browser and the file is never uploaded.
| PNG sequence | Sprite sheet | |
|---|---|---|
| Output | ZIP of numbered files | One PNG plus CSS |
| Best for | Video editors, game engines | Web animation without JavaScript |
| Transparency | Full alpha | Full alpha |
| Requests | One per frame | One, total |
| Limit | File count | 16384px per side on many GPUs |
So they sort in playback order. Without padding, frame_10 comes before frame_2 in every file manager and every image-sequence import dialog, and the animation imports scrambled. They are padded to at least four digits, more for very long animations.
Yes, the full 8-bit alpha channel. That is the main reason to choose a PNG sequence over a GIF: GIF stores one bit of transparency, so a pixel is either fully opaque or fully clear and every soft edge fringes against whatever is behind it.
The animation's own rate reproduces it exactly. Asking for less samples evenly — 15 fps from a 60 fps animation takes every fourth frame. Asking for more than the source has only produces duplicates, which makes the export bigger without adding anything.
Because a sprite sheet advances by jumping the background position between whole frames. Any timing function that interpolates — linear, ease, a cubic-bezier — slides the background mid-frame and shows two frames at once through the window.
It can be. Many GPUs and browsers cap a single image at 16384 pixels on a side, past which it may fail to draw or be quietly downscaled. The tool warns you when a sheet crosses that line; using more columns makes it squarer and usually solves it.
No. It is rendered in your browser and the frames are packed there too.
The animation is loaded into lottie-web's canvas renderer and stepped frame by frame with `goToAndStop`, rather than played and captured, so the output does not depend on the tab keeping up in real time — a dropped frame during playback would silently become a missing frame in the export. Which source frames get sampled comes from the requested output rate: asking for 15 fps from a 60 fps animation takes every fourth frame, and the schedule is built so the last sample lands on the end of the animation rather than up to one interval short. Each frame is read off the canvas as a PNG, which keeps the full alpha channel — the reason to choose a PNG sequence over a GIF, since GIF has one bit of transparency and fringes at every soft edge. Filenames are zero-padded to at least four digits, which matters more than it looks: without padding, frame_10 sorts before frame_2 in every file manager and every image-sequence import dialog, so the animation imports scrambled. The sprite-sheet mode draws the same frames into a grid and emits the CSS to play it, using `steps()` with the column count. That timing function is not a preference: a sprite sheet advances by jumping the background position between whole frames, and any interpolating function slides it mid-frame and shows two frames at once. Sheets are checked against the 16384px limit that many GPUs and browsers impose on a single texture, past which the image may fail to draw or be silently downscaled. Because the whole thing hinges on the canvas actually drawing, a transparent render is checked for coverage: if every frame comes back with no opaque pixels the renderer produced nothing, and the export is abandoned with an explanation rather than handing over an archive full of empty PNGs.