Convert WTV to M4V — Free Online Tool
Convert WTV recordings from Windows Media Center into M4V files compatible with iTunes, iOS devices, and Apple TV. This tool re-encodes the video stream using H.264 and wraps it in Apple's MPEG-4 container with the +faststart flag, making your recorded TV content immediately streamable on Apple devices.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your WTV file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
WTV (Windows Television) files produced by Windows Media Center typically contain H.264 or MPEG-2 video alongside AAC or AC-3 audio, wrapped in Microsoft's proprietary broadcast-recording container. During this conversion, FFmpeg decodes the WTV container and re-encodes the video stream using libx264 (H.264) at CRF 23, which provides a visually transparent quality level suitable for recorded TV content. The audio is encoded to AAC at 128k, which is natively supported by all Apple devices. The output is written into an M4V container — essentially an MPEG-4 file — with the -movflags +faststart flag applied, which relocates the moov atom to the beginning of the file so playback can begin before the entire file is downloaded. WTV-specific metadata such as program title, channel, and recording timestamp may be partially preserved depending on how FFmpeg maps the metadata fields, but WTV's DVR-specific broadcast metadata will not carry over fully into M4V.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg multimedia processing tool, which handles demuxing the WTV container, decoding its video and audio streams, re-encoding them, and muxing the result into the M4V container. |
-i input.wtv
|
Specifies the input WTV file recorded by Windows Media Center. FFmpeg automatically detects the container format and identifies the enclosed video and audio streams, which may be H.264, MPEG-2, or VC-1 video alongside various broadcast audio formats. |
-c:v libx264
|
Encodes the output video stream using the H.264 codec via libx264. This is required because M4V only supports H.264 or H.265, and WTV recordings may contain MPEG-2 or VC-1 video that must be transcoded into a format Apple devices can natively decode. |
-c:a aac
|
Encodes the audio stream to AAC using FFmpeg's native AAC encoder, which is the preferred audio codec for M4V files and is natively decoded by all Apple devices, iOS, and the iTunes/Apple TV ecosystem without any compatibility issues. |
-crf 23
|
Sets the Constant Rate Factor for H.264 encoding to 23, FFmpeg's default quality level. For broadcast TV recordings from Windows Media Center, this typically produces output that is visually indistinguishable from the source while keeping file sizes manageable. Lower values (e.g., 18) produce higher quality at larger file sizes. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, which is a standard quality level for stereo broadcast TV audio and is well-suited to the typical 2-channel audio found in most Windows Media Center recordings. Increase to 192k or 256k for recordings with rich audio content. |
-movflags +faststart
|
Moves the M4V file's moov atom (the container index) to the start of the file after encoding completes. This is essential for Apple compatibility, enabling AirPlay streaming, iTunes import, and web-based playback to begin before the entire converted recording has been transferred or downloaded. |
output.m4v
|
Specifies the output filename with the .m4v extension, which tells FFmpeg to wrap the encoded H.264 video and AAC audio into Apple's MPEG-4 container format. The .m4v extension signals iTunes and iOS that this file is Apple-compatible content. |
Common Use Cases
- Transferring recorded TV shows from a Windows Media Center PC to an iPhone, iPad, or Apple TV for offline viewing without needing a Windows ecosystem
- Importing a captured broadcast recording into iTunes or the Apple TV app to organize it alongside purchased TV content in your Apple library
- Archiving old Windows Media Center recordings in a widely supported format before decommissioning a legacy Windows Vista or Windows 7 Media Center PC
- Editing recorded TV footage in iMovie or Final Cut Pro, which prefer M4V or MP4 containers with H.264 video over the proprietary WTV format
- Streaming a recorded sports event or documentary from a Windows Media Center library to an Apple TV or AirPlay-compatible device via a local media server
- Sharing a recorded TV clip with someone using an iPhone or Mac, where WTV files would otherwise require specialized software to play
Frequently Asked Questions
Yes, this is a lossy transcode because the video is re-encoded through libx264 rather than simply remuxed. WTV files often contain H.264 or MPEG-2 video, and since M4V does not natively support MPEG-2, a full re-encode is required. At the default CRF 23, the quality loss is generally imperceptible for broadcast TV recordings, which are already compressed. If you want higher fidelity, lower the CRF value toward 18 in the FFmpeg command.
M4V is Apple's variant of the MPEG-4 container, functionally nearly identical to MP4 but signaling Apple-specific compatibility including potential FairPlay DRM support. Apple devices and iTunes recognize the .m4v extension natively. If you rename the output to .mp4, it will play on virtually all other platforms too, since the underlying H.264 video and AAC audio are identical — only the container extension differs.
Partially. FFmpeg can map some WTV metadata fields — such as the program title and description — into standard M4V/MPEG-4 metadata atoms, but WTV's broadcast-specific fields like channel number, original air date, and series link data are proprietary to the Windows Media Center DVR system and will not transfer meaningfully into M4V. You may need to manually set iTunes metadata (title, episode number, show name) after conversion using a tool like MP3Tag or iTunes itself.
The -movflags +faststart flag moves the moov atom — the index data that tells a player where all the video and audio chunks are located — to the beginning of the M4V file. By default, FFmpeg writes this atom at the end of the file after encoding finishes. Moving it to the front allows web players, AirPlay, and streaming media servers to begin playback before the full file is downloaded, which is especially useful when serving recorded TV content from a NAS or home media server to Apple TV.
WTV files from Windows Media Center sometimes contain multiple audio tracks, such as a primary broadcast track and a secondary language track. By default, FFmpeg maps only the first audio track and encodes it to AAC at 128k. To increase audio quality, change -b:a 128k to -b:a 192k or -b:a 256k. To include all audio tracks in the M4V output, add -map 0:v -map 0:a to the command before the output filename, which instructs FFmpeg to map all video and audio streams from the WTV source.
Yes. On Windows, open a Command Prompt in the folder containing your WTV files and run: for %f in (*.wtv) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart "%~nf.m4v". On macOS or Linux, use: for f in *.wtv; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart "${f%.wtv}.m4v"; done. This is particularly useful for archiving an entire Windows Media Center library in one pass.
Technical Notes
WTV is a container format introduced with Windows Vista Media Center that wraps broadcast TV recordings using Microsoft's Advanced Systems Format (ASF) variant. It can contain H.264, MPEG-2, or VC-1 video depending on the broadcast source and tuner hardware, alongside AAC, AC-3, or MP2 audio. Because M4V only supports H.264 and H.265 for video, any VC-1 or MPEG-2 streams must be fully decoded and re-encoded — there is no stream copy path available. This conversion uses libx264 at CRF 23, which is FFmpeg's default quality level and works well for standard-definition and high-definition broadcast recordings. The resulting file size will typically be smaller than the original WTV if the source was MPEG-2, or similar in size if the source was already H.264. Subtitles embedded in WTV recordings (often as CEA-608/708 closed captions from the broadcast stream) are not automatically mapped into the M4V output by this command; to include them, you would need to add -c:s mov_text and appropriate -map flags. The M4V container supports chapters, which WTV does not, so no chapter data will be present in the output unless added separately. Files processed in-browser are subject to the 1GB limit; for larger WTV recordings from extended recordings or high-bitrate HD broadcasts, use the displayed FFmpeg command directly on your desktop.