Lottie to MOV

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.

Which Lottie video export to use

FormatTransparencyBest for
MOV (this tool)No — background requiredFinal Cut, Premiere, QuickTime workflows
MP4No — background requiredThe web, and almost everything else
WebMYes, with VP9Transparent video on the web
APNGYes, 8-bit alphaTransparency with no player needed
GIF1 bit, fringesMaximum compatibility, small palettes

When to use it

  1. Bring an animation into Final Cut, Premiere or Resolve as a .mov.
  2. Hand a motion designer the container their workflow expects.
  3. Produce a QuickTime file for an older editing pipeline.
  4. Convert a Lottie for software that will not import JSON or GIF.
  5. Get an H.264 master at a chosen size and frame rate.

How to Use

  1. Drop a .json or .lottie file.
  2. Set the size, frame rate and quality, and pick a background colour.
  3. Encode, then download the .mov.

Features

  1. Genuine QuickTime container, not a renamed MP4
  2. H.264 through the browser's own encoder
  3. Size, frame rate and quality controls
  4. Estimated file size before you encode
  5. Even-dimension rounding for 4:2:0
  6. No ffmpeg download, no special headers
  7. Cancel mid-encode
  8. Nothing uploaded

FAQs

Is this a real MOV, or an MP4 renamed?

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.

Can I get a transparent MOV or ProRes?

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.

Why is a background colour mandatory?

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.

Does it need ffmpeg or any special headers?

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.

Why does the preview not play in my browser?

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.

Why are the dimensions rounded to even numbers?

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.

Is my animation uploaded?

No. It is rendered and encoded entirely in your browser.

Technical Details

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.

Lottie & Animation Tools

Lottie & Animation Tools

  • Lottie to PNG Sequence
  • Lottie to APNG
  • Lottie Metadata Viewer
  • Lottie Accessibility Analyzer
  • Lottie Optimizer
  • Lottie to dotLottie
  • dotLottie to Lottie
  • Lottie Player & Embed