Step 1: Share your WebM files using the button above or by drag and drop.
Step 2: Click the 'Transform' button to start the transformation.
Step 3: Grab your converted WebP files.
WebM to WebP Transformation FAQ
How do I turn a WebM video into an animated WebP?
+
Upload the WebM and the converter samples frames (default 15 fps), encodes them into the animated WebP container, and applies palette quantization tuned for the WebP format (GIF gets an adaptive 256-color palette; animated WebP supports full 24-bit color). WebM is a strict subset of Matroska that Google published in 2010 specifically to give HTML5 video a royalty-free container. WebP is Google’s 2010 image format, built from the VP8 keyframe encoder and intended to replace JPG, PNG and GIF at once.
How do I pick which few seconds of the WebM to animate?
+
Open it in a player, find the moment and note the timecode, because a WebM does not normally carry chapter marks to navigate by. Paste that into the start-time field, add a duration, and the converter seeks to that point and decodes only the span you asked for. The seek is accurate to the frame, but it can only be as good as the number it is handed — check it against a preview before committing to a long clip. WebM is a poor fit anywhere outside a browser — video editors, phones’ native galleries and Smart TVs largely ignore it.
Does the codec inside the WebM change the WebP I get?
+
Not the picture, only the wait. A WebM is a Matroska-family container, and that family keeps the container and the codec completely separate — what the file actually holds was decided when it was written and is not implied by the extension. The converter decodes whatever it finds back to raw frames first, and those frames are identical whichever codec produced them. Decode cost is not identical: the newer, more efficient codecs take several times longer to unpack than the older ones, so two WebM files of the same length can take noticeably different times to reach the same WebP. WebM is deliberately narrow: VP8 or VP9 video (AV1 more recently) with Vorbis or Opus audio, and nothing else.
The WebM came from a web page — can that be turned into a WebP?
+
Yes, once you have the file itself. A WebM is what the web uses for inline video precisely because browsers play it with no plugin, so the clip playing in a tab is usually a plain WebM that saves and uploads here like any other file. The exception is a streaming player that hands out short numbered segments rather than one file — those have to be reassembled before anything can be converted. Rights are the other thing worth checking: being able to download a video is not the same as being allowed to republish an animation made from it. WebM plays natively in every modern browser with no plugin, no licence fee and no patent exposure, which makes it the default for web-embedded video.
Should the frames in the animated WebP be lossy or lossless?
+
Lossy, for anything that started as video. An animated WebP can encode its frames either way: the lossless mode keeps every pixel and suits flat graphics and screen text, while the lossy mode uses block-based prediction of the kind a video codec uses and suits real footage. Camera frames are full of fine grain and gradients that lossless compression finds no pattern in, so a lossless animation of a filmed clip can run several times the size of a lossy one that looks the same. Leave it lossy unless the source was a screen recording of crisp text. WebP is still second-class outside the browser — print workflows, older Office builds and some phone galleries do not accept it.
How short should my WebM clip be for a clean WebP animation?
+
Animated WebP works best for clips under 10 seconds. Beyond that the file balloons (GIF is essentially per-frame uncompressed). For longer animations target animated WebP or APNG, both of which use video-codec-grade compression and scale much better.
What file size should I expect from a 5-second WebM → 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.
Will the WebP animation have the same frame rate as the WebM?
+
By default we downsample to 15 fps for animated GIF (it visually struggles above 25 fps) and 24 fps for animated WebP / APNG (which handle higher rates cleanly). Override via the frame-rate option if your viewer supports the source rate.
Will the WebP animation play audio from the WebM?
+
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-count option controls whether WebP loops infinitely (default), plays N times, or plays exactly once. The loop count is stored in the WebP container metadata and respected by every modern viewer.
Why does my WebP look choppy compared to the WebM source?
+
Two common causes. First, frame-rate downsampling: 15 fps WebP from a 60 fps WebM drops 75% of frames; fix with the frame-rate slider. Second, palette quantization: GIF is limited to 256 colors and gradient-heavy WebM dithers visibly. Switch to animated WebP for full-color fidelity.
Can I crop or resize the WebM before making the WebP?
+
Yes — the resize option scales the WebM down before frame extraction, which dramatically shrinks WebP file size. A 480p WebP from a 4K WebM is roughly 16x smaller than a 4K WebP. Use /video-cutter/ for cropping in a separate step.
