Initializing... drag & drop files here
Supports: MOV
Both are containers: envelopes that hold a video track, an audio track and some metadata. Neither one compresses better than the other, so the choice is entirely about what the envelope can carry and what will open it. The short version — convert your .mov to .mkv if the file is heading for a Plex, Jellyfin or Kodi library, a media box, or an archive where you later want several audio languages and soft subtitles in one file. Stay on MOV (or move to MP4) if it is heading for Final Cut, a browser, an iPhone, or anyone using the Apple ecosystem.
| Property | MOV (QuickTime) | MKV (Matroska) |
|---|---|---|
| Origin | Apple, 1991; ISO later based MP4 on its structure | Matroska project, started 2002 |
| Standard status | Apple's QuickTime File Format specification | IETF standard — RFC 9559, published 2024, built on EBML (RFC 8794) |
| Licensing | Apple-controlled specification | Open and royalty-free |
| Internal structure | Atoms / boxes | EBML elements: Segment, Tracks, Clusters, Cues, Chapters, Attachments |
| Audio tracks | Multiple supported | Multiple supported, no practical limit |
| Soft subtitles | QuickTime text and tx3g | Native for SRT, ASS/SSA, VobSub and PGS bitmap subs |
| Attachments | Not a general-purpose feature | Can embed fonts, cover art and arbitrary files |
| Chapters | Supported | Supported, including alternative editions |
| Native browser playback | Safari plays MOV; other browsers depend on the codec inside | None — WebM is the Matroska-derived subset browsers actually support |
| Native desktop playback | macOS and Windows via QuickTime-era support | Built into Windows since Windows 10; on macOS you need VLC, IINA or similar |
| Editing software | Final Cut, Premiere, DaVinci Resolve, iMovie | Premiere and Resolve are limited or unsupported; Final Cut will not import it |
| Media servers | Works, but usually transcoded | The de facto native format for Plex, Jellyfin, Kodi and Emby |
| Best for | Apple workflows, camera originals, handing a file to a client | Home libraries, multi-language archives, anything with subtitles |
.mkv; MOV to MP4 is the correct conversion for that..mov onto the page or click "+ Add Files". Several clips can be queued and converted in one batch with the same settings..mkv. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours — no sign-up, no watermark.| Choice | What it gives you | Pick it when |
|---|---|---|
| H.264 video (opens selected) | Widest hardware decode support; real 0–51 CRF control | Default answer — anything that must play on older TVs, boxes or phones |
| H.265 video | Roughly the same quality at a materially smaller size | Storage matters and every client in your house decodes HEVC |
| AV1 video | The best compression on offer, at a much slower encode | Long-term archive where encode time is irrelevant |
| AAC audio (opens selected) | Universally decodable, small | Default answer, especially if a media server may transcode anyway |
| FLAC audio | Bit-exact audio at roughly half the size of PCM | Archiving a master you may re-encode from later |
| AC3 / EAC3 / DTS audio | Formats an AV receiver accepts over passthrough | Surround audio going to a receiver rather than to TV speakers |
| Opus / Vorbis audio | Best quality per bit at low bitrates | Space-constrained libraries played on software clients |
It is a full re-encode, not a rewrap. Even when the MOV already holds H.264 and AAC and you leave both dropdowns alone, the video is decoded and encoded again rather than copied through, so there is a generation of quality loss — small at the Highest and Very High presets, obvious at the bottom of the ladder. If your goal is purely to change the wrapper with the streams untouched, a local muxer such as MKVToolNix does a true stream copy in seconds; a server-side converter cannot, because the whole pipeline is built around re-encoding.
The output carries one video track and one audio track. MKV's headline features — several audio languages, a stack of subtitle tracks, embedded fonts, chapter editions — are things you add afterwards in a muxer, not things a format conversion can invent from a single-track source. Two source behaviours also pass straight through: interlaced camcorder footage is not deinterlaced, and HDR footage from a recent iPhone gets a plain colour conversion with no tone-mapping, so Dolby Vision and HLG clips typically come out flat or washed out unless you export an SDR version first.
Yes, a little — this is a re-encode, not a container swap. The video is decoded and encoded again even when the codec stays the same, which is one generation of lossy compression. Set Quality Preset to Highest, or use Constant Quality with a CRF around 18, and the loss is very hard to see. If you need a genuinely lossless container change, do it locally with a muxer that stream-copies rather than through any online converter.
Just different, and the difference is entirely about the envelope. Neither container compresses anything — an H.264 stream is exactly the same stream in either one. MKV can carry more track types and more metadata and is openly specified; MOV is the format Apple's tools speak natively. Pick the one your destination software actually reads.
Yes, and considerably more. Matroska is codec-agnostic: H.264, H.265, AV1, VP9, MPEG-2 and MPEG-4 all sit in it happily, as do AAC, AC-3, E-AC-3, DTS, FLAC, Opus, Vorbis and uncompressed PCM. This page exposes that whole list. The practical constraint is not the container but the player at the other end — a five-year-old TV that reads MKV may still refuse an AV1 stream inside it.
Because no mainstream browser decodes Matroska, and Apple's ecosystem has never shipped MKV support — QuickTime Player, Photos and Final Cut all refuse it. WebM, which browsers do support, is a deliberately restricted subset of Matroska with a much narrower codec list, so it is not a workaround for an arbitrary MKV. If the destination is a browser or an iPhone, convert to MP4 instead.
Do not count on it. This conversion produces a video track and an audio track from a single source file; it is not a muxing tool, so treat any subtitle or chapter data in the MOV as something to re-attach afterwards. The usual workflow is to convert here, then use MKVToolNix locally to add .srt files, alternate audio and chapter markers — all operations MKV was designed for and all of which are stream copies, so they cost nothing in quality.
Leave it on AAC if the server or client may transcode anyway — it is the most universally decodable choice. Choose FLAC when you are archiving and want bit-exact audio at roughly half the size of PCM. Choose AC3 or EAC3 when the file will be sent to an AV receiver over passthrough. Opus is the most efficient option at low bitrates but has patchier support on older hardware players than its reputation on the web suggests.
Because the bitrate the encoder targets comes from your compression settings, not from the source file's size. On the default Very High preset with H.264, output size tracks your source's complexity and resolution and often lands close to the original. Switching the codec to H.265 typically cuts size substantially at matched quality; using Specific file size lets you name the number outright. Container overhead itself is negligible in both formats.
Yes — set Trim to Time Range and give a start time and duration, in seconds or as HH:MM:SS.sss, and only that section is encoded. That is faster and cleaner than converting the whole file and cutting afterwards. If you would rather cut first and decide on the container later, Video Cutter does that on the source.
It is uploaded over an encrypted connection, converted on our servers, and deleted automatically after a few hours. Nothing is shared, published or made searchable, there is no sign-up, and no watermark is added to the output.