Turn a Lottie into a WebM video, including a genuinely transparent one. VP9 carries an alpha channel, which is what makes WebM the right format for an animation that has to sit over a page background rather than in a box. Frames are stepped one at a time and handed to the browser's own encoder rather than screen-recorded, so the timing is exactly what you asked for instead of whatever the machine managed during playback — and it finishes as fast as it can encode rather than taking as long as the animation runs. Before anything renders, the tool checks whether your browser's encoder will actually keep the alpha channel, because supporting VP9 does not imply supporting VP9 with transparency, and a converter that assumes it hands you a file with a black box behind it.
| Browser | Encodes VP9 alpha | Plays VP9 alpha |
|---|---|---|
| Chrome / Edge | Yes | Yes |
| Firefox | Varies | Yes |
| Safari | No | No — shows opaque |
| VP8, any browser | No | No alpha in the codec |
With VP9, in Chrome, Edge and Firefox, yes — a real alpha channel, not a chroma key. Two caveats the tool checks and states: your browser's encoder has to accept alpha, which is verified before rendering rather than assumed, and Safari does not decode VP9 alpha and will show the video opaque.
VP9 unless you have a specific reason. It is smaller at the same quality and it is the only one of the two that can carry transparency. VP8 exists here for decoding on older devices.
Because it is not one. A capture through MediaRecorder runs in real time and drops frames whenever the main thread is busy. This steps the animation frame by frame, encodes each one, and finishes as fast as the machine allows — with every frame present and the intervals exactly as requested.
WebM plays in Chrome, Edge, Firefox and Opera, and on modern Safari for VP9 without alpha. For guaranteed playback including older Safari and most editing software, MP4 is the safer choice — the Lottie to MP4 converter covers that.
A plain video element with autoplay, muted, loop and playsinline. The alpha channel composites over whatever is behind it. Provide a fallback for Safari — a still image or an opaque version — since it will render the video opaque rather than transparent.
The animation's own size and frame rate, which are filled in for you. Going above the source frame rate adds file size and no smoothness, because the frames in between are duplicates.
No. It is rendered and encoded in your browser.
WebCodecs is needed, which means a recent Chrome, Edge, Firefox or Safari. If it is unavailable the tool says so up front rather than failing part way through — the GIF converter works everywhere as a fallback.
Frames are rendered by stepping lottie-web's canvas renderer with goToAndStop rather than by recording playback, and that distinction is the difference between a usable file and an unusable one. A screen capture through canvas.captureStream and MediaRecorder runs in real time: a ten-second animation takes ten seconds, every frame the main thread is busy for is dropped, and the frame timing is whatever the browser managed rather than what was asked for. Stepping the animation frame by frame and handing each one to a WebCodecs VideoEncoder produces exactly the frames requested, at exactly the intervals requested, as fast as the machine can encode — and the same schedule maths the MP4 converter uses, derived from the animation's real duration rather than assumed, means asking for 24fps from a 60fps source samples correctly instead of ending up short by an interval. Transparency is the other half of the tool and the part most converters get wrong by omission. Alpha in WebM needs VP9 specifically — VP8 has no alpha at all — and, more subtly, it needs the browser's VP9 encoder to accept `alpha: "keep"`, which is not implied by supporting VP9. So the capability is feature-detected with VideoEncoder.isConfigSupported before anything renders, and if the browser will discard the alpha you are told and given a solid background instead of a file that looks right in the preview and has a black box behind it on the page. The decode side is stated too: Chrome, Edge and Firefox play VP9 alpha, Safari does not and will show the video opaque. Bitrate is derived from pixels times frame rate times a bits-per-pixel figure, scaled to seventy per cent of the H.264 equivalent because VP9 genuinely is more efficient and reusing the H.264 number just makes a larger file for no visible gain; VP8 gets no such discount because it is not more efficient than H.264 to begin with. The encoder queue is throttled, since letting it run ahead costs far more memory than the frames themselves. Everything runs in the page.