Video · MP4 to MKV
MP4 to MKV, a pure remux.
Matroska accepts every codec, so MP4 to MKV never needs a re-encode. The video and audio are copied bit-for-bit into a new wrapper on your device, in seconds, and not uploaded.
How to convert MP4 to MKV
- Choose your MP4. The track table lists the video, each audio track and any subtitles.
- Untick any audio track or subtitles you do not want in the MKV.
- Press Convert to MKV. Every kept track is copied, so even a multi-gigabyte file finishes in seconds to minutes depending on your disk and memory.
What actually changes
Only the container. The H.264 or HEVC video and the AAC audio bytes are identical before and after, so there is no generation loss, no re-encode wait and the file size changes by well under one percent (Matroska's overhead is a little different from MP4's). Subtitles in MP4 are stored as mov_text, a format Matroska's muxer rejects, so they are rewritten as SRT text; the words and timing are preserved. Chapters are carried over.
Why people want MKV
- Media servers and players that prefer Matroska for libraries with multiple audio languages and subtitle tracks.
- Archiving a file in an open container that can later take extra tracks.
- A workflow or tool that does not accept MP4 but accepts MKV.
If your reason is playback on a phone or in Safari, stay with MP4: those devices and the built-in gallery apps do not generally play MKV.
What gets dropped, and why
Phone MP4 and MOV files may include extra data tracks (timecode, motion or camera metadata, Live Photo information) and cover art stored as a picture stream. Matroska cannot store most of those data tracks, and a cover picture would appear as a bogus video track, so these are left out; the table names each one. Rotation flags on portrait phone video are stored differently in Matroska, and some players ignore them: if a portrait clip appears sideways in a player after converting, that player does not read the Matroska rotation setting, and the MP4 original is the better file for it.
Worked example
A 1.2 GB 1080p H.264 recording with AAC audio and an SRT-style subtitle track. Convert to MKV: video Copied, audio Copied, subtitle Re-encoded as SRT (a text rewrite, not an image change). The output is about 1.2 GB, and the conversion runs at the speed of copying the file rather than at the speed of encoding. A 1.2 GB file is above the 500 MB warning, so close other tabs first.
Common mistakes
- Expecting a smaller file. The size stays essentially the same.
- Expecting to add subtitles or audio. This converts what is in the file; it does not add tracks.
- Converting to MKV to fix a damaged MP4. A missing index (the file stops with a moov error) cannot be repaired by re-wrapping what is not there.
- Using MKV for a file you will upload to a social site. Most reject it.
Your file never leaves your browser
The tool has no upload step. It runs FFmpeg compiled to WebAssembly in a sandboxed frame whose content security policy allows only local blob and data URLs; no ad or analytics code is inside the frame. The MP4 is read from your disk (mounted so it is not first copied into memory), the MKV is assembled in memory, and you save it with the browser's own download. The only thing fetched is the converter engine after you choose a file.
Limits and what this does not do
- One file at a time, up to 2 GB; warning above 500 MB because the output is built in memory.
- No re-encoding at all, by design. If you need a different codec, use another tool on this site.
- Data and metadata tracks and cover art are dropped.
- No batch queue, no trimming, no merging.
Common mix-ups
-
Often assumedPutting an MP4 in an MKV improves the picture.
What the source saysRFC 9559 states Matroska is not a compression format but an envelope for streams. A remux changes the wrapper only, so the picture and sound are the ones already in the MP4. [1]
-
Often assumedMKV and WebM are the same, so an MKV will play in any browser.
What the source saysMDN says WebM is a format based on Matroska, with VP8, VP9, Vorbis and Opus as its required codecs. An MKV holding H.264 or AAC is not a WebM file and gets no such promise. [2]
Checked against these sources on .
Frequently asked questions
Is MP4 to MKV really lossless?
Yes. The video and audio data are copied unchanged into the Matroska container. No frames are decoded or encoded, so there is no quality change.
Will the MKV be bigger than the MP4?
Almost exactly the same size, typically within a fraction of a percent. Only the container overhead differs.
What happens to MP4 subtitles?
MP4 text subtitles (mov_text) are rewritten as SRT text because Matroska cannot store mov_text. Words and timing are kept; picture subtitles are copied as they are.
Why was a track left out?
Data tracks such as timecode or Live Photo metadata, and cover-art pictures, cannot be stored properly in Matroska. The table names each dropped track; your video and sound are untouched.
Why does my portrait video look sideways in some players?
Matroska stores rotation differently from MP4, and some players ignore it. The pixels were not changed; try another player or keep the MP4.
Does it work with HEVC and 4K?
Yes. Because nothing is decoded or encoded, resolution and codec do not matter for speed, only file size and available memory.
Can I convert a MOV to MKV here?
Yes. MP4, M4V and MOV inputs are accepted and treated the same way.
Is my file uploaded?
No. It is read and rewritten on your device in a frame with no network access.
Sources
Last checked
- RFC 9559: Matroska Media Container Format — the container structure: tracks, chapters, attachments, tags
- Matroska codec specifications — codec identifiers Matroska files use, including subtitle formats
- FFmpeg formats documentation — the MP4, Matroska, WebM and Ogg muxers and their options (movflags faststart)
- FFmpeg command-line documentation — stream selection with -map and stream copy with -c copy
- MDN: media container formats — which codecs each container can hold and where browsers can play them
- ffmpeg.wasm project — FFmpeg compiled to WebAssembly, the engine this page runs in your browser
- Emscripten file system API — WORKERFS, which lets the converter read your file without copying it into memory first
Runs entirely in your browser. Your file is read on your device and is never uploaded.