Initializing... drag & drop files here
Supports: WEBM
Pull a sharp still image out of a WebM video and save it as WebP — one frame at a timestamp you choose, or a sequence of evenly spaced frames as separate WebP files. WebP stills are smaller than JPEG or PNG at the same visual quality, with optional lossless mode and transparency. This converter outputs still images, not a moving loop; if you need an animated, looping result, use WebM to GIF instead.
WebM and WebP are both Google-developed and share the same baseline still coder (VP8 powers lossy WebP, and the same intra-frame techniques appear inside WebM video). That kinship makes a clean still extraction natural: decode the WebM, grab the frame(s) you want, and re-encode each as a WebP image. Per Google's published measurements, the result is 25–34% smaller than JPEG for lossy stills and 26% smaller than PNG in lossless mode.
<video> tag — Grab a representative frame and serve it as the poster attribute so the player shows a crisp still before playback starts.| Property | WebM | WebP (output here) |
|---|---|---|
| Type | Video container | Still image |
| Codecs | VP8, VP9, AV1 + Vorbis/Opus audio | VP8 (lossy), VP8L (lossless) |
| Audio | Yes | No (stripped on conversion) |
| Color depth | 8-bit / 10-bit | 24-bit lossy; lossless preserves source |
| Alpha channel | VP9 + alpha | Yes (8-bit) |
| Lossy still vs JPEG | — | 25–34% smaller at equal quality |
| Lossless still vs PNG | — | ~26% smaller |
| Browser support | Browsers + media players | Chrome 32+, FF 65+, Edge 18+, Safari 16+ |
| Best for | Web video playback, screen recording | Web thumbnails, poster frames, transparent stills |
Audio is dropped during conversion — WebP is a still-image format with no audio track. If you need to keep audio, convert to a video format like WebM to MP4 instead. For a moving, looping image, WebM to GIF produces a real animation.
| Use case | Frame Selection | Quality | Result |
|---|---|---|---|
| Blog cover / hero still | Specific Frame | 90% lossy | 30–150 KB still, sharp |
| Web thumbnail | Specific Frame | 75–85% lossy | Small still for grids and cards |
| Transparent UI asset | Specific Frame | Lossless, Yes | Keeps VP9 alpha, larger file |
| Pixel-perfect archive frame | Specific Frame | Lossless, Yes | No second compression pass |
| Contact sheet / frame picks | Multiple Screenshots | 85% lossy | N separate stills, evenly spaced |
Poster image for <video> |
Specific Frame | 85–90% lossy | One representative frame |
No. This converter outputs still images only — one frame (Specific Frame) or several separate still frames (Multiple Screenshots). It does not produce an animated, looping WebP. If you want a moving image that loops, convert to GIF with WebM to GIF, which is built for animated output, or keep the clip as video via WebM to MP4.
Use Specific Frame mode and enter a timestamp in seconds (e.g. 2.5 for the frame at 2.5 seconds in). The output is a single still WebP. For a set of evenly spaced stills across the clip, switch to Multiple Screenshots — each frame is saved as its own WebP file. If you'd rather have JPG or PNG, see WebM to JPG.
WebM compresses video temporally — each frame references its neighbors — so an individual frame already carries some compression noise. Re-encoding it as lossy WebP adds a second pass. Two fixes: raise the Quality Preset toward Highest, or switch "Lossless?" to Yes. Lossless WebP is larger but preserves every pixel of the decoded WebM frame. In our testing, a 1080p frame from a screen-recording WebM re-encoded at Very High quality landed around 60–120 KB, versus roughly 300–500 KB for the same frame as lossless WebP.
Yes. WebP supports an 8-bit alpha channel, which covers what VP9+alpha encodes. A frame from a transparent screen recording or rendered animation keeps its alpha through the conversion. This is one of WebP's biggest advantages over JPG (no alpha) and GIF (1-bit alpha only, so soft edges look jagged). For best fidelity on transparent stills, set "Lossless?" to Yes.
Modern ones do: Chrome 32+, Firefox 65+, Edge 18+, and Safari 16+ render WebP images natively (Safari added full WebP support on macOS Big Sur 11 and iOS 14, September 2020, with broad parity by Safari 16). For very old clients you may still want a JPG or PNG fallback — convert the same frame with WebM to JPG.
Choose "Specific file size" and enter a target in KB or MB. The encoder iterates quality until the result lands near your target, which is handy for CMS upload caps or LCP budgets (for example, keeping a hero still under 200 KB). For an existing WebP you want to shrink further, see compress WebP.
Yes. Drop in multiple WebM files; settings apply to all by default, or override per file. Each file is processed on our servers in parallel, then you download the stills individually or as a single ZIP. There's no per-file cap beyond upload size and time.