Step 1: Provide your WebM files using the button above or by toss and let go.
Step 2: Click the 'Convert' button to start the conversion.
Step 3: Fetch your converted WebP files.
WebM to WebP Conversion FAQ
How do I turn a WebM clip into an animated WebP?
+
Upload the WebM 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). 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 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 WebM 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. WebP offers both lossy and lossless modes, with alpha transparency and animation available in either.
Will the WebP have the same framerate as the WebM 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 WebM if your target viewer supports it.
Will the WebP animation carry audio from the WebM?
+
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 WebM?
+
Two common causes: frame-rate downsampling (we drop a 30 fps WebM 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 WebM did not). Switch the target to animated WebP for full colour fidelity.
Can I crop or resize the WebM 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 WebM is 16x smaller on disk than a 4K WebP. Cropping is handled in a separate /trim/ or /crop/ step run before the conversion.
