Upload the MOV file, pick a start time and duration (default: first 5 seconds), and the converter samples frames at 15 fps, encodes them into an animated WebP container, and applies palette quantization tuned for the target (WebP GIF uses an adaptive 256-colour palette; animated WebP supports full 24-bit colour with alpha).
How short should my MOV input be to get a good WebP?
+
Animated WebP is sized for clips under 10 seconds. Longer than that and the output balloons fast — GIF is uncompressed-per-frame, so even modest clips run to many megabytes. For longer animations, target animated WebP or APNG, both of which compress similar to modern video codecs.
What is the file size of a 5-second WebP animation from a MOV clip?
+
For animated GIF at 480p the typical result is 2-8 MB depending on motion complexity. For animated WebP at the same resolution / quality, expect 200 KB to 1 MB — animated WebP is 5-10x more efficient than GIF for the same visual quality.
Will the WebP have the same framerate as the MOV source?
+
By default we downsample to 15 fps for animated GIF (GIF works poorly above 25 fps in most viewers) and 24 fps for animated WebP / APNG (which handle higher rates fine). The frame-rate option overrides the default to preserve the source rate from your MOV if your target viewer supports it.
Will the WebP animation carry audio from the MOV?
+
No — animated WebP formats (GIF, WebP, APNG) do not store audio at all. If you need sound with your clip, target a video container (MP4, WebM, MKV) instead of WebP. Many social embeds (Twitter, Discord) actually convert MP4 uploads into GIF-style autoplay loops, giving you the best of both.
Can I make the WebP loop endlessly?
+
Yes — the loop-count option controls whether the WebP loops infinitely (default), plays N times, or plays once and stops. The loop count is stored in WebP container metadata and respected by every modern viewer, web browser, and embed surface.
Why does the WebP look choppier than the source MOV?
+
Two common causes: frame-rate downsampling (we drop a 30 fps MOV to 15 fps GIF by default — bump the frame-rate option to restore smoothness) and palette quantization (GIF is limited to 256 colours per frame, which posterizes gradients in a way the original MOV did not). Switch the target to animated WebP for full colour fidelity.
Can I crop or resize the MOV before generating the WebP?
+
Yes — the resize option scales the input down before frame extraction, which dramatically reduces final WebP size. A 480p WebP generated from a 4K MOV is 16x smaller on disk than a 4K WebP. Cropping is handled in a separate /trim/ or /crop/ step run before the conversion.
Is my MOV private during WebP animation conversion?
+
Yes — same privacy model as every conversion. Source clip and output animation are processed in isolated workers and deleted within minutes.
How long does the MOV to WebP encode take?
+
Animated WebP encoding is CPU-bound and slower than typical video re-encoding because of the palette / dithering passes — expect roughly 1x source duration. A 10-second MOV clip produces a WebP in around 10 seconds; longer inputs scale linearly.
Does the WebP preserve transparency from the MOV?
+
Animated GIF supports single-colour transparency only (a binary mask). Animated WebP and APNG support full 8-bit alpha. Most camera-captured MOV sources have no alpha channel anyway, so the WebP comes out fully opaque regardless. If you do have transparent input (screen recordings, animated rendering output), target WebP or APNG for the WebP.
Can I share the WebP on Discord / Slack / Twitter / Bluesky?
+
Animated GIF is universally supported — every embed surface accepts it. Animated WebP plays on Twitter, Discord, and modern browsers but breaks on iMessage and older Slack clients. If maximum reach matters, target GIF; if file size or colour quality matters, target WebP.