Convert M4V to WTV — Free Online Tool
Convert M4V files from iTunes or iOS libraries into WTV format compatible with Windows Media Center's DVR ecosystem. This tool re-encodes the video using H.264 and packages it in the Windows Television container, letting you integrate Apple-sourced content into a PC-based home theater setup.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your M4V 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
M4V is essentially an MPEG-4 container with Apple-specific extensions, typically carrying H.264 video and AAC audio — and sometimes FairPlay DRM. When DRM-free, the H.264 video stream is re-encoded into a new H.264 stream tuned for the WTV container, and the AAC audio is re-encoded at the specified bitrate. WTV is a proprietary Microsoft format designed around broadcast TV recordings, so the conversion also strips M4V-specific metadata like iTunes chapter markers and multi-audio track structures that WTV either doesn't support or handles differently. The result is a file Windows Media Center can recognize and play as if it were a local broadcast recording.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary, the open-source multimedia processing engine that handles the M4V-to-WTV conversion. In this browser tool, it runs via FFmpeg.wasm compiled to WebAssembly — no installation required. |
-i input.m4v
|
Specifies the input file in M4V format — Apple's MPEG-4 container used for iTunes and iOS video, typically carrying H.264 video and AAC audio. FFmpeg reads and demuxes the M4V streams for re-encoding. |
-c:v libx264
|
Sets the video encoder to H.264 using the libx264 library, which is the default and most compatible video codec for WTV. The M4V source likely already contains H.264, but a full re-encode is required to fit the WTV container structure. |
-c:a aac
|
Sets the audio encoder to AAC, which is the default audio codec for WTV output and matches the most common audio format in M4V source files. The audio is re-encoded to ensure proper stream framing within the WTV container. |
-crf 23
|
Sets the Constant Rate Factor for H.264 video quality at 23, which is the FFmpeg default and produces a good balance of quality and file size for typical M4V content. Lower values like 18 increase quality at the cost of a larger WTV file. |
-b:a 128k
|
Sets the audio bitrate to 128 kilobits per second for the AAC stream in the WTV output. This is adequate for stereo dialogue and music tracks from typical M4V content; raise it to 192k or 256k if the source has high-quality surround audio. |
output.wtv
|
Specifies the output filename with the .wtv extension, which signals FFmpeg to mux the encoded streams into the Windows Television container format recognized by Windows Media Center. |
Common Use Cases
- Adding DRM-free iTunes movie or TV show purchases to a Windows Media Center library so they appear alongside recorded broadcast content
- Archiving Apple-format home videos into a Windows-based DVR system for long-term storage and playback on Media Center extenders
- Importing M4V lecture recordings or training videos into a Windows Media Center setup used as a dedicated home theater PC
- Converting M4V content downloaded from Apple platforms for playback on older Windows Vista or Windows 7 Media Center setups that natively recognize WTV
- Migrating a video library from an Apple ecosystem to a Windows-centric home entertainment system without relying on iTunes for playback
Frequently Asked Questions
No. WTV does not support chapter metadata, so any chapter structure embedded in the M4V — common in iTunes movies and episodic content — will be lost during conversion. If preserving chapters is important, you should export them separately before converting. The video and audio content itself is fully preserved.
No. FairPlay DRM-protected M4V files cannot be decoded by FFmpeg or any standard conversion tool, including this one. The conversion will fail or produce a blank video. Only DRM-free M4V files — such as those marked as iTunes Extras, self-encoded M4V files, or content you've personally ripped — can be processed.
This conversion performs a full re-encode of the video stream rather than a simple container copy, because WTV's structure differs fundamentally from M4V's MPEG-4 base. Re-encoding at CRF 23 (the default) produces visually transparent quality for most content, but each generation of encoding introduces a small amount of additional compression loss. If you want higher fidelity, lower the CRF value — try CRF 18 for near-lossless H.264 output.
To change video quality, modify the -crf value: lower numbers (e.g., 18) mean higher quality and larger files, while higher numbers (e.g., 28) reduce quality and file size. CRF 23 is the H.264 default and a solid starting point for most M4V content. To change audio quality, replace 128k in -b:a 128k with a value like 192k or 256k for better fidelity, which is worth doing if your source M4V has high-bitrate audio tracks.
By default, FFmpeg maps only the first audio track when converting to WTV. If your M4V contains multiple audio tracks — such as a foreign-language dub or a director's commentary track — only the primary track will be included in the output. To include additional tracks, you would need to add explicit -map flags to the FFmpeg command, such as -map 0:a:0 -map 0:a:1.
The single-file command shown can be adapted for batch processing using a shell loop. On Windows, you can use a FOR loop in Command Prompt: for %f in (*.m4v) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "%~nf.wtv". On macOS or Linux, use: for f in *.m4v; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k "${f%.m4v}.wtv"; done. This is especially useful for large collections exceeding the 1GB browser limit.
Technical Notes
The WTV format was introduced with Windows Vista Media Center as a successor to the DVR-MS format, and it is specifically designed to store broadcast television recordings with embedded EPG metadata. When converting from M4V, the H.264 video stream must be fully re-encoded rather than stream-copied, because WTV's internal framing and metadata headers differ from the MP4/M4V container structure even when both ultimately carry H.264. The AAC audio codec is shared between both formats, but it is still re-encoded to ensure proper stream framing within WTV. Notably, the -movflags +faststart flag used in M4V for web streaming has no equivalent or relevance in WTV, so it is omitted. WTV does support multiple audio tracks and subtitle streams, but chapter support is absent — a meaningful limitation when converting iTunes content that often relies on chapters for scene navigation. The MJPEG video codec is technically available in WTV, but H.264 is strongly preferred for its compression efficiency and compatibility with Media Center playback engines. File sizes for WTV output will typically be similar to or slightly larger than the source M4V at equivalent CRF settings, due to WTV's overhead from broadcast-style metadata structures.