What is a WMV file?

WMV is a container: a wrapper that holds streams encoded by something else. It is used for handing a finished file over.

The extension is .wmv, and the full name is Windows Media Video. Both matter less than what the file can hold, which is what the rest of this page is about.

Microsoft published it in 1999.

A format that has been readable for that long is a format worth trusting with something you want back in ten years.

Reading it outside the vendor’s own software depends on work done by other people, usually by inspection rather than by documentation. That mostly works and occasionally does not, which is the reason to convert anything you intend to keep.

The people who made it have moved on, and support is being withdrawn rather than added. Anything still in this format is worth moving while the tools to move it are still around.

It usually holds WMV9 and VC-1. This is the distinction behind most "why will this not play" questions: two files with the same extension can contain entirely different encodings, and a player that refuses one may be perfectly happy with the other.

It also explains why changing container is often fast and lossless while changing codec is neither. Moving the same stream into a different box rewrites the box; re-encoding rewrites the picture.

WMV can hold several audio tracks.

That matters mostly when converting: whatever the target cannot hold is dropped, usually without a warning.

Windows Media Player and VLC read it, and so do most programs of the same kind.

If a file will not open, the format is rarely the problem — it is more often that the program predates it. Converting to something older is the reliable way past that, and it is what the rest of this site is for.

No browser reads it.

That is the single most common reason to convert it: not that the format is bad, but that the place you want to show the file cannot read it.

WMV is meant to be handed over rather than worked in. Editing one is possible and rarely pleasant; the sane approach is to change the source and export again.

The recurring complaints: support outside its home ground is uneven.

None of these is a reason to avoid the format. They are the things worth knowing before you are surprised by one, which is a different claim and a more useful one.

Between roughly 1999 and 2012, a very large amount of institutional video was WMV: training modules, recorded webinars, internal announcements, screen captures made with Camtasia or Windows Media Encoder, conference recordings, and the video files embedded in PowerPoint decks.

The reason was defaults. Windows Movie Maker exported WMV, Media Encoder produced it, PowerPoint expected it, and the intranet streamed it. Nobody chose the format; it was what the toolchain did. Which is why it survives in exactly one place — organisational archives — and almost nowhere else.

VLC, and not much else worth relying on. No browser plays WMV, so it cannot be embedded in a modern intranet page or a learning platform. Phones and tablets do not. Macs need a third-party player. Smart televisions and meeting-room systems refuse it.

For an archive intended to be watchable, that is the whole problem. A training library nobody can open on a laptop, a phone or the screen in a meeting room has stopped being a library and become a storage cost.

A WMV is an ASF container holding Windows Media Video — usually version 9, which SMPTE standardised as VC-1 in 2006 — with WMA audio beside it. That makes it H.264’s contemporary rather than its ancestor; both were mandatory codecs on Blu-ray. What it lacks is reach, because almost nothing outside Windows will decode it.

The size comes from how these files were made rather than from the codec. Windows Media Encoder presets and screen-capture tools of the period ran at bitrates nobody would choose now, and encoder quality has moved on a long way since. Re-encoding an archive at a current setting frequently reduces it substantially while making it more watchable, which is an unusually easy argument to make to whoever pays for the storage.

Unlike MOV and MP4, which are close relatives whose streams can sometimes be rewrapped, WMV and MP4 share nothing. The video has to be decoded and encoded again, which costs time proportional to the length of the material and a generation of quality.

So it is worth doing once, from the best copy, at a decent setting — not repeatedly and not from a file somebody already converted. For an archive, that means finding the original master rather than the copy that has been on the shared drive since 2011, if such a thing still exists.

A large share of surviving WMV is screen capture: software demonstrations, training walkthroughs, recorded presentations. That material is mostly text and flat interface, and it behaves nothing like camera footage.

Encoding it like a film blurs the text and makes the recording useless for its actual purpose. A higher bitrate helps, and keeping the original resolution matters more than anything — a 1280-pixel screen recording scaled to 720 loses the small type it exists to show. If the choice is between a smaller file and readable text, the text is the content.

Windows Media supported DRM, and corporate and educational video from the period sometimes carries it — licensed to a domain, a machine or a login. Those licence servers are almost universally gone.

A protected file cannot be converted and will report an error rather than producing video. If a whole archive refuses, that is why, and the remaining route is a working licence on a machine that still has one — which in practice means the material is lost. Worth checking a sample before planning a migration around it.

Convert to MP4 with H.264, which plays on every browser, phone, television and meeting-room system without anything installed, and will still do so in ten years. That is the whole decision; there is no serious alternative for material that has to remain watchable.

Then keep a copy of the originals somewhere cold. Not because WMV is worth anything, but because a conversion run is easy to get wrong across five hundred files, and discovering a settings mistake after the source has been deleted is the one failure mode that cannot be repaired.