What Is an MKV File? Matroska Video Explained
MKV Is a Container, Not a Codec
The single biggest misconception about MKV files is that people treat them as a video format the way they treat MP4 or AVI. MKV — short for Matroska Video — is actually a container format. Think of it as a ZIP archive that holds video streams, audio tracks, subtitles, chapter markers, and metadata all in one file. The video inside that container might be encoded with H.264, H.265 (HEVC), AV1, VP9, or even an older codec like MPEG-2. The audio might be AAC, AC-3 (Dolby Digital), DTS, FLAC, or TrueHD. MKV itself is agnostic about all of that. The Matroska project was launched in 2002 as an open-standard alternative to proprietary containers like AVI (Microsoft) and MOV (Apple). The name comes from the Russian word for nesting dolls — matryoshka — which is a fitting metaphor for a format that wraps multiple streams inside a single file. The specification is maintained by the Matroska.org community and is completely royalty-free. This distinction between container and codec matters practically. If you download a 4K Blu-ray rip in MKV format and it won't play on your smart TV, the problem is almost never MKV itself — most modern devices handle the container fine. The obstacle is usually the video codec (often H.265 or AV1) or the audio codec (often DTS-HD or TrueHD) that the TV's hardware decoder doesn't support. Understanding this saves you from re-encoding an entire file when you only need to convert the audio track.
What MKV Can Hold That MP4 Cannot
MP4 is the more universally compatible container, but MKV has real technical advantages that explain why it dominates in home-theater and archival circles. Multiple audio tracks are the most practical one. An MKV file can carry a full English 7.1 DTS-HD Master Audio track, a Spanish 5.1 Dolby Digital track, and a stereo AAC commentary track simultaneously. When you play the file in VLC or Kodi, you switch between them from the Audio menu without re-encoding anything. MP4 technically supports multiple audio tracks too, but many MP4-based workflows and devices silently ignore all but the first track. Software subtitles are another area where MKV shines. The format natively supports SubRip (.srt), ASS/SSA (Advanced SubStation Alpha, the format used for styled anime fansubs), HDMV PGS (the bitmap subtitle format used on Blu-rays), and VobSub. You can embed ten different subtitle languages and toggle them in your player. MP4's subtitle support is limited to a handful of text formats; it handles PGS poorly and ASS styling inconsistently. Chapter markers in MKV are stored as plain XML-like text inside the container, making them easy to edit with tools like MKVToolNix without touching the video or audio streams. Attachment support lets you embed fonts directly into the file — critical for ASS subtitles that rely on specific typefaces to render correctly. Finally, MKV has better resilience to file corruption. Its segment-based structure means a partially downloaded MKV file is often still playable up to the point of corruption, whereas a corrupted MP4 index (the moov atom) can make the entire file unreadable.
How MKV Files Are Typically Created
Most MKV files you encounter in the wild were not encoded from scratch into MKV. They were muxed — meaning streams from other sources were remultiplexed into the container without re-encoding. This is an important distinction because muxing is nearly instantaneous and lossless, while re-encoding takes significant CPU or GPU time and always involves some quality trade-off. The dominant tool for muxing MKV files is MKVToolNix, a free, open-source application available for Windows, macOS, and Linux. In MKVToolNix GUI, you drag in your source files (a raw H.265 video stream, a DTS audio file, an .srt subtitle), set the track order and default flags, and click Start Multiplexing. The output MKV is ready in seconds regardless of file size because no transcoding happens. HandBrake, the popular open-source transcoder, outputs MKV natively alongside MP4. When you encode a video in HandBrake and select Matroska as the container under the Summary tab, you get access to features like chapter markers and multiple audio tracks that HandBrake's MP4 output doesn't fully support — for instance, HandBrake can pass through DTS audio into MKV but must convert it to AAC or AC-3 for MP4. FFmpeg, the command-line powerhouse, handles MKV creation with a straightforward flag: ffmpeg -i input.mp4 -c copy output.mkv remuxes an MP4 to MKV in seconds by copying all streams unchanged. Adding -c:v libx265 -crf 22 -c:a copy would re-encode the video to H.265 while keeping the original audio, a common workflow for compressing large files while preserving audio quality. Blu-ray and DVD ripping software like MakeMKV (the name is not a coincidence) outputs directly to MKV, preserving all the original tracks, chapters, and metadata from the disc in a single file.
Playback: Where MKV Works and Where It Doesn't
MKV playback support has improved dramatically over the past decade, but compatibility gaps still exist and it's worth being specific about them. On desktop computers, VLC Media Player handles MKV reliably on Windows, macOS, and Linux — including complex files with ASS subtitles and multiple tracks. Windows 11's built-in Movies & TV app added native MKV support in 2017 via a codec update, though it struggles with some audio formats like DTS-HD. macOS's QuickTime Player does not natively support MKV; you need IINA, VLC, or Infuse. On streaming devices, the picture is mixed. Kodi, Plex, and Jellyfin all handle MKV well when run on capable hardware, doing software decoding as a fallback when hardware decoding fails. The Nvidia Shield Pro handles nearly any MKV codec combination through hardware. Roku devices support MKV containers but only with H.264 video and specific audio codecs — DTS and TrueHD will fail. Apple TV 4K via the Infuse app handles MKV broadly; via the native TV app, support is limited. Smart TVs are the most inconsistent. Samsung Tizen TVs (2018 and later) play MKV with H.264 and H.265 video and AC-3/AAC audio, but reject DTS. LG webOS TVs have similar restrictions. If your TV shows a 'format not supported' error on an MKV file, the issue is almost certainly the audio codec rather than the container. Game consoles are largely a dead end for MKV. PlayStation 5 and Xbox Series X both support MP4 and some MKV files through their media players, but codec support is narrow and subtitle rendering is minimal. For reliable playback on consoles, converting to MP4 with H.264 video and AAC audio is the pragmatic choice.
Converting MKV Files: What CocoConvert Can and Cannot Do
CocoConvert handles the most common MKV conversion scenarios: converting MKV to MP4, WebM, MOV, or AVI; extracting audio to MP3, AAC, or FLAC; and converting video files from other formats into MKV. For the majority of users who need to make an MKV file playable on a device that doesn't support it, these conversions cover the use case. When you upload an MKV to CocoConvert and select MP4 as the output, the service re-encodes the video to H.264 and the audio to AAC — the most broadly compatible combination for phones, tablets, smart TVs, and social media platforms. The process takes a few minutes depending on file size and server load. Files up to 2 GB can be converted without an account; larger files require a registered account. However, there are real limitations worth knowing upfront. CocoConvert does not currently support extracting or preserving multiple audio tracks — the output will contain only the default audio track from the source MKV. Embedded subtitle streams are not carried over to the output file; if you need subtitles, you would need to use a desktop tool like HandBrake to burn them into the video or MKVToolNix to extract them as a separate .srt file before uploading. Lossless remuxing (changing the container without re-encoding) is not available through the web interface — every conversion involves transcoding. For complex MKV workflows — remuxing without quality loss, managing multiple audio tracks, handling PGS bitmap subtitles, or working with files larger than 10 GB — desktop tools like MKVToolNix, HandBrake, or FFmpeg are the appropriate choice. CocoConvert is best suited for quick, single-track conversions where convenience matters more than preserving every stream in the original file.
MKV vs. MP4: Choosing the Right Container
The choice between MKV and MP4 comes down to what you're doing with the file, not which format is objectively better. Choose MKV when you're archiving media and want to preserve everything: multiple language tracks, lossless audio like FLAC or TrueHD, bitmap subtitles from a Blu-ray source, and chapter markers. Home theater setups running Plex, Jellyfin, or Kodi on a capable server or device handle MKV without issues, and the flexibility to switch audio tracks and subtitles on the fly is genuinely useful. MKV is also the right choice if you're storing files long-term and value the open, royalty-free specification — there's no corporate owner who can change licensing terms. Choose MP4 when compatibility is the priority. If you're sending a video to someone who will play it on an iPhone, uploading to YouTube, sharing via WhatsApp, or playing it on a TV that doesn't have a media server, MP4 with H.264 video and AAC audio will work. Nearly every device manufactured since 2010 plays this combination without any additional software. The file size difference between MKV and MP4 containing identical streams is negligible — typically under 1% — so storage efficiency is not a meaningful factor in the decision. Both containers support H.265 and AV1, so codec choice drives file size far more than container choice. One practical note: if you have an MKV file where the video is already H.264 and the audio is already AAC, you can remux it to MP4 using FFmpeg (ffmpeg -i input.mkv -c copy output.mp4) in seconds with zero quality loss. This is the fastest path to compatibility when the codecs are already right but the container is causing problems.
The Future of MKV and the WebM Connection
MKV's influence extends beyond the .mkv file extension. WebM, the open video format used on YouTube and across the web, is a direct subset of the Matroska specification. WebM restricts the container to VP8/VP9/AV1 video and Vorbis/Opus audio, and it uses the same underlying binary format (EBML — Extensible Binary Meta Language) as MKV. In practice, many WebM files can be renamed to .mkv and will open in Matroska-compatible players, though the reverse isn't true since MKV allows codecs that WebM doesn't. The broader Matroska ecosystem also includes MKA (Matroska Audio, for audio-only files) and MKS (Matroska Subtitles), though these are rarely encountered outside of specialized workflows. AV1, the royalty-free codec developed by the Alliance for Open Media, is increasingly stored in MKV containers for local playback. AV1 offers roughly 30% better compression than H.265 at equivalent quality, and hardware decoding support is now present in Intel 11th-generation and newer CPUs, AMD RDNA 2 and newer GPUs, Apple M3 chips, and most 2023-and-later Android flagship phones. As AV1 hardware support becomes ubiquitous, MKV is well-positioned as its primary container for local files — the same way it became the default container for H.265 content years before H.265 hardware decoding was widespread. MKV is not going away. It has been the dominant container for high-quality local video for over 15 years, the specification is actively maintained, and its open nature means no single company can deprecate it. For anyone serious about managing a local video library, understanding what MKV contains — and why — is foundational knowledge.