Convert MKV to M4V — Free Online Tool

Convert MKV files to M4V for seamless playback on Apple devices, iTunes, and iOS. This tool re-encodes video using H.264 and audio using AAC — the codec pair native to Apple's M4V container — ensuring compatibility with iPhones, iPads, Apple TV, and the iTunes library ecosystem.

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

MKV is a flexible open container that can hold nearly any codec combination, which is exactly why re-encoding is required here: M4V only supports H.264 or H.265 video with AAC or MP3 audio. If your MKV already contains H.264 video, the video stream still needs to be placed into the M4V wrapper with proper Apple-compatible metadata. Audio tracks encoded as Opus, Vorbis, or FLAC — common in MKV files — must be transcoded to AAC. The FFmpeg command also applies the -movflags +faststart flag, which relocates the MP4/M4V metadata atom to the beginning of the file so Apple devices and web players can begin playback before the entire file is downloaded.

What Each Flag Does

Flag What it does
ffmpeg Invokes the FFmpeg program. When run locally on your desktop, this command must be typed in your terminal or command prompt with FFmpeg installed and available in your system PATH.
-i input.mkv Specifies the input file — your source MKV container. FFmpeg reads all available streams from this file, including video, audio, subtitles, and chapter metadata, before applying the output options.
-c:v libx264 Sets the video encoder to H.264 using the libx264 library. This is required because M4V only supports H.264 or H.265 video, and H.264 is chosen here for maximum compatibility with all Apple devices including older iOS hardware and Apple TV models.
-c:a aac Encodes the audio stream as AAC using FFmpeg's built-in AAC encoder. This is necessary because MKV sources frequently contain Opus, Vorbis, or FLAC audio, none of which are valid inside an M4V container — AAC is the native audio format for Apple's ecosystem.
-crf 23 Sets the Constant Rate Factor for H.264 encoding to 23, the default quality level. This controls the quality-to-filesize tradeoff: lower values like 18 produce larger, higher-quality files closer to the MKV source, while higher values like 28 produce smaller files with more compression.
-b:a 128k Sets the AAC audio bitrate to 128 kilobits per second. This is a widely accepted standard for stereo AAC audio that balances file size and audio fidelity — appropriate for most spoken word, music, and film audio tracks coming from an MKV source.
-movflags +faststart Moves the M4V file's metadata block (moov atom) to the beginning of the file after encoding completes. This is critical for Apple compatibility — it allows iPhones, iPads, Apple TV, and web-based Safari players to begin playback of the M4V immediately without waiting for the full file to load.
output.m4v Specifies the output filename with the .m4v extension. The M4V extension signals to iTunes, iOS, macOS, and Apple TV that this is an Apple-compatible MPEG-4 video file, enabling proper library import and device syncing behavior.

Common Use Cases

  • Adding a downloaded MKV movie or TV episode to your iTunes or Apple TV library, which requires the M4V format for proper metadata and chapter support
  • Preparing video content for distribution through Apple's ecosystem, including syncing to an iPhone or iPad via Finder or iTunes
  • Converting an MKV file that contains Opus or FLAC audio — incompatible with Apple devices — into an M4V with AAC audio that plays natively on iOS
  • Making a home video stored in MKV format compatible with Apple TV or AirPlay without relying on third-party codec packs or media server transcoding
  • Producing M4V files for web delivery to Safari users on macOS and iOS, leveraging the +faststart flag for immediate streaming playback
  • Converting MKV files with embedded chapter markers into M4V, preserving chapter navigation for use in Apple's native video players

Frequently Asked Questions

The default FFmpeg command used by this tool does not explicitly map subtitle streams, so embedded subtitles from the MKV will not be carried over to the M4V output. M4V does support subtitles in the MOV text or TX3G format, but MKV subtitles are commonly stored as ASS, SSA, or SRT, which require conversion. If you need subtitles in the output, you would need to modify the FFmpeg command to include subtitle mapping and specify a compatible subtitle codec such as mov_text.
This conversion re-encodes the video using H.264 at CRF 23, which is a high-quality lossy setting — visually lossless for most content at typical resolutions. There will be a small generational quality loss compared to the original, but at CRF 23 it is rarely perceptible. If your MKV source video was already encoded with H.264 at a similar or lower CRF, consider using a lower CRF value like 18 to minimize quality degradation during the re-encode.
M4V is built on the MPEG-4 Part 12 container specification, which Apple designed specifically for their ecosystem. That ecosystem is optimized for AAC, the audio codec Apple has promoted since the iPod era. MKV, by contrast, is a fully open container designed to hold virtually any codec without restriction. This means MKV files sourced from the internet commonly use Opus or Vorbis for audio — both of which must be transcoded to AAC when wrapping content in M4V for Apple compatibility.
By default, FFmpeg writes the moov atom — the metadata block that describes the file's structure — at the end of the MP4 or M4V file after encoding is complete. With +faststart, FFmpeg performs a second pass to move the moov atom to the beginning of the file. This means a media player or browser can begin reading and playing the video immediately without downloading the entire file first. It is especially important for M4V files served over HTTP or streamed to Apple devices, where progressive playback is expected.
Yes. The -crf 23 value controls quality using H.264's Constant Rate Factor scale, where lower numbers mean higher quality and larger files. For a higher-quality output closer to the MKV source, try -crf 18. For smaller files where some quality loss is acceptable — such as video intended for mobile storage — values like -crf 28 or -crf 35 will significantly reduce file size. The CRF scale for H.264 runs from 0 (lossless) to 51 (worst quality).
The single-file command shown here can be adapted for batch processing on the desktop. On Linux or macOS, you can run: for f in *.mkv; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart "${f%.mkv}.m4v"; done. On Windows Command Prompt, a for loop using %f as the variable achieves the same result. This browser-based tool processes one file at a time, so the FFmpeg command is especially useful for batch workflows on files over 1GB.

Technical Notes

M4V is functionally almost identical to MP4 — it uses the same MPEG-4 Part 12 container structure — but Apple distinguishes M4V primarily to signal iTunes compatibility and optionally to carry FairPlay DRM. Without DRM, most players treat .m4v and .mp4 interchangeably. The critical codec constraint is that M4V only accepts H.264 or H.265 video with AAC or MP3 audio; any MKV sourced with VP9, AV1, Opus, Vorbis, or FLAC content must be fully transcoded. This tool uses H.264 (libx264) as the output video codec rather than H.265, because H.264 has broader Apple device compatibility — particularly with older iOS hardware and Apple TV generations. Multiple audio tracks present in the MKV are not automatically mapped; the default FFmpeg behavior selects the best single audio stream. Chapter metadata embedded in the MKV is generally preserved during this conversion since both containers support chapter structures via the MP4 chapter atom format. The output file size relative to the MKV source will vary considerably depending on the original codec: a VP9-encoded MKV re-encoded to H.264 at CRF 23 may produce a larger file if the VP9 source was highly efficient.

Related Tools