Convert MOV to M4V — Free Online Tool
Convert MOV files to M4V for iTunes, Apple TV, and iOS devices using H.264 video and AAC audio — the native codec pairing Apple uses for its own video downloads. This tool runs entirely in your browser using WebAssembly, so your files never leave your device.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your MOV 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
MOV and M4V are both MPEG-4-derived container formats from Apple, so this conversion is more of a container re-wrap than a full transcode — but it's not a lossless remux. Because MOV files can carry a wide variety of codecs (VP9, MJPEG, PNG video, Opus audio, FLAC, etc.), the tool standardizes the output to H.264 video encoded with libx264 and AAC audio, which are the codecs that define M4V compatibility with iTunes and iOS. If your source MOV already uses H.264 and AAC, re-encoding still occurs to ensure clean M4V compliance, though quality loss is minimal at the default CRF 23 setting. The -movflags +faststart flag relocates the MP4 metadata atom to the beginning of the file, enabling progressive streaming playback before the full file is downloaded — a key requirement for web and Apple device delivery.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary. In the browser version of this tool, FFmpeg runs as a WebAssembly module (FFmpeg.wasm) with no server involvement — the same command can be run locally on any desktop with FFmpeg installed. |
-i input.mov
|
Specifies the input file as a MOV container. FFmpeg will detect all streams inside — which could include H.264, MJPEG, VP9, AAC, FLAC, Opus, or other codecs depending on how the MOV was created. |
-c:v libx264
|
Re-encodes the video stream using the libx264 H.264 encoder, the required video codec for M4V compatibility with iTunes and iOS. Any source video codec in the MOV — including MJPEG, VP9, or PNG video — will be transcoded to H.264. |
-c:a aac
|
Re-encodes the audio stream to AAC using FFmpeg's native AAC encoder, which is the standard audio codec for M4V and required for iTunes and Apple device compatibility. Source audio in formats like FLAC, Opus, or MP3 embedded in the MOV will be transcoded to AAC. |
-crf 23
|
Sets the Constant Rate Factor for libx264 to 23, the widely recommended default that balances visual quality and file size for H.264 output. Lower values (e.g., 18) produce higher quality at larger file sizes; higher values (e.g., 28) reduce bitrate at the cost of visible compression artifacts. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, a standard quality level appropriate for stereo content in iTunes and iOS video files. Increase to 192k or 256k for music-heavy content or when audio fidelity is a priority. |
-movflags +faststart
|
Moves the MP4/M4V metadata ('moov' atom) to the beginning of the output file after encoding completes. This is essential for streaming playback on Apple TV, iOS, and Safari, as it allows the player to start rendering video before the entire file has been downloaded. |
output.m4v
|
Specifies the output filename with the .m4v extension, which signals to iTunes, QuickTime, and iOS that the file is an Apple-format MPEG-4 video container optimized for their ecosystem. |
Common Use Cases
- Preparing video content for distribution through iTunes or the Apple TV app, where M4V is the expected and natively supported container format
- Converting professional video exports from Final Cut Pro or DaVinci Resolve (which often output MOV) into M4V files for sideloading onto iPhones and iPads via Finder
- Packaging tutorial or course videos recorded on a Mac for delivery through platforms that require Apple-compatible M4V files with chapter markers intact
- Converting MOV footage that uses exotic codecs like MJPEG or VP9 into H.264/AAC M4V so the file plays natively in QuickTime Player and iOS without third-party apps
- Archiving home videos or event recordings originally in MOV format into M4V for long-term storage in an iTunes library with preserved chapter and metadata support
- Optimizing MOV files with the +faststart flag for HTTP streaming delivery to Apple devices, where the metadata-first structure enables instant playback
Frequently Asked Questions
Yes, some generation loss occurs because the video is re-encoded to H.264 using libx264, even if the source MOV already contains H.264. At the default CRF 23 setting, quality loss is minimal and virtually indistinguishable for most content. If your source is a high-quality ProRes or MJPEG MOV from a professional camera or editing timeline, consider lowering the CRF value (e.g., CRF 18) to preserve more detail — though this will increase file size.
Transparency is lost. MOV supports alpha channels through codecs like PNG video or certain ProRes profiles, but M4V does not support transparency at all — it is a lossy-only format based on MPEG-4. During conversion, the alpha channel is dropped and the video is composited against a black background by default. If you need to preserve transparency, M4V is the wrong target format.
Yes. M4V supports both chapter markers and multiple audio tracks, and FFmpeg will carry these through from a MOV source that contains them. This makes the MOV-to-M4V conversion particularly well-suited for long-form content like films or course videos where chapters and alternate language audio tracks need to survive the conversion intact.
Both are built on the ISO Base Media File Format (ISOBMFF) and are structurally very similar, which is why conversion between them is essentially a container re-wrap. The practical difference is intent: MOV is Apple's general-purpose, production-oriented container that accepts a wide range of codecs for editing flexibility, while M4V is Apple's distribution-oriented format locked to H.264 or H.265 video with AAC audio, designed for iTunes Store compatibility and optional FairPlay DRM. An M4V file is essentially an MP4 that Apple has branded for its ecosystem.
To adjust video quality, change the -crf value: lower numbers (e.g., -crf 18) mean higher quality and larger files, while higher numbers (e.g., -crf 28) reduce quality and file size. The valid range for libx264 is 0–51. To change audio bitrate, replace -b:a 128k with your preferred rate — for example, -b:a 192k for higher-fidelity audio or -b:a 96k to reduce file size. A full custom command would look like: ffmpeg -i input.mov -c:v libx264 -c:a aac -crf 18 -b:a 192k -movflags +faststart output.m4v
Yes. On macOS or Linux you can use a shell loop: for f in *.mov; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart "${f%.mov}.m4v"; done. On Windows Command Prompt, use: for %f in (*.mov) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart "%~nf.m4v". This browser-based tool processes files one at a time, so the FFmpeg command is especially useful for batch workflows involving large collections of MOV files.
Technical Notes
MOV and M4V share the same MPEG-4 container DNA, but M4V enforces a much stricter codec subset. The output is constrained to libx264 (H.264) for video and AAC for audio, which means any MOV carrying VP9, libvorbis, Opus, FLAC, or MJPEG streams must be fully transcoded — not simply remuxed — to produce a valid M4V. The -movflags +faststart flag is critical for Apple ecosystem delivery: it runs a second pass to move the 'moov' atom to the front of the file, allowing QuickTime Player, Safari, and iOS to begin playback before the entire file is buffered. Subtitle tracks in MOV (typically stored as text or tx3g) are preserved in M4V, which also uses tx3g, so soft subtitles survive the conversion. One notable limitation: M4V has no transparency support whatsoever, unlike MOV which can carry RGBA video via PNG or ProRes 4444 codecs — any alpha channel data in the source will be silently discarded. File sizes after conversion are typically smaller than the original MOV if the source used a lossless or high-bitrate intermediate codec, and comparable or slightly larger than a well-optimized H.264 MOV source at the same CRF value.