Step 1: Transfer your MOV files using the button above or by slide and deposit.
Step 2: Click the 'Convert' button to start the conversion.
Step 3: Retrieve your converted WebP files.
MOV to WebP Conversion FAQ
What file size should I expect from a 5-second MOV → WebP?
+
Animated GIF: 2 to 8 MB at 480p depending on motion complexity. Animated WebP: 200 KB to 1 MB at the same resolution / quality. Animated WebP is 5 to 10x more efficient than GIF for the same visual quality. WebP offers both lossy and lossless modes, with alpha transparency and animation available in either.
Does it matter that the MOV came off a phone or a camera?
+
Mainly for the orientation. An MOV is an ISO base-media file, and that family records rotation as a flag in the container rather than by turning the pixels — which is why a clip shot upright on a phone can look right in one player and lie on its side in another. The animation is built from the decoded pixels, so that flag has to be honoured before the first frame is written; if the preview comes back sideways, rotate the source and convert it again. Everything else about a camera or editor recording is the easy case: one video track, one steady stream of frames. A MOV normally carries H.264 or HEVC for delivery, or ProRes when it is an editing master, alongside AAC or uncompressed PCM audio.
Why will my browser not open the MOV I want to animate?
+
Because an MOV is not a container browsers are obliged to support, and which builds manage it varies rather than being guaranteed. It changes nothing about the conversion — the file is decoded server-side, so a container the browser refuses converts exactly as well as one it accepts, and no local codec pack is needed to use it here. It is worth knowing which way the trade runs, though: the animated WebP that comes back is a format every browser renders, so this moves the clip from something the web will not touch to something it will. MOV files are large, and outside the Apple ecosystem playback support is patchier than MP4 — older Android builds and some Smart TVs will refuse them.
Will the WebP animation play audio from the MOV?
+
No — animated WebP formats (GIF, WebP, APNG) do not store audio. If you need sound, target a video container (MP4, WebM) instead of an animated image format.
Can I make the WebP animation loop forever?
+
Yes. The Loop setting makes the WebP repeat forever (the default) or play once and stop. There is no setting for a specific number of repeats. The loop flag is stored in the file, and most viewers respect it.
Why does my WebP look choppy compared to the MOV source?
+
Two common causes. A lower frame rate drops frames: 15 fps from a 60 fps MOV keeps only one frame in four, so pick a higher value in the Frame Rate setting. And GIF is limited to 256 colours, so gradients dither visibly; animated WebP keeps full colour.
Can I crop or resize the MOV before making the WebP?
+
Yes — the resize option scales the MOV down before frame extraction, which dramatically shrinks WebP file size. A 480p WebP from a 4K MOV is roughly 16x smaller than a 4K WebP. Use /video-cutter/ for cropping in a separate step.
Is my MOV video private during WebP animation creation?
+
Yes. Uploaded MOV files are processed on our own conversion servers, no person reviews them, and they are never shared. The upload and the converted WebP are both deleted automatically about 24 hours after the conversion, which leaves time to download the result. See /privacy/ for the full policy.
How long does converting a 10-second MOV into WebP take?
+
Animated WebP encoding is CPU-bound and slower than typical video re-encode — expect roughly 1x source duration. A 10-second MOV → WebP finishes in about 10 seconds; a 30-second clip in about 30. GIF is slightly slower than animated WebP due to palette computation.
