Turn a Lottie animation into an animated GIF for the places that still will not take anything else — email, documentation, Slack, marketplace listings. The animation is stepped frame by frame rather than screen-recorded, so nothing is dropped and the timing is exact. Choose the output size, the frame rate and a background colour, and the GIF is built in your browser; the animation is never uploaded, which matters when it is client work or a paid marketplace file. One thing this handles that many converters do not: GIF stores frame delay in whole hundredths of a second, and every browser silently clamps anything faster than 50 fps down to 10. A converter that ignores that will hand you a file that plays five times slower than you asked for, with nothing to explain why. Here the rate is capped where the format stops working, and if rounding changes the timing at all, you are told what the file will actually play at.
| Aspect | Limit |
|---|---|
| Colours | 256 per frame, quantised from the original |
| Transparency | One bit — opaque or invisible, nothing between |
| Frame delay | Whole hundredths of a second |
| Maximum usable rate | 50 fps; faster is clamped to 10 by browsers |
| File size | Scales with width x height x frame count |
| Audio | Not supported at all |
No. It is rendered and encoded in your browser. Lottie files are routinely client work or paid marketplace purchases, so keeping them off a server is the point rather than a nicety.
Because they are not the same kind of thing. A Lottie is vector instructions — a few kilobytes that scale to any size. A GIF stores every frame as pixels, capped at 256 colours, compressed with a 1987 algorithm. A 20 KB Lottie becoming a multi-megabyte GIF is entirely normal.
Reduce the dimensions and the frame rate — those are the two things that actually matter, because size scales with width times height times frame count. There is no quality slider that will save you; GIF has no such control in the way JPEG does.
Because GIF cannot store it. Frame delays are whole hundredths of a second, and every browser clamps anything under two hundredths up to ten — so a 60 fps GIF actually plays at 10 fps. The cap here is 50, which is the fastest the format genuinely supports. For smoother motion, use MP4 or WebM.
GIF alpha is one bit: every pixel is either fully opaque or fully invisible, with nothing in between. Anti-aliased edges, which rely on partial transparency, have to be forced one way or the other and pick up a halo of whatever colour was behind them. A solid background almost always looks better.
Yes. A .lottie is a zip container, so it is unpacked in the browser and the animation inside is rendered.
Every frame is held in memory as raw pixels before compression, so a large canvas with many frames adds up quickly. The tool estimates this and warns you beforehand — reduce the width or the frame rate when it does.
The animation is rendered with lottie-web's canvas renderer at the chosen output size, stepping frame by frame with goToAndStop rather than recording playback, so the result is deterministic and never drops a frame under load the way a screen capture does. Each frame is painted onto a background first (or left clear for transparency), read back as RGBA, quantised to a 256-colour palette with gifenc and appended to the encoder. The frame schedule is computed rather than assumed: asking for 15 fps from a 60 fps source means sampling every fourth frame, and the sampling is derived from the animation's real duration so the output does not end up short by an interval. The timing detail that catches people out is that GIF stores frame delay in whole hundredths of a second, which cannot express 30 fps exactly, and every browser clamps a delay below two hundredths up to ten as a legacy guard against flashing images. A naive converter that writes a delay of one for 60 fps therefore produces a file that plays at 10 fps — visibly wrong and hard to diagnose. Here the delay has a floor of two hundredths, the rate is capped at 50, and the tool states the rate the file will really play at whenever rounding changes it. Transparency is offered but flagged, because GIF alpha is a single bit: a pixel is either fully opaque or fully invisible, so anti-aliased edges fringe against whatever colour they land on. Memory is estimated before rendering — every frame is held as RGBA, so width times height times four times the frame count — and a render likely to exhaust the tab is warned about rather than attempted silently. Everything runs in the page.