Initializing... drag & drop files here
Supports: ASF
This page grabs one frame out of an ASF (Windows Media) video and saves it as a WebP image. You pick the exact moment with a timestamp; the result is a single still, not an animation. WebP is worth choosing when the still is headed for a web page or an app, because Google measures it at 25–34% smaller than a JPEG of equivalent quality and 26% smaller than the same image as a lossless PNG. It is the wrong choice when the file has to open in older desktop software, and this page starts with that trade-off rather than burying it.
| Property | WebP (this page) | JPG | PNG |
|---|---|---|---|
| Compression | Lossy or lossless, your choice | Lossy only | Lossless |
| Relative size, same frame | Smallest — 25–34% under JPEG lossy, 26% under PNG lossless | Small | Largest |
| Bit depth | 8 bits per channel | 8 bits per channel | 8 or 16 bits per channel |
| Transparency | Supported (a video frame has none to keep) | Not supported | Supported |
| Maximum dimensions | 16,383 × 16,383 pixels | 65,535 × 65,535 pixels | Effectively unlimited |
| Browser display | Chrome 32+, Firefox 65+, Edge 18+, Safari 16 on macOS, iOS Safari 14+ | Universal | Universal |
| Old desktop viewers and editors | Patchy — many pre-2020 tools cannot open it | Universal | Universal |
| Underlying design | VP8 keyframe coding in a RIFF container, from Google | DCT, ISO/IEC 10918 | Deflate, W3C/ISO standard |
| Best for | Web thumbnails, previews, anything served over HTTP | Sharing and compatibility | Exact pixels, screenshots, text and line art |
.asf or .wmv onto the page, or click "+ Add Files" to browse. Several clips can be queued with the same settings.2.100 means 2 seconds and 100 milliseconds. Switch to Multiple Screenshots and set a Capture Rate (one frame per second by default) to sample across the clip..webp. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared.| Property | Value |
|---|---|
| Developer | Google, first released in 2010 |
| Container | RIFF, with the image data coded like a VP8 keyframe |
| Modes | Lossy, lossless, transparency, and animation |
| Size advantage | 25–34% smaller than JPEG at equivalent SSIM quality; 26% smaller than PNG when lossless |
| Alpha cost | About 22% extra bytes for lossless transparency; lossy transparency is typically a third the size of PNG |
| Maximum dimensions | 16,383 × 16,383 pixels |
| Browser support | Chrome 32+, Firefox 65+, Edge 18+, Safari 16 on macOS, iOS Safari 14+ — about 96% of tracked usage |
| Output here | A single still frame, at the video's native resolution unless you scale it |
A single still. This tool captures one frame at the timestamp you set under Time (seconds) and encodes it as a static WebP; switching to Multiple Screenshots gives you several separate stills in a ZIP, not one animated file. The WebP format itself does support animation — it has dedicated chunks for frames and looping — but assembling one is a different job from grabbing a frame. For a moving clip from the same source, ASF to GIF produces an animation that plays anywhere, and ASF to MP4 keeps it as video.
WebP if the image is going on the web, JPG if it is going anywhere else. Google's own measurements put lossy WebP 25–34% below a JPEG of equivalent SSIM quality, which is a real bandwidth saving on a page that carries many thumbnails. JPG's advantage is that literally everything opens it: old image viewers, print shops, embedded devices, document tools that were written before 2010. For a still that a colleague will double-click on an unknown computer, ASF to JPG is the safer answer.
Only when you actually need pixel fidelity. Set Lossless? to Yes when the still is an archival reference, a source for further editing, or a frame full of text and sharp UI edges where lossy ringing is visible. Leave it on "No (Recommended)" for web thumbnails and previews, where lossy WebP is dramatically smaller for a difference you have to hunt for. Note the honest limit either way: lossless preserves the frame the Windows Media decoder produced, and that frame already went through WMV's lossy compression.
Google publishes the figures it measured: lossy WebP images run 25–34% smaller than comparable JPEG images at an equivalent SSIM quality index, and lossless WebP runs 26% smaller than the same image as PNG. Transparency costs about 22% extra bytes in lossless mode, and lossy WebP with alpha is typically around a third the size of the PNG equivalent. Those are averages over image sets, not a guarantee for one particular frame — a noisy standard-definition video still compresses differently from a clean photograph.
Browsers are the easy part: Chrome from version 32, Firefox from 65, Edge from 18, Safari 16 on macOS and iOS Safari from 14, which together cover about 96% of tracked browser usage. Desktop software is patchier. Plenty of older image viewers, editors, and document tools have no WebP decoder at all and will simply refuse the file. If you are handing the still to someone else's computer rather than to a web server, grab it as JPG or PNG instead.
There is none to keep. Video frames are fully opaque — ASF carries Windows Media Video, and no consumer WMV workflow stores an alpha channel — so the WebP comes out as a solid image. That is not a limitation of the output format: WebP does support alpha in both lossy and lossless modes, at a cost of roughly 22% extra bytes when lossless. If you need a transparent background, that is a masking job for an image editor after extraction, not something the frame grab can produce.
Both problems come from the source, and both are fixed by moving the timestamp. A blurry grab means you landed on fast motion or a scene cut — nudge Time (seconds) by a tenth or two and convert again. Thin horizontal stripes through moving objects are interlacing: Windows Media captures from broadcast and camcorder sources are often interlaced, so a frame frozen mid-motion shows the two fields disagreeing. Pick a moment where the subject is still, and the comb artifacts disappear with it.
WebP tops out at 16,383 × 16,383 pixels, which no ASF frame will ever approach — a 1080p source is 1920 × 1080 — so the format is never the constraint. The real one is upload size and connection speed, since the extraction runs on our servers rather than on your own hardware; a long clip mostly costs you upload time. Uploads travel over an encrypted (TLS) connection, are processed on our servers, and both the source and the extracted still are deleted automatically after a few hours. Nothing is shared or made public, and no account is required.