WebM to PNG Converter

How to Convert WebM to PNG Online

1. Upload Your WebM File: Drag and drop or click "+ Add Files" to select your WebM clip. VP8, VP9, and AV1 WebM streams are all accepted, and batch upload is supported so you can pull frames from several clips in one pass.
2. Pick Frame Selection mode: Choose Specific Frame with a Time (seconds) input (e.g. 2.100 for the frame at 2.1 s) to grab one still, or switch to Multiple Screenshots and set frame interval to harvest a sequence — every Nth frame, or one frame per second.
3. Tune image output (Optional): Open Advanced Options to set Quality Preset (Very High is the default), Image resolution (Keep original, a preset like 1080P/720P, percentage scale, or custom W x H), Colors (ORIGINAL truecolor, or quantize to 256/128/64/.../2 colors for smaller PNGs), and Compression level 1-9 (default 6) plus Compression speed 1-10 (default 4) for zlib DEFLATE tuning.
4. Convert and Download: Click Convert. Single frames download as one .png; multi-frame extractions arrive bundled as a ZIP so the image sequence stays in order.

Why Convert WebM to PNG?

WebM is the open VP8/VP9/AV1 container Google introduced in 2010 for royalty-free web video, but it's a moving picture format — most editors, slide decks, and CMS image fields will not embed a .webm. PNG (ISO/IEC 15948, third edition June 2025) is the lossless raster format every browser, OS, and image tool reads, and it preserves the alpha channel that VP9-alpha WebMs carry. Pulling a still or a frame sequence out of a WebM clip is the bridge between "video on the web" and "asset I can drop into Figma, Photoshop, a PR pitch, or a static page."

• Capture a hero frame for a thumbnail or social card — extract the strongest frame from a screen recording or product loop and ship it as the PNG poster for embeds, OG tags, or YouTube custom thumbnails.
• Pull a transparent overlay — VP9 with yuva420p carries an 8-bit alpha channel; converting to PNG keeps the transparent background intact for logos, lower-thirds, or sticker assets.
• Build sprite sheets and image sequences for animation — game engines (Godot, Unity), After Effects, and Lottie tooling consume PNG sequences; ffmpeg one-liners are fine for one job, but a browser tool wins when you need 600 ordered frames from a 20-second 30 fps clip without scripting.
• Document a bug from a screen recording — Chrome and Firefox DevTools record screens as WebM; converting the exact problem frame to PNG gives you a clean attachment for Jira, Linear, or GitHub issues.
• Save a sticker from Telegram, Discord, or a Twitter video — animated stickers and short video clips often arrive as WebM; a PNG still is what you actually need for an avatar, emoji set, or print.
• Archive a key frame at full quality — PNG is lossless, so the still you save is bit-for-bit the decoder's output, ready for OCR, image-recognition training, or evidentiary use.

WebM vs PNG — Format Comparison

Frame Extraction Quick Guide

Frequently Asked Questions

Will the PNG keep my WebM's transparent background?

If the source is a VP9 (or AV1) WebM encoded with an alpha pixel format such as yuva420p, the alpha channel is decoded and written into the PNG's alpha channel — the rounded corners, soft edges, and transparent backdrop survive. If the WebM is plain VP8 or a VP9 file without alpha, there is nothing transparent to preserve and you'll get an opaque PNG. Chrome and Firefox can play VP9-alpha WebMs directly; Safari historically cannot.

Why is my PNG so much bigger than the original WebM?

WebM is a lossy video codec storing inter-frame deltas; PNG stores every pixel of every frame losslessly. A 2-second 1080p VP9 clip might be 400 KB, while a single 1080p PNG frame from it can be 2-4 MB and a 60-frame sequence can blow past 100 MB. To shrink output, lower Image resolution to a preset like 720P, drop Colors to 256 (8-bit indexed), or raise Compression level to 9 — all three are lossless or near-lossless for screenshots and UI captures.

Which frame does "Specific Frame" actually pick if I leave Time blank?

The default is the first decoded frame (t = 0), which for many WebMs is a near-black keyframe before the encoder ramps up. For a meaningful still, set Time (seconds) to a value at least 0.5-1 s into the clip, or use Multiple Screenshots and pick the best frame from the ZIP.

Does the converter handle VP8, VP9, and AV1 WebM?

Yes — the WebM specification requires VP8 and VP9 support, with AV1 as an additional permitted codec, and all three decode correctly here. If a clip refuses to load, the most common cause is a .webm that's actually a different container with a renamed extension; try WebM to MP4 first to normalize the file, then extract frames.

Should I use PNG or JPG for the extracted frames?

Use PNG when the frame contains text, UI, line art, transparency, or you need bit-exact archival quality — PNG is lossless. Use WebM to JPG when the frame is a photographic scene and you care about file size: JPEG at quality 85 will be 5-10x smaller than the equivalent PNG, with no visible loss for photo content.

What does the Colors dropdown actually do, and why would I lower it?

It quantizes the image to an indexed palette (256, 128, 64, 32, 16, 8, 4, or 2 colors) before encoding. PNG-8 with 256 colors is a fraction of the size of PNG-24 truecolor and is perfect for screenshots, app UI, icons, and pixel art. For photographs, stick with ORIGINAL truecolor — palette reduction will cause visible banding in skies and gradients.

How many PNGs will Multiple Screenshots produce?

It depends on the interval you set. A 20-second clip with "1 frame per second" gives 20 PNGs; the same clip at 30 fps with "every frame" gives 600 PNGs (20 x 30). The output ZIP filenames are zero-padded and ordered, so you can drop the sequence straight into After Effects, Premiere, or an ffmpeg -framerate pipeline.

Is my file uploaded to a server, and what's the size limit?

Files move to the xconvert worker to be decoded and re-encoded — full server-side processing is required because in-browser WebM frame seeking is unreliable across codecs. Files are auto-deleted shortly after conversion; no sign-up, no watermark, no permanent storage. There's no hard per-file cap published, but very large WebMs (multi-GB screen recordings) are slower; for those, consider trimming with WebM to MP4 first or pulling only the seconds you need with the Time input.

Can I get a transparent PNG sequence for use as a video overlay on a website?

Yes — extract the sequence with Multiple Screenshots at the source frame rate, keep Colors on ORIGINAL so the alpha channel survives, and you'll get a PNG sequence with transparency. For modern web use, also consider re-encoding the result to APNG or animated WebP via PNG to WebP — both deliver smaller files than a PNG sequence and play natively in browsers.