Convert MKV to MOV — Free Online Tool

Convert MKV files to MOV format using H.264 video and AAC audio — the codec combination natively supported by Apple's QuickTime and Final Cut Pro. This tool runs entirely in your browser via WebAssembly, so your files never leave your device.

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 and MOV are both container formats, but they serve very different ecosystems. During this conversion, the H.264 video stream is re-encoded using libx264 with a CRF of 23, and the audio is transcoded to AAC at 128k bitrate — both of which MOV handles natively. Unlike a simple remux, this is a full transcode, meaning FFmpeg decodes and re-encodes the video rather than just copying the bitstream. This is necessary because MKV files frequently carry video encoded with codecs like VP9 or HEVC, or audio in formats like Opus or Vorbis that QuickTime does not reliably support. The output also includes the `-movflags +faststart` flag, which relocates the MOV metadata atom to the beginning of the file — a critical step for web-based playback and smooth scrubbing in editing applications.

What Each Flag Does

Flag What it does
ffmpeg Invokes the FFmpeg binary — the open-source multimedia processing engine that powers this conversion both in the browser (via FFmpeg.wasm) and on the desktop command line.
-i input.mkv Specifies the input file — in this case an MKV container, which may contain any combination of video, audio, subtitle, and chapter streams that FFmpeg will analyze before processing.
-c:v libx264 Re-encodes the video stream using the libx264 H.264 encoder, producing a video track that QuickTime Player, Final Cut Pro, and virtually all Apple software can decode natively without additional codecs.
-c:a aac Transcodes the audio stream to AAC using FFmpeg's built-in AAC encoder, replacing any audio codec present in the source MKV — including Opus, Vorbis, or MP3 — with the audio format QuickTime expects by default.
-crf 23 Sets the Constant Rate Factor for H.264 encoding to 23, which is the libx264 default and represents a high-quality, visually transparent encode for most video content — balancing file size against output quality.
-b:a 128k Targets a 128 kilobits-per-second bitrate for the AAC audio track, which is the standard quality level for stereo audio and produces clean sound for speech, music, and mixed content in the MOV output.
-movflags +faststart Moves the MOV container's moov metadata atom to the start of the file after encoding completes, enabling progressive playback in QuickTime, web browsers, and editing applications without requiring the full file to be loaded first.
output.mov Defines the output filename and, by its .mov extension, instructs FFmpeg to wrap the encoded H.264 video and AAC audio streams in a QuickTime MOV container rather than any other format.

Common Use Cases

  • Importing footage recorded with open-source tools like OBS or Handbrake (which default to MKV output) into Final Cut Pro or Adobe Premiere Pro on macOS, where MOV is the preferred native container.
  • Preparing video files for upload to Apple-centric platforms or workflows where QuickTime compatibility is assumed and MKV files are rejected or unsupported.
  • Converting MKV files downloaded from media archives or streaming sources so they can be played back natively in QuickTime Player without installing third-party codec packs.
  • Wrapping H.264 content in a MOV container to meet delivery specifications required by post-production houses or broadcast facilities using Apple-based editing suites.
  • Re-packaging MKV recordings from screen capture software into MOV format to use them as source clips in iMovie or other consumer-level Apple video editors.
  • Converting an MKV with Vorbis or Opus audio tracks — codecs that QuickTime cannot decode — into a MOV file with standard AAC audio for reliable playback across all Apple devices.

Frequently Asked Questions

Yes, because this conversion performs a full re-encode of both the video and audio streams rather than simply remuxing them. The video is re-encoded with H.264 at CRF 23, which is a high-quality lossy setting — visually close to lossless for most content, but not bit-for-bit identical to the source. If your MKV already contains H.264 video and AAC audio, you could theoretically stream-copy to avoid quality loss, but doing so risks compatibility issues with the MOV container if the source bitstream has non-standard parameters. For archival use, consider using CRF 18 or lower.
Both MOV and MKV support subtitles and chapter markers, but the specific subtitle formats used in MKV files (such as ASS, SSA, or PGS image-based subtitles) are often incompatible with MOV's subtitle tracks. The default FFmpeg command shown here does not explicitly map subtitle streams, so they will not be carried over automatically. Chapter metadata may transfer depending on the source MKV's chapter format. If subtitle preservation is critical, you should add `-c:s mov_text` and `-map 0:s` to the command — though only text-based subtitles will convert successfully.
The `-movflags +faststart` flag instructs FFmpeg to move the moov atom — the block of metadata that describes the file's structure — to the beginning of the MOV file instead of leaving it at the end. Without this, a player or browser must download the entire file before it can begin playback, since it needs the moov atom to decode the content. With faststart, playback and scrubbing can begin almost immediately, which is essential for web delivery and for smooth performance in editing applications like Final Cut Pro.
The default FFmpeg command maps the first audio stream only. MKV files commonly carry multiple audio tracks (e.g., different languages or commentary), but MOV also supports multiple audio tracks. If you need to preserve all audio tracks, modify the command by adding `-map 0:v -map 0:a` before the output filename, which tells FFmpeg to include all video and audio streams from the source MKV. Each audio track will be transcoded to AAC independently.
Adjust the `-crf` value to control quality. CRF operates on an inverse scale: lower numbers mean higher quality and larger file sizes, while higher numbers mean lower quality and smaller files. The default is CRF 23, which is a good general-purpose balance. For high-quality output suitable for professional editing, use CRF 18. For smaller files where some quality loss is acceptable — such as preview or proxy files — use CRF 28 or higher. The valid range for H.264 is 0 (lossless) to 51 (worst quality).
Yes. On macOS or Linux, you can wrap the command in a shell loop to process an entire folder: `for f in *.mkv; do ffmpeg -i "$f" -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart "${f%.mkv}.mov"; done`. On Windows using PowerShell, use: `Get-ChildItem *.mkv | ForEach-Object { ffmpeg -i $_.Name -c:v libx264 -c:a aac -crf 23 -b:a 128k -movflags +faststart ($_.BaseName + '.mov') }`. This is particularly useful for files over 1GB, which exceed the browser tool's limit.

Technical Notes

MKV's strength is its flexibility as a universal container — it can hold virtually any codec combination, which makes it popular for archiving and media distribution but problematic when handing off files to Apple-centric workflows that expect QuickTime-compatible containers. MOV, by contrast, is tightly coupled to Apple's codec ecosystem and historically expects H.264, HEVC, ProRes, or MJPEG for video and AAC, ALAC, or PCM for audio. This conversion standardizes on H.264 + AAC, which is the broadest compatibility target across both Apple and non-Apple platforms. One important limitation: MOV does not support VP9 or AV1 video streams or Opus audio in any meaningful way — if your source MKV uses these codecs (common for web-sourced content), a full re-encode is unavoidable. Transparency is technically supported in MOV via codecs like PNG or Apple ProRes 4444, but the default H.264 path does not preserve an alpha channel; if your source MKV contains a transparency layer encoded with PNG video, you would need to change the video codec to `png` in the command. File sizes after conversion will typically be similar to or slightly smaller than the source MKV at CRF 23, though this depends heavily on the source codec — VP9-encoded MKVs may produce larger MOV outputs at equivalent perceptual quality.

Related Tools