Export a Lottie animation as a QuickTime .mov for editors and workflows that expect one. The video is H.264, encoded by your browser's own encoder, and written into a genuine QuickTime container — the file is branded qt rather than being an MP4 with the extension swapped, which is the usual shortcut and produces a file that is not what it says it is. Set the size, frame rate, quality and background, and the file is built locally. Nothing is uploaded and there is no ffmpeg to download first.
| Format | Transparency | Best for |
|---|---|---|
| MOV (this tool) | No — background required | Final Cut, Premiere, QuickTime workflows |
| MP4 | No — background required | The web, and almost everything else |
| WebM | Yes, with VP9 | Transparent video on the web |
| APNG | Yes, 8-bit alpha | Transparency with no player needed |
| GIF | 1 bit, fringes | Maximum compatibility, small palettes |
A real one. The container's ftyp box carries the QuickTime brand rather than the MP4 one. The shortcut of muxing an MP4 and changing the extension usually plays, because QuickTime reads MP4 — but it produces a file that is not the format it claims to be, and anything that inspects the container rather than the extension will notice.
No, and nothing in a browser can. Transparent MOV in practice means ProRes 4444, which no browser can encode. H.264 has no alpha channel at all, which is why a background colour is required here rather than optional. If you need transparency, use the WebM converter — VP9 keeps an alpha channel.
Because H.264 cannot store transparency. An animation encoded without a background does not come out transparent, it comes out black, so the tool makes you choose rather than letting you find out afterwards.
Neither. It uses the browser's built-in WebCodecs encoder and a muxer written in plain TypeScript, so there is no multi-megabyte ffmpeg download and none of the cross-origin isolation headers that ffmpeg.wasm requires.
Some browsers refuse to play .mov in a video element even when the file is perfectly valid, because they go by container rather than codec. The file itself is fine — download it and open it in QuickTime or your editor.
H.264 stores colour at half resolution on each axis, so an odd width or height leaves the last row or column without a whole colour sample. Encoders either refuse it or silently crop, so the size is rounded to even before encoding.
No. It is rendered and encoded entirely in your browser.
The animation is stepped frame by frame with lottie-web's `goToAndStop` onto a canvas rather than played and captured, so the timing of the result never depends on the tab keeping up — a frame dropped during playback would become a frame missing from the file. Each canvas state is handed to a WebCodecs `VideoEncoder` through mediabunny's CanvasSource, encoded as H.264, and written into a QuickTime container. The container is the point of this tool and it is a real one: the file's `ftyp` box carries the brand `qt `, not the `isom` that an MP4 carries. That distinction matters because the usual way to offer a MOV export is to mux an MP4 and change the extension, which works in most players precisely because QuickTime will read MP4 — and is still a file that is not the format it claims to be, which fails in the places that check. Every frame is composited onto a solid background before encoding, and that is a requirement rather than a setting: H.264 has no alpha channel, so a transparent animation encoded without a background is not transparent in the output, it is black. Transparency needs the WebM converter and VP9 instead. Dimensions are rounded to even numbers because H.264's 4:2:0 chroma subsampling stores colour at half resolution on each axis, so an odd width or height has no whole chroma sample to describe its last row or column and encoders either fail outright or silently crop. Bitrate is derived from the pixel count, frame rate and the quality setting, with a floor that stops a small animation turning to mush and a ceiling that stops a large request producing a file nothing will play back smoothly. No ffmpeg.wasm is involved, which means none of the cross-origin isolation headers it requires — the encoding is the browser's own hardware-backed encoder, and nothing is uploaded.