Why is the audio out of sync after converting?

Common causes: (1) variable framerate source rendered as constant (use -vsync vfr to preserve VFR); (2) different audio sample rates not resampled (add -ar 48000 ); (3) container limitations (MP4 with variable framerate misbehaves — prefer MKV during editing, encode to MP4 only at the end). Always run ffprobe on both source and output to compare timing.

Why is the audio out of sync after converting?

Common causes: (1) variable framerate source rendered as constant (use -vsync vfr to preserve VFR); (2) different audio sample rates not resampled (add -ar 48000 ); (3) container limitations (MP4 with variable framerate misbehaves — prefer MKV during editing, encode to MP4 only at the end). Always run ffprobe on both source and output to compare timing.

Guide

MKV/Matroska Container Format: The Open-Source Multimedia Powerhouse

PC By Pablo Cirre • Updated May 7, 2026

MKV/Matroska Container Format: The Open-Source Multimedia Powerhouse

Matroska (MKV) is an open-standard multimedia container format that has become the preferred choice for high-quality video archival, Blu-ray rips, and complex multi-track media. Unlike MP4, which prioritizes device compatibility, Matroska prioritizes flexibility — it can hold virtually any codec combination, unlimited tracks, full chapter systems, and advanced subtitle formats. Understanding its architecture reveals why it dominates in enthusiast and professional media contexts.

Origins and Specification

Matroska was created in 2002 by Steve Lhomme as an open alternative to proprietary containers like AVI, ASF, and RealMedia. The name comes from the Russian matryoshka (nesting dolls), reflecting its hierarchical element structure. It is maintained by the Matroska organization and licensed under BSD.

The format uses EBML (Extensible Binary Meta Language) — a binary analog to XML designed for streaming and forward compatibility. Each element has a variable-length ID and size, allowing players to skip unknown elements rather than failing. This design means a player from 2010 can still open a Matroska file using features added in 2024 — it simply ignores the unknown elements.

Related formats:

MKV (.mkv): Full Matroska container — video, audio, subtitles, chapters, attachments
MKA (.mka): Matroska audio only
MKS (.mks): Matroska subtitles only
WebM (.webm): Google's restricted subset — VP8/VP9/AV1 video + Vorbis/Opus audio only

EBML Structure

A Matroska file is organized into top-level segments:

EBML Header           — EBML version, DocType ("matroska")
Segment
  ├── SeekHead        — index of element positions (enables fast seeking)
  ├── Info            — duration, title, muxing app, creation date
  ├── Tracks          — codec, language, pixel dimensions per track
  │     ├── TrackEntry (Video, CodecID: V_MPEG4/ISO/AVC)
  │     ├── TrackEntry (Audio, CodecID: A_AAC)
  │     ├── TrackEntry (Subtitle, CodecID: S_TEXT/ASS)
  │     └── TrackEntry (Attachment: font file)
  ├── Chapters        — full hierarchical chapter system
  ├── Cluster(s)      — blocks of compressed media data
  │     └── SimpleBlock / BlockGroup (each frame/sample)
  ├── Cues            — seek table (keyframe positions for fast seeking)
  ├── Attachments     — embedded files (fonts, cover art, etc.)
  └── Tags            — extensive tagging system

Track Flexibility

Matroska supports virtually any codec through its codec ID system:

Track Type	Supported Codecs
Video	H.264, H.265/HEVC, AV1, VP8, VP9, MPEG-2, Theora, Dirac, FFV1, VC-1, RealVideo
Audio	AAC, AC-3, E-AC-3, DTS, DTS-HD, TrueHD, Dolby Atmos, FLAC, MP3, Vorbis, Opus, ALAC, PCM
Subtitles	ASS/SSA, SRT (SubRip), WebVTT, PGS (Blu-ray), DVB subtitles, VobSub (DVD), USF
Attachments	Fonts (TTF, OTF), cover art, ICC profiles, any binary file

This codec freedom makes MKV the natural format for:

Blu-ray remuxes: preserving TrueHD Atmos, DTS-HD MA, and PGS subtitle tracks without conversion
Anime: ASS subtitles with complex typesetting, multiple audio/subtitle language tracks
Archival: lossless audio (FLAC, TrueHD) + lossless video (FFV1) in one file

Chapter System

Matroska's chapter system is far more powerful than MP4's:

<!-- Ordered chapters (chapters from different files) -->
<Chapters>
  <EditionEntry>
    <EditionFlagOrdered>1</EditionFlagOrdered>
    <ChapterAtom>
      <ChapterTimeStart>00:00:00.000</ChapterTimeStart>
      <ChapterTimeEnd>00:02:30.000</ChapterTimeEnd>
      <ChapterDisplay>
        <ChapterString>Opening</ChapterString>
        <ChapterLanguage>eng</ChapterLanguage>
      </ChapterDisplay>
    </ChapterAtom>
    <!-- ... -->
  </EditionEntry>
</Chapters>

Features unique to Matroska chapters:

Ordered chapters: reference segments from other MKV files (used to avoid duplicating anime OPs/EDs)
Multiple editions: alternative chapter structures for director's cuts vs. theatrical versions
Nested chapters: hierarchical chapters within chapters
Chapter tags: per-chapter metadata (rating, description)

Tags and Metadata

Matroska's tag system is vastly richer than MP4's:

# Apply tags with mkvpropedit
mkvpropedit output.mkv \
  --edit info --set "title=My Film" \
  --edit track:1 --set "name=English" \
  --tags global:tags.xml

Tags can target the entire file, individual tracks, individual chapters, or individual editions. They support arbitrary tag names, allowing full cataloging metadata: DIRECTOR, CINEMATOGRAPHER, IMDB_ID, CONTENT_RATING, ORIGINAL_TITLE, and more.

Working with MKV — Essential Tools

mkvtoolnix (GUI + CLI)

The reference implementation for Matroska:

# Remux Blu-ray streams into MKV without re-encoding
mkvmerge -o output.mkv \
  --track-order 0:0,0:1,0:2 \
  video.h265 audio_truehd.thd subtitles.sup

# Extract specific tracks
mkvextract tracks input.mkv 0:video.h265 1:audio.flac 2:subtitles.ass

# Edit track properties without remuxing
mkvpropedit input.mkv --edit track:a1 --set language=jpn

# Get full info
mkvinfo input.mkv

ffmpeg with MKV

# Convert MP4 to MKV with stream copy (instant, no quality loss)
ffmpeg -i input.mp4 -c copy output.mkv

# Add external subtitle file to MKV
ffmpeg -i input.mkv -i subtitles.ass \
  -c copy -c:s copy \
  -metadata:s:s:0 language=eng \
  output_with_subs.mkv

# Extract embedded subtitle
ffmpeg -i input.mkv -map 0:s:0 output.ass

# Encode with lossless FFV1 video + FLAC audio for archival
ffmpeg -i input.mkv \
  -c:v ffv1 -level 3 -threads 8 -slices 24 \
  -c:a flac \
  archive.mkv

Seeking Performance and Cue Points

Matroska's Cues element contains a seek table of keyframe positions, enabling instant random access. Without cues (or when they are at the end of the file), a player must linearly scan the file to find a position. The mkvmerge tool always writes cues; some remuxers may not.

For HTTP streaming, Matroska requires the server to support byte-range requests (HTTP Range: header). Since the seek table (Cues) is typically at the end of the file, seeking in a streaming context requires the player to first fetch the Cues element location from SeekHead, then perform a range request. This is less efficient than fMP4 but works correctly with compliant servers.

MKV vs. MP4 — When to Choose Which

Use Case	Recommended
Web streaming (DASH/HLS)	MP4 (fMP4/CMAF)
Mobile device playback	MP4 (H.264+AAC)
Blu-ray remux (lossless audio/video)	MKV
Anime with styled ASS subtitles	MKV
Multiple language audio tracks	MKV (simpler tooling)
Universal sharing	MP4
Archival (lossless FFV1+FLAC)	MKV
Smart TV / media center (Kodi, Plex)	Both (MKV preferred for full features)

Hardware and Software Support

MKV is not supported natively in most browsers (no <video> tag support) or many mobile devices. However, it plays natively in:

Desktop: VLC, MPC-HC, mpv, Kodi, Plex (all platforms)
Windows: Windows Media Player (Win10 1709+ with codec pack), Files app
macOS: VLC, IINA, Infuse (iTunes wrapper)
Smart TVs: Most LG/Samsung/Sony TVs natively (2015+)
Android: MX Player, VLC, Nova Video Player

For broader device support, transcode MKV to MP4: ffmpeg -i input.mkv -c copy output.mp4 (if codecs are MP4-compatible) or with re-encoding if necessary.

Summary

Matroska/MKV is the uncompromising choice when content quality and track flexibility matter more than device compatibility. Its EBML foundation provides forward compatibility, its codec support is virtually unlimited, and its chapter/tag system far surpasses MP4. For media archival, Blu-ray preservation, enthusiast collections, and professional production workflows, MKV is the correct container. For internet distribution and mobile consumption, MP4 remains the right tool.

Related conversions

Common video conversions that pair well with this guide:

Related conversions

Put what you just learned into practice — convert your files now in seconds, free and without registration.

Convert →

Convert →

Convert →

Convert →

Convert →

Convert →

Frequently Asked Questions

Web browsers do not support MKV natively because the HTML5 video element requires specific container and codec combinations. Browsers support MP4 (H.264/H.265), WebM (VP8/VP9/AV1), and Ogg. MKV's flexible codec support would require browsers to implement decoders for every possible codec. To play MKV in a browser, transcode to MP4 with ffmpeg: ffmpeg -i input.mkv -c copy output.mp4 (if codecs are compatible).

Web browsers do not support MKV natively because the HTML5 video element requires specific container e codec combinations. Browsers support MP4 (H.264/H.265), WebM (VP8/VP9/AV1), e Ogg. MKV's flexible codec support would require browsers to implement decoders para every possible codec. To reproduzir MKV in um navegador, transcode to MP4 com ffmpeg: ffmpeg -i input.mkv -c copy output.mp4 (if codecs are compatível).

Web browsers do not support MKV natively because the HTML5 video element requires specific Container und Codec combinations. Browsers support MP4 (H.264/H.265), WebM (VP8/VP9/AV1), und Ogg. MKV's flexible Codec support would require browsers to implement decoders für every possible Codec. To abspielen MKV in ein Browser, transcode to MP4 mit ffmpeg: ffmpeg -i input.mkv -c copy output.mp4 (if Codecs are kompatibel).

Web browsers do not support MKV natively because the HTML5 video element requires specific contenedor y codec combinations. Browsers support MP4 (H.264/H.265), WebM (VP8/VP9/AV1), y Ogg. MKV's flexible codec support would require browsers to implement decoders para every possible codec. To reproducir MKV in un navegador, transcode to MP4 con ffmpeg: ffmpeg -i input.mkv -c copy output.mp4 (if codecs are compatible).

AV1 is the most efficient (royalty-free, ~30% smaller than H.265) but encoding is slow. H.265 (HEVC) saves ~30–50% over H.264 and is supported by every modern phone and desktop. H.264 remains the safest baseline for legacy compatibility. Rule of thumb: archives → AV1, daily use → H.265, broadest reach → H.264.

WebM is a restricted subset of Matroska created by Google for web use. It limits video to VP8, VP9, or AV1 codecs and audio to Vorbis or Opus — no H.264, no AAC, no Dolby. This restriction allows browser vendors to ship royalty-free codec support. MKV has no codec restrictions and supports lossless audio (FLAC, TrueHD), PGS subtitles, and attachments that WebM omits.

WebM is a restricted subset of Matroska created by Google para web use. It limits video to VP8, VP9, ou AV1 codecs e audio to Vorbis ou Opus — no H.264, no AAC, no Dolby. This restriction permite browser vendors to ship royalty-free codec support. MKV has no codec restrictions e suporta sem perdas audio (FLAC, TrueHD), PGS subtitles, e attachments that WebM omits.

WebM is a restricted subset von Matroska created by Google für web use. It limits video to VP8, VP9, oder AV1 Codecs und audio to Vorbis oder Opus — no H.264, no AAC, no Dolby. This restriction erlaubt browser vendors to ship royalty-free Codec support. MKV has no Codec restrictions und unterstützt verlustfrei audio (FLAC, TrueHD), PGS subtitles, und attachments that WebM omits.

WebM is a restricted subset de Matroska created by Google para web use. It limits video to VP8, VP9, o AV1 codecs y audio to Vorbis o Opus — no H.264, no AAC, no Dolby. This restriction permite browser vendors to ship royalty-free codec support. MKV has no codec restrictions y soporta sin pérdidas audio (FLAC, TrueHD), PGS subtitles, y attachments that WebM omits.

CRF (Constant Rate Factor) is the best default for offline files: ffmpeg picks the bitrate frame-by-frame to maintain perceived quality. Two-pass is only better when you must hit an exact final size (DVD targets). Constant bitrate is for streaming with a fixed channel. For "smallest at quality X" always use CRF.

Yes. Matroska supports adding, removing, and replacing subtitle tracks without touching the video or audio streams. Use mkvmerge: mkvmerge -o output.mkv input.mkv subtitles.ass. Or with ffmpeg: ffmpeg -i input.mkv -i subtitles.srt -c copy -c:s srt output.mkv. The video and audio are stream-copied with no quality loss.

Yes. Matroska suporta adding, removing, e replacing subtitle tracks sem touching the video ou audio streams. usar mkvmerge: mkvmerge -o output.mkv input.mkv subtitles.ass. ou com ffmpeg: ffmpeg -i input.mkv -i subtitles.srt -c copy -c:s srt output.mkv. The video e audio are stream-copied com no quality loss.

Yes. Matroska unterstützt adding, removing, und replacing subtitle tracks ohne touching the video oder audio streams. verwenden mkvmerge: mkvmerge -o output.mkv input.mkv subtitles.ass. oder mit ffmpeg: ffmpeg -i input.mkv -i subtitles.srt -c copy -c:s srt output.mkv. The video und audio are stream-copied mit no quality loss.

Yes. Matroska soporta adding, removing, y replacing subtitle tracks sin touching the video o audio streams. usar mkvmerge: mkvmerge -o output.mkv input.mkv subtitles.ass. o con ffmpeg: ffmpeg -i input.mkv -i subtitles.srt -c copy -c:s srt output.mkv. The video y audio are stream-copied con no quality loss.

Common causes: (1) variable framerate source rendered as constant (use <code>-vsync vfr</code> to preserve VFR); (2) different audio sample rates not resampled (add <code>-ar 48000</code>); (3) container limitations (MP4 with variable framerate misbehaves — prefer MKV during editing, encode to MP4 only at the end). Always run <code>ffprobe</code> on both source and output to compare timing.

Ordered chapters allow an MKV file to reference segments from other MKV files on disk. Anime distributors use this to avoid duplicating the opening (OP) and ending (ED) sequences across every episode: a single OP.mkv and ED.mkv file is referenced by each episode MKV, saving significant disk space. When a compatible player (VLC, mpv, MPC-HC) plays the episode, it seamlessly splices in the OP and ED from the separate files.

Ordered chapters allow an MKV arquivo to reference segments de other MKV arquivos on disk. Anime distributors usar this to avoid duplicating the abrindo (OP) e ending (ED) sequences across every episode: a single OP.mkv e ED.mkv arquivo é referenced by each episode MKV, salvando significant disk space. When a compatível player (VLC, mpv, MPC-HC) plays the episode, it seamlessly splices no OP e ED de the separate files.

Ordered chapters allow an MKV Datei to reference segments von other MKV Dateien on disk. Anime distributors verwenden this to avoid duplicating the opening (OP) und ending (ED) sequences across every episode: a single OP.mkv und ED.mkv Datei is referenced by each episode MKV, saving significant disk space. When a kompatibel player (VLC, mpv, MPC-HC) plays the episode, it seamlessly splices im OP und ED von the separate files.

Ordered chapters allow an MKV archivo to reference segments de other MKV archivos on disk. Anime distributors usar this to avoid duplicating the opening (OP) y ending (ED) sequences across every episode: a single OP.mkv y ED.mkv archivo is referenced by each episode MKV, saving significant disk space. When a compatible player (VLC, mpv, MPC-HC) plays the episode, it seamlessly splices en el OP y ED de the separate files.

Yes if you only change the container: <code>ffmpeg -i in.mkv -c copy out.mp4</code>. This remuxes the stream without re-encoding, takes seconds even for hours of footage. Limitations: codec must be supported by the target container (e.g. you cannot put H.264 in WebM, only VP8/VP9/AV1). To shrink size you must re-encode.