How to Convert MKV to MP4 (Without Re-encoding Where Possible)
What's Actually Different Between MKV and MP4
MKV (Matroska Video) and MP4 are both container formats — think of them as zip files that hold video streams, audio streams, subtitles, and chapter markers. The crucial point is that the video codec inside those containers is often identical. A typical MKV file downloaded from the internet will contain H.264 or H.265 video paired with AAC or AC3 audio. An MP4 file you'd upload to YouTube or play on a smart TV uses those exact same codecs. This is why the phrase 'convert MKV to MP4' is a bit misleading. In many cases, you aren't converting anything — you're remuxing. Remuxing means pulling the streams out of one container and dropping them into another without touching the actual encoded data. The result is bit-for-bit identical video quality, and the process takes seconds rather than minutes because your CPU isn't doing any heavy lifting. Where things get complicated is when the MKV contains audio in a format MP4 doesn't support natively — most commonly TrueHD, DTS-HD MA, or FLAC. In those cases, the audio track has to be re-encoded, usually to AAC or AC3. The video can still be remuxed losslessly while only the audio is transcoded. Full re-encoding of video (where quality loss and long processing times occur) is only necessary if the video codec itself is incompatible, which is relatively rare with modern files.
Checking Your MKV Before You Convert
Before running any conversion, spend 30 seconds identifying what's inside your MKV. This tells you exactly what the tool needs to do and helps you catch problems early. On Windows, right-click the file and open Properties — this gives you duration and file size but not codec details. For codec information, use MediaInfo (free, open-source). Open the file in MediaInfo and switch to the Tree view. You'll see something like: Video — Format: AVC (H.264), Profile: High@L4.1, Bit rate: 8 500 kb/s. Audio — Format: AC-3, Channels: 6, Bit rate: 640 kb/s. That example is a best-case scenario for remuxing: H.264 video and AC3 audio both go into MP4 without any re-encoding. Compare that to a Blu-ray rip showing: Audio — Format: MLP FBA (TrueHD), Channels: 8. TrueHD is not supported inside an MP4 container, so that audio track must be transcoded. Also check the subtitle tracks. MKV supports image-based subtitles (PGS/VOBSUB) and text-based subtitles (ASS/SRT). MP4 supports only a limited subtitle format (TX3G/SRT). If your MKV has PGS subtitles, they cannot be carried into the MP4 container at all — they'll either be dropped or burned into the video (which does require re-encoding). Knowing this upfront prevents unpleasant surprises after a 20-minute wait.
Using CocoConvert for Quick Browser-Based Conversion
If you have a standard MKV — H.264 or H.265 video with AAC or AC3 audio — CocoConvert's [MKV to MP4 converter](/convert/mkv-to-mp4) handles the remux automatically. Upload your file, select MP4 as the output format, and the service detects whether the streams are compatible. When they are, it performs a remux rather than a full transcode, which means a 4 GB file can be processed in under a minute depending on your upload speed. For files with incompatible audio (FLAC, DTS, TrueHD), CocoConvert re-encodes the audio track to AAC at 192 kb/s stereo or 384 kb/s for 5.1 surround, while leaving the video stream untouched. This is a reasonable default for most use cases — streaming to a TV, uploading to a platform, or sharing with someone whose device doesn't support MKV. Honestly, there are limitations worth knowing. CocoConvert currently has a 2 GB file size cap on free accounts and 8 GB on paid plans. If you're working with a 50 GB Blu-ray remux, you'll need a local tool (covered in the next section). The service also drops PGS subtitle tracks rather than burning them in, because burning requires full video re-encoding and significantly increases processing time. If subtitle preservation matters, check the output file before deleting the original. For everyday use cases — a TV show episode, a downloaded movie under 8 GB, a video file someone sent you — the browser-based approach is the fastest path from MKV to MP4 with no software to install.
Doing It Locally with FFmpeg (Free, No File Size Limit)
FFmpeg is the tool that powers most video conversion software under the hood, and using it directly gives you precise control. It's a command-line application, which puts some people off, but the commands for MKV-to-MP4 conversion are short and easy to remember. For a pure remux (no re-encoding at all), the command is: ffmpeg -i input.mkv -c copy output.mp4 The flag -c copy tells FFmpeg to copy all streams — video, audio, subtitles — without touching them. This is instantaneous on modern hardware. The catch: if your audio is in a format MP4 can't carry (like TrueHD or FLAC), FFmpeg will throw an error and stop. In that case, encode only the audio: ffmpeg -i input.mkv -c:v copy -c:a aac -b:a 384k output.mp4 Here, -c:v copy remuxes the video losslessly, and -c:a aac -b:a 384k re-encodes audio to AAC at 384 kb/s — good quality for 5.1 surround. For stereo content, 192 kb/s is fine. If you have multiple audio tracks and only want the first one: add -map 0:v:0 -map 0:a:0 before the output filename. To keep all audio tracks: -map 0:v -map 0:a. For subtitle handling, text-based SRT subtitles can be included with -c:s mov_text. Image-based PGS subtitles cannot go into MP4 at all — omit them with -map -0:s or they'll cause an error. FFmpeg runs on Windows, macOS, and Linux. On macOS, install it via Homebrew: brew install ffmpeg. On Windows, download the static build from ffmpeg.org and add it to your PATH. Processing a 10 GB MKV with -c copy takes roughly 15–30 seconds on a mid-range laptop.
When You Actually Need to Re-encode (And What to Expect)
Full video re-encoding becomes necessary in a few specific situations: the video codec is something MP4 doesn't support well (like AV1 in older players, or MPEG-2 from a DVD rip), you need to reduce file size significantly, or you're targeting a device with strict codec requirements (older Samsung TVs, for example, often reject H.265 above certain profile levels). Re-encoding always involves quality trade-offs and time costs. A 2-hour H.264 movie re-encoded to H.264 at a lower bitrate will look slightly worse than the original — the degree depends on how aggressively you compress it. Re-encoding to H.265 can achieve similar visual quality at roughly half the file size, but encoding time is much longer: expect 3–8x real-time on a mid-range CPU, meaning a 2-hour film could take 6–16 hours. GPU-accelerated encoding (NVENC on Nvidia, VideoToolbox on Apple Silicon) is much faster but produces slightly lower quality at equivalent bitrates. In FFmpeg, a basic H.264 re-encode with good quality looks like: ffmpeg -i input.mkv -c:v libx264 -crf 18 -preset slow -c:a aac -b:a 192k output.mp4 CRF 18 is near-transparent quality; CRF 23 is the default and noticeably smaller; CRF 28 starts to look soft. The preset slow gives better compression efficiency at the cost of encoding time — for archival purposes, use veryslow. If you're just trying to play an MKV on a device that doesn't support the format, re-encoding is often the wrong solution. Installing VLC or Infuse on that device is faster and preserves full quality. Reserve re-encoding for situations where you genuinely need a smaller file or a specific compatibility target.
Common Problems and How to Fix Them
A few issues come up repeatedly when converting MKV to MP4, and most have straightforward solutions. Audio sync drift: This sometimes appears when remuxing MKV files that were created with variable frame rate video — common in screen recordings and some camera footage. The video and audio were in sync in the MKV but drift apart in the MP4. The fix is to add -vsync cfr to the FFmpeg command to force constant frame rate, though this technically re-encodes the video timing. Alternatively, CocoConvert's remux engine applies a sync correction pass automatically when it detects VFR content. Missing audio after conversion: If your output MP4 plays video but has no audio, the most common cause is that the audio codec wasn't supported in the container and was silently dropped. Re-run with explicit audio encoding: -c:a aac -b:a 192k. File won't play on iPhone or iPad: Apple devices require H.264 Baseline/Main/High profile up to Level 5.1, or H.265 Main profile. Check MediaInfo for the video profile. If it says High@L5.2 or above, or if it's H.265 Main 10 (HDR content), you may need to re-encode for Apple compatibility. For HDR specifically, tone-mapping is required — a topic complex enough for its own article. Output file is larger than input: This happens when audio is re-encoded to a higher bitrate than the original, or when the muxer adds overhead. It's normal for the file to be within 1–2% of the original size after a remux. If it's dramatically larger, check that you aren't accidentally re-encoding the video. Chapters and metadata disappearing: FFmpeg's -c copy preserves chapters, but some online converters strip them. If chapter markers matter to you (for long films or TV compilations), verify the output in MediaInfo or VLC's Playback > Chapters menu.
Choosing the Right Method for Your Situation
The right approach depends on your file, your goal, and how much time you want to spend. For files under 8 GB with standard H.264/H.265 video and AAC/AC3 audio, CocoConvert's [MKV to MP4 tool](/convert/mkv-to-mp4) is the fastest option — upload, wait for the remux, download. No software installation, no command-line knowledge required, and the output quality is identical to the source. For files over 8 GB, for batch conversions of dozens of files, or if you need fine-grained control over which audio and subtitle tracks are included, FFmpeg with -c copy is the right tool. It's free, handles any file size, and the remux commands are simple enough to put in a shell script for automation. For genuinely incompatible source material — MPEG-2 video from DVD rips, AV1 content targeting older devices, or files that need significant size reduction — plan for a re-encode. Use HandBrake if you prefer a graphical interface: File > Open Source, select your MKV, choose the MP4 container in the Summary tab, and pick a preset like H.264 MRF 18 for high quality. HandBrake also handles audio track selection and subtitle burning in a straightforward way. One last note: always keep your original MKV until you've verified the output. A remux takes seconds and the file is lossless, but if something goes wrong — a dropped audio track, a subtitle issue, a sync problem — you want the source available to try again with different settings. Disk space is cheap; re-downloading a large file is not.