WAVE MP4
VC-1 · to · MP4

Convert raw VC-1 (.vc1) to MP4

VC-1 is a Microsoft-developed codec that shows up in Blu-ray remuxes and some old broadcast captures. Wave decodes the raw VC-1 elementary stream and re-encodes to H.264 in MP4, since VC-1 in an MP4 wrapper plays inconsistently across consumer devices.

Under the hood

What actually changes

VC-1 source VIDEO VC-1 (Annex B) AUDIO (none) MP4 new codecs VIDEO H.264 AUDIO (none) RE-ENCODE streams transcoded
VC-1 in MP4 plays inconsistently, so Wave re-encodes to H.264 for broad player support.

VC-1 (formally SMPTE 421M) is Microsoft's answer to H.264, developed in the mid-2000s and standardized under the same MPEG-4 Part 2 amendment that added HEVC in MP4. A .vc1 file is a raw VC-1 elementary stream in Annex B format - NAL-style start codes delimiting the bitstream, with no container and no audio track.

Even though MP4 has a registered codec entry for VC-1 (via the `vc-1` sample entry), broad player compatibility is poor: iOS refuses it, most Android players silently fail, and browsers do not decode it in a <video> element. Wave takes the pragmatic path and re-encodes the source through the on-device ffmpeg engine, then re-encodes to H.264 with the browser's WebCodecs H.264 encoder (or the LGPL MPEG-4 Part 2 fallback where WebCodecs H.264 is unavailable). The result is a plain H.264 in MP4 that plays everywhere. See <a href="/blog/h264-vs-hevc-vs-av1/">the codec comparison article</a> for why H.264 is the right target for maximum compatibility.

VC-1 was Microsoft's bid to become the dominant video codec of the mid-2000s, competing directly with H.264 for HD DVD, Blu-ray, Xbox 360, and Windows Media. It won the HD DVD standardization battle (HD DVD required VC-1) and briefly co-existed with H.264 on Blu-ray, but Blu-ray players started to favour H.264 and by 2010 the industry had consolidated. Microsoft still ships a VC-1 decoder in Windows Media Foundation and Xbox, and Silverlight streaming used VC-1 heavily; outside that ecosystem, native decoders are rare.

The visible file inventory today is small: some Blu-ray remuxes where the source was authored with VC-1, some older Silverlight-based streaming captures, and a handful of broadcast recordings from stations that used VC-1 encoders. Whenever you have a .vc1 file that needs to play anywhere modern, transcoding to H.264 is the honest answer - the alternative (VC-1-in-MP4) technically satisfies the container spec but plays on so few consumer devices that it defeats the purpose of converting in the first place.

How to convert

Three steps.

  1. 01

    Step 1

    Drop your .vc1 file onto the card.

  2. 02

    Step 2

    Wave inspects and shows Re-encode needed - VC-1 has to be transcoded for broad playback.

  3. 03

    Step 3

    Convert and save the MP4.

FAQ

Answers, specifically.

Where do VC-1 files even come from?

Almost always from Blu-ray remuxing tools that extracted the VC-1 stream separately, or from very old broadcast captures. Consumer cameras and modern encoding tools do not produce VC-1.

Could Wave remux to MP4 instead of re-encoding, if VC-1 is technically supported?

It could, but the resulting MP4 would fail to play on iOS and most Android devices, defeating the purpose of the conversion. Wave chooses the honest path: re-encode to H.264 so the output plays anywhere.

Will the quality drop noticeably?

Small transcoding loss, but Wave targets a bitrate that preserves the visible detail of the source. On typical Blu-ray-sourced VC-1 the output looks essentially identical at normal viewing distance.

The playback speed looks wrong. Why?

Raw VC-1 has no embedded timebase. Wave assumes 25 fps. If the source was captured at 24 (film) or 29.97 (broadcast), you can override the rate at the command line: `ffmpeg -r 24 -i input.vc1 -c:v libx264 -tag:v avc1 output.mp4` (requires a local ffmpeg install).

Can I stitch an audio track back in?

Not in Wave. On the command line: `ffmpeg -i video.vc1 -i audio.aac -c:v libx264 -c:a copy output.mp4` gives you a merged file in one pass.

What is the relationship between VC-1 and WMV3?

They are the same bitstream. WMV3 is Microsoft's early name for what became the VC-1 SMPTE standard. A .wmv file with WMV3 video and a .vc1 raw stream contain the same compression format - the difference is entirely in the wrapper. Wave transcodes both to H.264 on the way to MP4.

How is VC-1 quality compared to H.264?

Very close at the same bitrate. VC-1 was competitive with H.264 in the mid-2000s and won some quality tests. In 2026, H.264 encoders have improved further while VC-1 has not, so an H.264 re-encode at the same bitrate typically looks marginally better than the source. Wave targets a bitrate that preserves the visible detail.

Are there any players that natively handle raw VC-1?

VLC decodes raw .vc1 through its built-in vc1 decoder. MPC-HC on Windows does too. Consumer-grade players (Photos, Files, iOS Videos, Chromecast) do not. Converting to H.264 in MP4 is the way to get playback anywhere consumer devices go.

Related

Other converters.