Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Converting MKV to M4A pulls the sound out of a Matroska file and keeps all of it. M4A is one of three audio targets here that do that — Ogg and Opus keep every track too, since all three containers have room for as many soundtracks as the MKV had — so a commentary, an audio description or a second language survives instead of being silently dropped in favour of the first track.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
MKV to M4A
People who convert an MKV for its audio are frequently not after the main mix. They want the director’s commentary, the audio description track that narrates what is on screen, the original language under a dub, or the interpreter channel from a recorded conference. Matroska is where all of that lives, because it is the container that stops nobody from adding a fourth soundtrack.
Every other audio conversion here answers that request by taking the first track and throwing the others away without saying so. That is the right behaviour for a format with room for one, and it is exactly wrong for this reader — which is why this page exists as something other than a second version of the MP3 page.
An M4A is not a codec, it is a container: AAC audio inside the same MPEG-4 box that an MP4 uses, with the extension changed so that software knows to expect sound and no picture. That box was designed for films, so it counts audio tracks in the millions rather than stopping at one. Ogg and Opus are built the same way and share that headroom, which is why all three sit on the "keeps everything" side of this page.
MP3, raw AAC, WAV and FLAC are all built the other way. Each of them is a single stream of audio with a header on the front, and there is nowhere in the specification to put a second one. It is not a limitation of this converter; it is what those formats are. When the requirement is "keep them all", the container has to come from the video world, and M4A is the smallest, most widely supported thing in that world that is still an audio file.
Every audio track the browser can decode is written into the M4A, in the order the MKV declared them. Nothing is reordered and nothing is promoted — including Matroska’s own "default track" flag, which is not consulted. A rip with an English mix, a commentary and a Spanish dub produces a three-track M4A in that same sequence.
A player with an audio menu is what turns that into something usable. VLC lists them under Audio › Audio Track on every platform it runs on, and mpv and Infuse do the same. Apple’s Music app is the awkward one, because its model is one stream per file and it will generally hand you the first — so the practical arrangement is an M4A as the file you keep and a capable player as the thing you open it with.
Even when the MKV already holds AAC, the audio is decoded back to samples and compressed again. There is no packet-copy path in this converter, so AAC to AAC costs a second generation of lossy compression rather than nothing. It is audible on music at the small-file band and effectively inaudible on speech at the balanced one.
For a commentary or a description track — speech, usually mono, recorded in a booth — the loss is not worth thinking about. For a concert mix it is, and the high band is the lever. If nothing at all should change, a desktop remuxer will lift the same AAC stream out of the Matroska container and into an MPEG-4 one in seconds without decoding a frame, and that is the correct tool for an archive copy.
A track is dropped before conversion if the browser cannot decode it, and the list of codecs that fall into that hole is short and predictable: AC-3, E-AC-3, DTS and Dolby TrueHD. Those are the soundtracks discs carry, and browsers do not ship decoders for them — DTS and TrueHD are not even recognised as codecs by the reader.
This lands hardest on precisely the files this page is for. A commentary track on a Blu-ray rip is very often AC-3 while the main feature is DTS-HD, so a file can come back with one track where you expected three, or refuse entirely because none of them could be read. If that happens, converting the audio to AAC once with a desktop tool and returning here is the shortest way through.
The band applies to all of them, so it has to suit the most demanding one. Small, balanced and high are offered, defaulting to balanced, and the band is resolved per codec rather than being a bitrate you have to guess at.
Balanced is right for a file that is mostly speech tracks. Go to high when one of the tracks is a music mix, because the setting is not per track and a band chosen for a commentary will be applied to the score as well. The size cost is real but modest against the video file the audio came out of — an hour of AAC at the high band is still a small fraction of a gigabyte.
Title, artist, album, date, description and comment are read out of the Matroska tags and written into the M4A, which is what the Music app, Podcasts and a file inspector read to show something other than a filename. Cover art carried in the source comes across the same way.
Chapter marks do not. Matroska chapters are one of the format’s selling points and this conversion does not read them, so an audiobook or a lecture series that was navigable inside the MKV becomes one long track in the M4A. Where that matters — and for a five-hour recording it matters a great deal — the chapters have to be rebuilt afterwards in a tool that writes them, or the file has to be split.
Inside the browser tab, on your own processor, with the decoders the machine already has. Nothing carrying the file is sent to a server, and the network tab will show you that in ten seconds if you want to check rather than take it on trust.
The free tier accepts an MKV up to 100 MB. That is generous for a recorded talk and restrictive for a film, which is the awkward shape of this pair: the files with the most interesting alternate tracks are usually the largest ones. For those, extracting the tracks with MKVToolNix on the desktop costs nothing in quality and no time at all, and this page is the browser-sized version of the same job.
| MKV | M4A | |
|---|---|---|
| Full name | Matroska Video | MPEG-4 Audio |
| File extension | .mkv | .m4a |
| Media type | video/x-matroska | audio/mp4 |
| Compression | Lossy — file size is bought with quality | Lossy — file size is bought with quality |
| First published | 2002 | 2004 |
| Published by | — | Apple |
| Specification | Matroska | — |
| Licensing | Open standard | Published, not standardised |
| Standing today | Current | Current |
| Audio channels | — | up to 48 |
| Opens in a browser | Some browsers | Every browser |
| Considered instead | MP4, WebM | MP3, FLAC |
M4A opens in every current browser. MKV has narrower browser support than that. If the file is going onto a web page or into a form, that is usually the whole reason for the conversion.
M4A is a container rather than a single format. What actually plays is the codec inside it — usually AAC and ALAC — which is why two files with the same extension can behave differently on the same device.
VLC reads both MKV and M4A, so there is a way to check the result against the original without a second tool.
MKV was published in 2002. The specification is Matroska, and it is worth reading if the file has to outlive the tool that wrote it.
M4A comes from Apple and dates from 2004. iTunes, VLC and FFmpeg all read it.
No. This conversion runs entirely inside your browser, so the file never leaves your device. You can confirm it yourself: open the network tab of your browser's developer tools and convert something. You will see the page load, plus the analytics and advertising the site is paid for with — and nothing carrying your file. The engine behind this particular pair is mediabunny, a wrapper around WebCodecs, which borrows your device's own hardware decoders; your browser fetches it once and caches it.
Yes, and it is one of three audio formats here that do — Ogg and Opus keep every track too. An M4A is AAC inside an MPEG-4 container, and that container has no practical limit on audio track count, so all of them are written in the order the MKV held them. Converting the same file to an MP3, an AAC, a WAV or a FLAC keeps exactly one and drops the rest without comment.
In a player that offers an audio menu. VLC lists them under Audio › Audio Track on every platform, and Infuse and mpv do the same. Apple’s Music app is the weak point — it is built around one stream per file and will generally give you the first — so a multi-track M4A is best treated as an archive copy with a player-of-choice on top.
The order the MKV declares them in, unchanged. That is file order rather than Matroska’s "default" flag, so on a disc rip the first track is not reliably the one a player would have started with. Keeping all of them is precisely what removes the need to guess.
Yes. Every track is decoded and encoded again as AAC, which costs a second generation of lossy compression. There is no packet-copy path here, so an AAC track going into an M4A is not lifted across untouched — if that matters, a desktop remuxer will move it without decoding anything.
Every soundtrack in it was in a codec the browser cannot decode, and with the picture discarded there was nothing left to write. That is AC-3, E-AC-3, DTS or Dolby TrueHD — disc audio, which browsers ship no decoder for. It is a common outcome for exactly the sort of file that has commentary tracks, which is the irony of this pair.
The container. Both hold AAC audio; the M4A wraps it in an MPEG-4 box with an index, tags and room for many tracks, while the AAC target writes a bare stream of frames with room for one. If you want to listen, choose M4A. If a piece of software asked for a raw AAC elementary stream, choose AAC.