Convert MKV to M4V

On a server the MKV is never really played as it is. Plex, Jellyfin and Emby inspect it, decide what the client in front of them can handle, and rebuild the stream on the fly — picking an audio track, converting a codec the device cannot decode, and drawing the subtitles into the picture if the player cannot switch them. All of that happens between the file and your screen and none of it is stored.

Take the file out of that arrangement and none of the service comes with it. That is the real shape of this conversion: not a change of extension but the loss of a live translator. What the M4V has to be is a file that needs no translator at all, and everything below is about what that costs.

Apple has never shipped Matroska support in the Photos, Files, TV or QuickTime paths. Hand an iPhone an MKV and it does not offer to play it; hand a Mac one and QuickTime declines it. Third-party players like VLC and Infuse read it perfectly, which is what makes the refusal feel arbitrary — it is a platform decision rather than a technical impossibility.

M4V is the other side of the same decision. Apple introduced the extension in 2005 for video sold through its own store, and everything in the ecosystem treats a file with that name as a video it owns. Underneath it is ordinary MPEG-4; the store’s copies additionally carry FairPlay protection, which nothing produced here has and nothing here could remove.

This converter reads video tracks and audio tracks. Subtitle tracks are not refused, they are never seen — the engine has no concept of them, so a soft-subbed MKV and a plain one look identical to it. If the film is in a language you do not speak, the M4V you get back is not a slightly reduced version of what you had. It is unwatchable.

The fix takes about a minute and happens before you come here. MKVToolNix extracts every subtitle track out of an MKV without touching a frame, and an SRT with the same base name sitting next to the M4V is picked up by VLC and Infuse on iOS automatically. The Apple TV app is fussier about sidecar files than either of those, which is a reason to use a third-party player for subtitled material and keep the TV app for the rest.

Audio is the part that goes better than expected. All audio tracks the browser can decode are written into the M4V in the order the MKV held them, because the MPEG-4 container has no practical ceiling on how many it stores. A release with an original language, a dub and a commentary produces a file where the player’s audio menu offers all three.

That is the exception rather than the rule on this site, and it is the reason to convert the video rather than pull the sound out. An MP3, an AAC, a WAV or a FLAC made from the same MKV keeps exactly one soundtrack and discards the others without comment, because those formats have room for one.

Before any soundtrack is converted the browser is asked whether it can decode it, and if the answer is no the track is dropped while the picture carries on. The conversion succeeds, the file looks correct, and it plays in silence. Nothing flags it at the moment it happens.

The codecs this catches are exactly the ones disc rips use: AC-3 and E-AC-3 from DVD and Blu-ray, DTS in its several forms, and Dolby TrueHD. Those carry their own licensing and browsers do not ship decoders for them. An MKV that came from a camera, a capture card or a download tool carries AAC or Opus and is never affected. If yours came off a disc, play the first ten seconds of the M4V before you sync it anywhere.

This is the setting that decides whether the file fits on the device. A 4K rip dropped to 1080p loses three quarters of its pixels and roughly that share of its size, and on a phone or a tablet held at arm’s length the difference is not visible. For a long flight, 720p is a perfectly respectable trade that puts three films where one was.

The control only ever reduces — asking for more than the source has is ignored on purpose, since upscaling invents no detail and costs bytes for nothing. Do the reduction here rather than leaving it to the device: an iPhone playing a 4K file it has to scale down on every frame spends battery doing work that could have been done once.

The output codec is fixed rather than inherited. Whatever was in the MKV — H.264, HEVC, VP9, AV1 — the M4V holds H.264 at High profile with AAC audio, the combination every Apple device made in the last decade and a half decodes in hardware.

For a 4K HEVC source this is the one case where converting is arguably a step backwards: modern iPhones and Apple TVs play HEVC natively, and H.264 needs more bits for the same picture, so the M4V can be larger and slightly softer than what you started with. If the device only refused the container rather than the codec, remuxing with a desktop tool keeps the HEVC and loses nothing.

Everything happens inside the browser tab, on your own processor, with the decoders the computer already has for playing video. Nothing carrying the file is sent to a server, there is no account, and there is nothing queued behind other people’s uploads.

That is worth more than it sounds for this pair. Media libraries are personal by definition — home recordings, purchased material, things ripped from discs on a shelf — and the ordinary route for this conversion involves handing several hundred megabytes of it to a website found ten seconds earlier. The free tier stops at 100 MB, which is a real limit rather than a nudge towards an account, and for anything larger HandBrake on the desktop is the honest recommendation.