Convert M4V to MP4 — Free Online Tool

Convert M4V files to MP4 by re-encoding with H.264 and AAC — the same codecs already used in most M4V files — while stripping iTunes-specific DRM wrappers and container restrictions. The result is a universally compatible MP4 file that plays on virtually any device, browser, or media player without Apple ecosystem dependencies.

FFmpeg Command

Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg

Free — no uploads, no signups. Your files never leave your browser.

Estimated output:

Conversion Complete!

Download

How It Works

M4V and MP4 are closely related container formats — M4V is essentially Apple's branded extension of the MPEG-4 container, so the video and audio codecs inside are typically identical (H.264 video and AAC audio). This conversion re-encodes the video stream using libx264 at CRF 23 and the audio at 128k AAC, which means the content is decoded and re-encoded rather than simply remuxed. Re-encoding ensures compatibility with all MP4-compliant players and removes any Apple-specific container metadata or FairPlay DRM signaling. The -movflags +faststart flag repositions the MP4 index (moov atom) to the beginning of the file, enabling progressive streaming and faster playback starts in browsers and media servers.

What Each Flag Does

Flag What it does
ffmpeg Invokes the FFmpeg command-line tool. In the browser-based version of this tool, the same FFmpeg engine runs via WebAssembly (ffmpeg.wasm) entirely within your browser without sending any files to a server.
-i input.m4v Specifies the input M4V file. FFmpeg reads the Apple MPEG-4 container and demuxes the internal video and audio elementary streams for processing.
-c:v libx264 Re-encodes the video stream using the libx264 encoder, producing H.264 output in a codec profile that is universally supported in MP4 players — even if the source M4V already contained H.264, re-encoding ensures the output has clean, standard-compliant headers without Apple-specific extensions.
-c:a aac Re-encodes the audio stream using FFmpeg's native AAC encoder. Since M4V files nearly always carry AAC audio, this maintains format consistency in the output MP4 while ensuring the audio track conforms to standard MP4 AAC packaging rather than Apple's variant.
-crf 23 Sets the Constant Rate Factor for libx264 to 23, which is the default quality level offering a good balance between file size and visual quality for the H.264 codec. Lowering this value (e.g., to 18) increases quality and file size; raising it (e.g., to 28) reduces both.
-b:a 128k Sets the AAC audio bitrate to 128 kilobits per second, a standard bitrate that provides clear stereo audio for most M4V content including iTunes videos and iPhone recordings. Raise to 192k or 256k if the source M4V has high-fidelity audio worth preserving.
-movflags +faststart Moves the MP4 moov atom (the file's index metadata) to the beginning of the output file after encoding completes. This is essential for web delivery — it allows browsers and streaming players to begin playing the MP4 before the entire file has been downloaded.
output.mp4 Specifies the output filename with the .mp4 extension, telling FFmpeg to write a standard MPEG-4 Part 14 container. Unlike .m4v, the .mp4 extension is universally recognized by all operating systems, browsers, and media players without requiring Apple software.

Common Use Cases

  • Playing iTunes video downloads on non-Apple devices like Android tablets, smart TVs, or Windows media players that don't recognize the .m4v extension
  • Uploading Apple-purchased or recorded M4V content to video platforms like YouTube, Vimeo, or Wistia that expect standard MP4 containers
  • Embedding video in websites or web apps where the .m4v extension causes browser MIME type mismatches or playback failures
  • Archiving old iTunes movie or TV show downloads into a format-agnostic container before migrating away from the Apple ecosystem
  • Preparing M4V files for use in video editing timelines in tools like DaVinci Resolve or Premiere Pro that handle .mp4 more reliably than .m4v
  • Stripping Apple-specific chapter and metadata structures from M4V recordings made on iPhone or iPad before sharing with non-Apple collaborators

Frequently Asked Questions

Because both the input M4V and output MP4 use the same codecs (H.264 and AAC), re-encoding introduces a small generation loss compared to a lossless remux. At the default CRF 23 setting, the quality difference is minimal and not perceptible during normal viewing, but it is not a bit-for-bit copy of the original. If preserving maximum quality is critical, you can lower the CRF value (e.g., to 18) at the cost of a larger output file.
In many cases a direct stream copy (remux) would work, but M4V files from iTunes may contain FairPlay DRM metadata, Apple-specific track flags, or codec profile settings that cause compatibility problems in standard MP4 players. Re-encoding with libx264 and AAC produces a clean, fully standard-compliant MP4 that any player can handle. For DRM-protected M4V files purchased from iTunes, re-encoding is not possible without first removing the DRM through authorized means.
The FFmpeg command shown here copies video and audio streams but does not explicitly map subtitle tracks or additional audio tracks. If your M4V contains multiple audio tracks or embedded subtitles, you would need to add '-map 0' to the command to include all streams, or '-map 0:s' to specifically carry over subtitle tracks. Chapters stored in the M4V container are generally preserved in the output MP4 by default.
FFmpeg by default writes the MP4 moov atom (the index that describes all the media tracks) at the end of the file after encoding is complete. The +faststart flag runs a post-processing step that moves the moov atom to the beginning of the file. This is critical for web streaming because browsers and media servers can begin buffering and playing the video before the entire file is downloaded, instead of waiting for the index at the end.
The -crf 23 flag controls video quality using libx264's Constant Rate Factor. Lower values produce higher quality and larger files — CRF 18 is considered visually near-lossless, while CRF 28 produces noticeably smaller files with some quality reduction. The scale runs from 0 (lossless) to 51 (worst). For audio, change the -b:a 128k value to 192k or 256k for higher fidelity, or 96k to reduce file size when audio quality is less important.
Yes. On Linux or macOS, you can run a shell loop: 'for f in *.m4v; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart "${f%.m4v}.mp4"; done'. On Windows Command Prompt, use: 'for %f in (*.m4v) do ffmpeg -i "%f" -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart "%~nf.mp4"'. The browser-based tool processes one file at a time, so batch processing via the command line is especially useful for converting large collections.

Technical Notes

M4V is Apple's extension of the ISO Base Media File Format (ISOBMFF), sharing its foundational structure with MP4 but adding Apple-specific boxes for DRM (FairPlay), iTunes metadata tags, and content rating flags. When converting non-DRM M4V files — such as those recorded by iPhone or exported from iMovie — the internal H.264 video and AAC audio streams are technically identical to what MP4 uses, so the codec parameters remain compatible. Re-encoding with libx264 at CRF 23 produces H.264 video in the High profile by default, which is broadly compatible with virtually all hardware decoders. One consideration: M4V files from iTunes Store purchases are protected by FairPlay DRM and cannot be processed by FFmpeg or any conversion tool without prior DRM removal through legitimate means. For non-protected M4V content, metadata such as title, artist, and year stored in iTunes-style atom tags (©nam, ©ART, etc.) may not fully transfer to the MP4 output, as MP4 players typically read the same atom format but some iTunes-specific extended tags may be silently dropped. File size after conversion is largely determined by the source bitrate and the CRF value chosen — at CRF 23 the output will typically be similar in size to the original M4V for live-action content.

Related Tools