Initializing... drag & drop files here
Supports: WMV
WMV (Windows Media Video) is Microsoft's codec family, with WMV 7 launched in 1999 and WMV 9 standardized as SMPTE 421M (VC-1) in March 2006. BMP is the much older sibling — Microsoft's uncompressed device-independent bitmap, baked into Windows since 1990 and into OS/2. Pulling stills out of a WMV as BMP gives you raw RGB pixels with no JPEG ringing, no PNG deflate pass, and no chroma subsampling — exactly what some legacy pipelines, lab tools, and embedded systems still demand.
| Property | WMV | BMP |
|---|---|---|
| Type | Video container + codec (Windows Media) | Still-image bitmap (Windows / OS/2) |
| Owner / origin | Microsoft, 1999 (WMV 7); VC-1 in 2006 | Microsoft / IBM, 1990 |
| Compression | Lossy DCT-based (VC-1 / MPEG-4 derivatives) | Uncompressed by default (optional RLE for 4/8-bit) |
| Bit depth | 8-bit YUV 4:2:0 typical | 1, 4, 8, 16, 24, 32 bpp (alpha since BITMAPV4HEADER, Windows 95) |
| Audio | Yes — usually WMA | None (still image) |
| Browser support | Limited — no native Chrome / Firefox / Safari decoder | Native in Chrome, Edge, Firefox, Safari, Opera |
| Typical use | Streaming, Windows-era recordings, screen captures | Legacy Windows apps, lossless reference, embedded GUIs |
| File size (1080p, 1 frame equivalent) | ~6-12 KB per frame at 2 Mbps | ~6.2 MB (24-bit, uncompressed) |
| Setting | What it does | Pick when |
|---|---|---|
| Specific Frame at 00:00 | One BMP at first frame | You only need a thumbnail or title card |
| Specific Frame at custom timestamp | One BMP at a chosen second | You want a specific scene (e.g., 1:23.5) |
| Multiple Screenshots every 1 second | One BMP per second of footage | Quick storyboard or timeline preview |
| Multiple Screenshots every 5-10 seconds | Sparse stills across a long clip | Surveying long screen recordings or lectures |
| Multiple Screenshots every N frames | Frame-accurate sequence | Computer-vision input or motion analysis |
| Quality preset High (default) | Standard color quantization | Most general use — visually identical to source |
| Quality preset Highest | Maximum fidelity, slower | Forensic / archival captures |
| Quality preset Low / Lowest | Faster, more aggressive downsampling | Thumbnails where size matters more than detail |
WMV is a heavily compressed video codec (lossy DCT in the MPEG-4 / VC-1 family), so a 1080p clip might average 2-5 Mbps — roughly 250-625 KB per second of video. A single uncompressed 24-bit BMP at 1920x1080 is about 6.2 MB by itself (1920 x 1080 x 3 bytes plus a small header, with each row padded to a multiple of 4 bytes). That is by design: BMP stores raw RGB pixels with no inter-frame prediction and no entropy coding. If size is a concern, convert WMV to PNG instead — PNG is lossless but applies DEFLATE compression and usually ends up 2-5x smaller for the same pixels.
Yes — under Frame Selection, switch to Multiple Screenshots and pick "every 1 frame" (or set the framerate dropdown to match the source). The output is a ZIP of sequentially numbered BMPs. Be aware of the math: a 60-second 30 fps 1080p clip yields 1,800 frames, which at 6.2 MB each totals roughly 11 GB uncompressed. For frame-accurate work but smaller files, choose JPG or PNG instead.
Standard output is 24-bit RGB (8 bits per channel, no alpha) — the most universally supported BMP variant. The BMP specification itself allows 1, 4, 8, 16, 24, and 32 bits per pixel, and alpha-channel BMPs have existed since the BITMAPV4HEADER shipped with Windows 95. Most decoders, especially older Windows tools, expect 24-bit, which is why we default to it.
Yes — keep "Specific Frame" selected and enter the time in the Time (seconds) field. Decimals work: 12.5 gives you the frame at 12.5 seconds. If the timestamp falls between two frames, the converter snaps to the nearest displayed frame.
It will look the same as the decoded video frame at that instant, but with two caveats. First, WMV uses 4:2:0 chroma subsampling — color information is stored at half resolution and is upsampled at decode time, so fine color edges may look slightly softer than a true RGB source. Second, any deblocking or post-processing applied by your media player (Windows Media Player, VLC, MPC-HC all do this differently) won't be applied during extraction, so flat-color regions may show subtle block boundaries on heavily compressed sources.
Yes — all common WMV variants are decoded server-side regardless of which Windows Media encoder produced the file. That covers WMV 7 (1999), WMV 8 (2001), WMV 9 (2003), and WMV 9 Advanced Profile / VC-1 (SMPTE 421M, 2006). Encrypted WMV files with DRM cannot be decoded — that's a license restriction, not a tooling limit.
BMP is the right answer specifically when something downstream requires it — legacy Windows software, embedded displays, certain CAD or lab pipelines, or any toolchain that explicitly rejects compressed images. For everything else (web use, sharing, archival, editing in modern tools), PNG gives you lossless storage at a fraction of the size, and JPG gives you tiny photographic stills. Major browsers do decode BMP, but the format is essentially never used on the web because file sizes are so much larger than the alternatives.
Yes. Drop multiple WMVs into the upload area and every clip uses the same Frame Selection and Image resolution settings. Each input produces either one BMP (Specific Frame mode) or a ZIP of BMPs (Multiple Screenshots mode). For converting full videos rather than extracting stills, see WMV to MP4 or WMV to GIF.
Anonymous uploads can handle multi-gigabyte WMVs, with practical decode time scaling roughly linearly with clip duration. For very long screen recordings (multi-hour lectures), prefer Multiple Screenshots with a wider interval (every 5-10 seconds) rather than every-frame extraction, otherwise the output ZIP can exceed 100 GB.