MKV to MP4 Converter

You did the patient thing. Every disc and download went into MKV — chapters intact, subtitles preserved, every stream exactly as it was captured. Two hundred films and forty seasons later, the library is a monument to doing it right, and it plays beautifully on the machine it lives on. Then you visit your parents, or open your editor, or try to send a clip to the group chat, and the world goes gently hostile: the TV announces it cannot read the format, the editing software pretends the file was never there, and the chat app declines anything wearing that particular three-letter extension.

Here is the part almost nobody tells you: in most of those cases, nothing inside the file is wrong. The video itself — usually H.264, the same codec that carries most of the internet's video — is already perfectly decodable by the device refusing it. What the device objects to is the wrapper. MKV is Matroska, an open, capacious container that consumer hardware was never obliged to support. MP4 is the container nearly everything was licensed to play. Same content, different envelope, and the envelope is the entire fight.

This converter settles that fight in the cheapest way available. It opens your MKV locally, inspects the streams inside, and — when the codecs are MP4-friendly, which they usually are — repackages them without touching a single compressed frame. That path takes about as long as copying the file. When the streams are not compatible, the tool says so plainly and offers a re-encode with settings you control. Either way, an 8 GB movie never has to make a round trip to somebody's server farm to become a file your television likes.

1. 1

   Load the MKV

   Drag the file onto the page or click to browse. It opens into the browser's media engine; there is no upload step, so a 9 GB remux starts just as fast as a 9 MB one.

2. 2

   Read the stream report

   The tool lists what is actually inside: video codec and profile, audio codecs, resolution, duration, subtitle tracks, chapters. MKV files are honest about their contents, which is exactly what makes a smart conversion possible.

3. 3

   Confirm the smart path

   Compatible streams get remux mode by default — stream copy, zero re-compression. If something inside is MP4-hostile, the report marks it in red and the fallback encode becomes the offered route instead.

4. 4

   Choose the tracks that travel

   Multiple audio tracks, commentary, subtitles: keep what MP4 can carry, leave what it cannot. Subtitle handling is flagged explicitly rather than silently dropped.

5. 5

   Convert and download

   Remuxes finish at disk speed — an 8 GB file in well under a minute on an SSD. The MP4 downloads in faststart layout, so streaming players begin instantly instead of buffering through an index hunt.

A container is a filing system for video, audio, subtitles, and metadata; the codec is the language the contents are written in. Confusing the two is why "convert MKV to MP4" sounds scarier than it is. The question is never "translate this video" — it is "re-file these papers in a binder the reader accepts." Nothing about the papers changes.

Matroska, the format behind .mkv, is built on EBML — Extensible Binary Markup Language — a self-describing binary tree. Its designers optimized for generosity: practically unlimited tracks, any codec anyone dreams up, chapter markers, font attachments, soft subtitles in elaborate formats, and error recovery that lets a player continue after a corrupt span. Archivists, subtitle authors, and open-source tools adore it for exactly those qualities. Consumer electronics manufacturers, who pay per decoder they ship, largely ignored it.

MP4 is the disciplined one. Formally ISO/IEC 14496-14, it descends from the ISO Base Media File Format (14496-12), which itself descends from Apple's QuickTime File Format — a family tree worth remembering when you meet the MOV cousin of this same conversion. Structurally it is a sequence of boxes: ftyp declaring the brand, moov holding the index of every audio and video sample, mdat holding the samples themselves. The diet is strict — a short list of sanctioned codecs, of which H.264 video and AAC audio form the universal pair.

That strictness is the whole commercial story. H.264-in-MP4 is the one combination guaranteed to decode on virtually every phone, television, console, browser, and editing timeline sold in the last fifteen years. So the interesting question about any MKV is not "is it good video?" but "is it H.264?" — and for most files in most libraries, the answer is yes.

Remux — short for remultiplex — is the trade's word for moving streams between containers without decoding them. The tool parses Matroska's cluster structure, pulls out the compressed H.264 access units and AAC audio frames, and writes them into fresh MP4 boxes with a correctly built moov index. The compressed bits that describe every pixel of every frame are copied, never interpreted. There is no quality loss because there is no transformation: the video stream in your new MP4 is bit-identical to the video stream in the old MKV.

One genuinely technical wrinkle happens at the header level, and it deserves to be known. H.264 arrives from Matroska in "Annex B" framing — each chunk of encoded data preceded by a start-code marker — while MP4 wants the AVCC arrangement: a four-byte length prefix on each chunk, with the codec's setup parameters stored once in the avcC box instead of repeated in-band. Rewiring that framing is bookkeeping, not re-compression; the encoded picture data passes through untouched. It is the difference between re-addressing envelopes and rewriting the letters inside them.

Speed follows from the architecture. Nothing is decoded and nothing is encoded, so the CPU barely wakes up — run time is bounded by how fast your storage can read the MKV and write the MP4. On a laptop with an SSD that means a couple hundred megabytes per second, and an 8.7 GB feature film repackaged in about forty-five seconds. The same film as a quality-conscious re-encode takes the better part of an hour on the same machine.

Some streams cannot ride the free path. Video in VP9 or AV1, audio in DTS, TrueHD, or FLAC, ten-bit H.264 variants that hardware decoders never learned — none of these have a sanctioned seat in mainstream MP4 playback, and the only honest options are re-encoding them or accepting that some devices will refuse the result.

Re-encoding means decoding every frame and compressing it again, and it charges you three ways. Time: the CPU does real work — minutes per short clip instead of seconds, tens of minutes per hour of film on an older laptop. Quality: a second pass of lossy compression costs a generation; a careful encode at a high quality setting keeps the damage below what most eyes catch on most content, but below notice is not zero. Size: the output is whatever your quality setting produces, which can land larger or smaller than the source depending on how efficient the original encode happened to be.

The fallback exists because sometimes the trade is obviously worth it. A VP9 file your television cannot open is worth exactly nothing to that television; four gigabytes of H.264 that it plays happily is worth four gigabytes. The fallback encode defaults to a conservative quality level and leaves the choice to raise or lower it with you — the one decision no converter should make silently on your behalf.

# Remux: copy streams, change only the container
ffmpeg -i input.mkv -map 0:v -map 0:a -c copy -movflags +faststart output.mp4

# Fallback re-encode when codecs are incompatible
ffmpeg -i input.mkv -c:v libx264 -crf 20 -preset slow -c:a aac -b:a 256k output.mp4

The remux output is about 20 MB smaller than the source — Matroska's structural overhead plus the dropped subtitle and chapter tracks, nothing more. Forty-four seconds against forty-seven minutes is a factor of roughly sixty-four, and that ratio holds across file sizes because both paths scale linearly with duration. The re-encode's 4.3 GB looks tempting until you remember what it bought: half the storage, at the price of a generation and most of an evening.

The upload arithmetic is worth doing too, because it is the hidden cost of cloud converters. Sending 8.7 GB — about 70 gigabits — over a 40 Mbps connection takes twenty-nine minutes before any conversion begins; then you wait in a queue, then you download everything back. The local remux finishes before the cloud version has finished leaving your building. On hotel or metered internet, the comparison stops being funny.

Mixed files are common and the map handles them piecemeal: a film with H.264 video and DTS audio remuxes the picture and re-encodes only the soundtrack. That is the correct economy — spend effort exclusively on the streams that need it, and let everything else travel free.

• HEVC branding. HEVC ships in two MP4 flavors, hvc1 and hev1, and Apple devices historically accept only hvc1, where the codec's parameter sets live in the sample entry rather than in-band. The tool writes hvc1; a share of the "my HEVC file won't play on iPhone" complaints on the internet come down to that single branding choice.
• Ten-bit H.264 (Hi10P). Anime encoders love it, hardware decoders do not. A remux preserves it perfectly, but playback fails on most televisions — the report flags it and recommends the fallback so you can decide with the facts.
• Variable frame rate. Screen recordings and OBS captures often carry timestamps that drift. A remux preserves them faithfully; some editors and platforms expect constant frame rate and stutter on VFR, and the fallback encode can conform the timeline when a destination demands it.
• Multiple audio tracks. Commentary, dubs, and original language can all ride in MP4; the track picker exists so the choice of which ones make the trip stays yours.
• Chapters and attachments. MP4 has a chapter mechanism, but support outside players like VLC is thin, and font attachments for styled subtitles have nowhere to live. Both are dropped with a notice — one more reason the MKV remains the master.
• Truncated files. An interrupted download leaves Matroska without its index; the parser can rebuild from cluster headers and salvage what is readable, then tell you how much survived rather than pretending the file was whole.
• Copy protection. Encrypted streams cannot and will not be converted. That is not a technical gap to engineer around; it is the line this tool does not cross.

• Home-media librarians running Plex or Jellyfin, whose server handles Matroska beautifully but whose relatives' TVs and hotel-room sticks do not.
• Editors receiving MKV source footage — several major editing applications refuse Matroska at the import dialog, and a fast remux keeps the footage untouched while making it editable.
• Course creators and teachers, because every learning-management system on earth accepts MP4 and approximately two of them accept MKV.
• Subtitlers and translators who need an MP4 preview copy of an MKV master to send to reviewers who would never install a Matroska-capable player.
• Podcasters with video versions — the MP4 becomes the upload, the MKV stays the archive, and trimming dead air first with the Audio Silence Remover keeps the deliverable tight.
• Anyone sharing clips to group chats, where the receiving phones decide what plays and MP4 is the safe bet.

The conversion earns its keep at the edges of other jobs, too. Need three seconds of that film as a looping preview? Run the remux, then cut the clip with the Video to GIF Converter. Want only the concert's audio? The M4A to MP3 Converter handles the soundtrack while the MP4 handles the picture. And if your source is an iPhone's .mov rather than an MKV, the sibling MOV to MP4 Converter speaks that dialect natively.

The fair reading of that table: cloud converters exist because re-encoding is a real service and hosting it costs them money. But most MKV-to-MP4 requests never needed the service — they needed a filing change. Charging an upload, a queue, and a subscription for what is structurally a file copy is the modern version of paying someone to re-address an envelope. This page exists so you do not have to.

The privacy argument here is unusually concrete because the files are unusually large. An MKV library is personal — family archives, concert films, the media you chose to keep — and the cloud workflow for converting it requires handing all of it to a third party, at speeds that make the handoff itself a twenty-nine-minute ceremony. The local path never starts that clock. The file opens in your browser, the repackaging happens in your machine's memory, and the download is a file you could have copied yourself with a file manager.

Nothing is stored, because there is nothing to store it in — no account, no upload endpoint, no conversion history carrying your file names. Load the page once and it keeps working offline, which also makes it the converter of last resort on airplanes, in edit bays with no outside network, and on machines whose entire purpose is to never touch the internet.

Sibling jobs live one click away: the MOV to MP4 Converter for iPhone and QuickTime sources, the Video to GIF Converter for turning clips into loops, and the M4A to MP3 Converter when you want the audio alone. The philosophy carries across every one of them: run it locally, keep the master, and spend your minutes on something a machine cannot do for free.