QuickTime will not open it. the video is fine.

updated · by

mkv and webm are containers — boxes holding a video track and an audio track — and macOS reads neither box. what is inside is very often h.264, which your Mac plays all day. so the file is not the problem and the codec is not the problem: the wrapper is, and swapping a wrapper does not require re-encoding anything.

why macOS will not open an mkv

is mkv a codec or a container?

a container. Matroska describes how tracks are laid out in the file — video here, audio there, subtitles alongside, chapters after. it says nothing about how the picture is compressed; that is the codec's job, and inside an mkv it is usually h.264 or h.265, exactly what an mp4 carries.

the demonstration is easy to reproduce. take a working mp4, copy its tracks into an mkv without touching them, and hand both to macOS. here the mp4 loaded with two tracks; the mkv came back with zero and error −11828, «cannot open — this media format is not supported». identical picture, identical sound, one opens and one does not.

the same container-versus-codec point shows up on a file macOS does read, where it produces the opposite surprise — a rename that looks like it worked: convert mov to mp4

macOS publishes the list of containers it will read, and Matroska is not on it: AVURLAsset.audiovisualTypes()

what the format actually describes, if you want the structure rather than the marketing: Matroska technical specification

webm is a Matroska too, and it gets its name from Chrome

webm is a restricted subset of Matroska: the same structure, with the codecs narrowed to VP8, VP9 or AV1 for picture and Vorbis or Opus for sound. macOS does not read it either — the same test file failed with the same error.

there is a small oddity worth knowing. an mkv on your Mac has no file type at all: the system falls back to a generated identifier, which is why the Finder can tell you so little about it. a webm does have one — and on this machine that type was declared by Chromium rather than by Apple, and is marked as imported and untrusted. install Chrome and the format acquires a name; on a Mac without it, webm is as anonymous as mkv.

the subset and its codecs, from the project itself: the WebM container

the codecs inside webm are the royalty-free answer to a licensing problem, and that story explains a lot about which formats your Mac reads: why your photos are heic

how to play an mkv on a Mac for free

if you only want to watch it, install VLC or IINA and stop reading. both are free, both open mkv and webm without a thought, and neither converts anything. for «a colleague sent me a recording», that is the entire job and hop has nothing to add to it.

the two worth having: VLC for macOS

and the one built for Apple hardware, if you prefer the native feel: IINA

worth saying plainly, because most of what ranks for this wants to sell you a converter for a file you were going to watch once.

convert mkv to mp4 without re-encoding

you need a real conversion when something else has to accept the file — an editor, a phone, a platform, an app that only speaks mp4. and this is where two completely different operations wear the same name.

repack, remux, rewrap — the same operation

  • remuxing — the tracks are copied out of one container and into the other, untouched. nothing is decoded, nothing is encoded, no quality is lost, and it takes seconds regardless of how long the video is.
  • transcoding — the video is decoded and encoded again. minutes to hours, a hot Mac, and always some quality gone.

an mkv holding h.264 needs only the first. every converter in the search results will happily do the second, because that is what a converter does — and a two-hour recording becomes a two-hour job that also looks slightly worse at the end of it.

the distinction has a precise name in the tool most of this is built on — stream copy: ffmpeg: stream copy

why macOS cannot remux it either

this is the part that surprises people who know their Mac. macOS does have a lossless remuxer built in: avconvert, with the PresetPassthrough preset, copies tracks between containers without re-encoding and does it in seconds. it is genuinely good, and it is already on your disk.

it just cannot open a Matroska. asked to read the test mkv it answered «unable to read», and the same for the webm, while the mp4 went through with error 0. the tool exists; Apple never taught the layer underneath it to parse this container.

so the gap here is not «macOS is bad at video». it is narrow and specific: the system can do this exact operation, for every container except the two you have.

for a .mov that same command is the right answer, and there it works perfectly: convert mov to mp4

which leaves the free third-party routes, and they are not equal. ffmpeg does a perfect remux with one flag and asks you to install it and know the flag. HandBrake is excellent and only transcodes — it has no plain repack, so it will spend an hour making a slightly worse copy of a file that needed a rewrap.

how hop converts mkv to mp4

the free routes above all work. what they ask for is that you already know which one you need — play it or convert it, remux or transcode, this flag or that preset — and that you be willing to install a toolkit and use a Terminal to get the fast, lossless version of the answer.

hop asks you to drop the file in. it repacks mkv and webm into mp4 with the picture copied across untouched, shows the size before it runs, and does the folder as easily as the file.

what you havethe free routewith hop
one file, you just want to watch itVLC or IINA — free, better at playbacknot needed, use the player
one mkv, something else needs an mp4install ffmpeg, learn -c copydrop it in, seconds, nothing lost
a folder of recordingsa shell loop over ffmpegone drop, all of them
you were about to use HandBrakean hour of transcoding, slightly worsea remux, seconds, identical picture
it also has to be smaller or reframeda second pass with different flagssame window, size shown first

the first two rows are the honest shape of this. for watching, a player beats us and always will. for one file and a comfortable Terminal, ffmpeg is free and does exactly the same thing. what hop removes is the part where you have to know which of those two situations you are in before you can start.

the helper that handles these containers downloads once, verified by signature, and is not needed for anything else.

the module in full — images, audio and documents go through the same window: file converter on the features page

when a remux is not enough

no sound after converting

the most common disappointment, and it is the audio codec rather than the container. an mkv often carries Vorbis or Opus, and an mp4 will not hold either — so the sound has to be re-encoded to aac even when the picture is copied. a remux that silently dropped it is worse than one that tells you.

  • the video inside is VP9 or AV1 — common in webm from the web. mp4 will not carry those, so this one genuinely has to be re-encoded, and it will take real time.
  • there are subtitles you need. Matroska carries subtitle tracks that an mp4 handles differently or not at all — check the result before deleting the original.
  • there are several audio tracks or several languages. containers differ in what they keep; expect to lose the ones you did not select.
  • it is a partial download. an incomplete mkv often plays anyway, which makes it easy to mistake a truncated file for a broken converter.
  • the file is enormous and the disk is not. a remux writes a second copy of the whole thing before you can delete the first.

large recordings are also the quietest way a Mac fills up, and rarely the first place people look: what «system data» is actually using

and if the clip is going to a platform, the frame matters more than the container: compress video for reels, TikTok and shorts

frequently asked questions

why can't QuickTime play mkv?
macOS has no support for the Matroska container — it is not in the list of types AVFoundation will read. the video inside is usually h.264, which QuickTime plays happily; it simply cannot open the box it arrived in.
is there a QuickTime mkv plugin?
no, not any more. the old plugin architecture that made this possible was retired with QuickTime 7, and modern QuickTime Player does not accept components. installing a player that reads mkv natively is the working answer.
how do i remux mkv to mp4 without losing quality?
copy the tracks instead of re-encoding them. ffmpeg does it with -c copy; hop does it by dropping the file in. either way nothing is decoded, so the picture is bit-for-bit what it was.
can macOS convert mkv itself?
no. it ships a lossless remuxer — avconvert with PresetPassthrough — but that tool cannot read Matroska: it answers «unable to read» for mkv and webm while handling mov and mp4 fine.
how long should converting an mkv take?
a remux is seconds, even for a two-hour file. if your converter is showing an hour, it is transcoding — either because something inside genuinely has to be, or because it does not know how to do anything else.
what is the difference between mkv and mp4?
the container. Matroska is more permissive — more codecs, more tracks, better subtitle support; mp4 is the one every device accepts. the video inside is frequently identical.
should i just use VLC?
if you only want to watch it, yes, and it costs nothing. convert when something else must accept the file.

the tool behind this

file converterimages, video, audio and documents. offline, with the size shown up front.

done with convert and compress

other things people do

about the author

Anton Shakirov, the author of hop

makes hop

makes hop and every page on this site. eighteen tools under a single menu bar icon, MIT licensed and open source. reads and answers issues and email himself.

download hopfree · macOS 14+ · Apple silicon and Intel