Initializing... drag & drop files here
Supports: WMV
.tiff (recommended) or .tif if your downstream pipeline requires the legacy 8.3-style name.WMV is Microsoft's container/codec family — a .wmv file is almost always WMV3 (Windows Media Video 9) inside an ASF container, which Microsoft submitted to SMPTE and standardized as SMPTE 421M (VC-1) in March 2006. WMV is excellent for streaming and storage but useless as a delivery format to print shops, evidence reviewers, or scientific tools — those workflows want still images, and they want them lossless. TIFF, first published by Aldus in 1986 and now maintained by Adobe, is the long-running standard for that role: the Library of Congress lists baseline TIFF as a preferred preservation format for raster images, and it's the de facto handoff for print, archive, and forensic work.
| Property | WMV (source) | TIFF (output) |
|---|---|---|
| Type | Video container + codec | Still image (also multi-page) |
| Codec / encoding | Usually WMV3 (VC-1, SMPTE 421M, 2006) | Lossless or lossy compression of pixel arrays |
| Container | ASF (Advanced Systems Format) | Single TIFF or multi-page TIFF |
| Lossless? | No — VC-1 is lossy | Yes by default (LZW, Deflate, PackBits, None) |
| Bit depth | 8-bit per channel typical | 1, 8, 16, even 32-bit per channel |
| Color spaces | YUV 4:2:0 typical | RGB, CMYK, grayscale, Lab* |
| Native browser playback | Limited (Edge legacy / Windows) | None (image, not video) |
| Print & archival use | Not accepted | Industry default |
| Maintained by | Microsoft / SMPTE | Adobe (since 1994) |
| Typical extension | .wmv |
.tiff or .tif |
| Compression | Lossless? | Best for | Trade-off |
|---|---|---|---|
| LZW | Yes | General use; print delivery; 8-bit photos | Universal compatibility; modest size reduction |
| Deflate / ZIP | Yes | 16-bit photos, archival | Smaller than LZW (especially at 16-bit), but slower and slightly less broadly supported |
| PackBits | Yes | Simple imagery, baseline TIFF readers | Older RLE scheme; weak compression on photos |
| CCITT Fax 4 | Yes | 1-bit black-and-white scans / OCR pages | Bi-level only — won't work for color/grayscale |
| JPEG / Lossy | No | Smaller previews, web-style stills | Quality loss; some pro print tools reject JPEG-in-TIFF |
| WebP / JP2K / ZSTD | Optional | Modern compact archives | Reader support is uneven outside specialized tools |
| None | Yes | Maximum compatibility, master-grade archive | Largest file size |
For 8-bit photographic stills, LZW is the safe default. For 16-bit masters, Deflate/ZIP gives meaningfully smaller files because LZW can actually grow 16-bit data.
PNG is also lossless and is the right choice for web use; the case for TIFF is print, prepress, and archival. TIFF supports CMYK color, embedded ICC profiles, multi-page documents, 16-bit and 32-bit per-channel depths, and tagged metadata that survives professional workflows — none of which PNG handles fully. JPEG is lossy and re-encodes every save, which is unsafe for evidence or master-quality stills. If you're exporting to a phone or website, WMV to PNG or WMV to JPG is usually the better pick.
No — extraction is lossless relative to the decoded WMV frame, but the WMV itself was compressed with VC-1, which is a lossy codec. You're capturing the decoded pixels exactly as a player would render them, including any block artifacts or chroma subsampling already baked in. TIFF can't undo what VC-1 already discarded; it can only stop the next stage from adding more loss.
Choose None (uncompressed) or LZW so the file is bit-exact lossless. Avoid JPEG / Lossy / WebP for evidence — anything in that family changes pixel values. Many forensic SOPs additionally require a hash (SHA-256) of the exported file to be logged, which is straightforward with a lossless TIFF.
The cadence is configurable from one frame every 0.1 s (10 frames per second) to one frame every 10 s. A 60-second clip at "1 frame per second" produces 60 TIFFs; the same clip at "every 0.1 s" produces 600 TIFFs. The output is delivered as a ZIP. If you need every frame at the source frame rate, that's an image sequence — use a low interval and check that your downstream tool can handle the file count.
.tiff and .tif?Nothing technical — both are the same format. The three-letter .tif extension dates from FAT/MS-DOS 8.3 filename limits; modern systems are fine with .tiff. Use whatever your downstream tool expects. Some prepress workflows still default to .tif, while most current software accepts either.
Yes. In Specific Frame mode, set Time (seconds) to the offset you want; the unit dropdown lets you switch to minutes if that's easier. For sub-second precision, enter a fractional value such as 83.456. The accuracy is limited by WMV's keyframe interval — non-keyframes are reconstructed from the nearest preceding keyframe, so values land on the closest decoded frame.
Yes — those typically use the WMV Screen codec (MSS2) inside the same ASF container and decode normally. For very old WMV1/WMV2 files (pre-2003 webcam captures), the converter still extracts frames; the source quality just sits below modern WMV3/VC-1. If you also need the recording itself in a modern format, WMV to MP4 re-wraps it to H.264.
Most likely the chosen compression isn't supported by that app. JPEG-in-TIFF, ZSTD, JP2K, and WebP-in-TIFF are TIFF 6.0 extensions or later supplements and aren't required reading for "baseline TIFF" software. If you need maximum compatibility, re-export with LZW or None — the Library of Congress's preferred TIFF profile for preservation uses these.
WMV decoding happens server-side because there is no native WMV3/VC-1 decoder in browsers, but files are processed in your private session and removed after download. There's no account requirement, no watermark, and no third-party redistribution. If you'd rather work the other direction, TIFF to WMV and the related compress TIFF tool are also available.