Getting an MKV to play on a smart TV from USB

There are two different failures hiding behind "my TV won't play this MKV", and the fix depends on which one you have. If the TV skips the file entirely, greys it out, or shows it as an unknown item, the container is the problem: remux to MP4 and the H.264 or H.265 video inside is copied across as it is, with no quality loss and no re-encoding.

If the picture plays but you get silence or a banner about an unsupported audio format, the container is fine and the audio track is DTS. Samsung's own developer specifications for recent model-year TVs state plainly that DTS is not supported, while AAC, HE-AAC, AC-3, Dolby Digital Plus, MP3 and Opus are. That one needs the sound converted to AAC — the picture can still be copied untouched.

Work out which failure you have first

The two look similar from the sofa and have different fixes, so identify yours before converting anything.

• The file does not appear in the USB browser at all, or is greyed out, or the TV calls the file type unsupported. That is the container, the file system on the stick, or a video codec the panel cannot decode.
• The file opens, the picture plays, and there is no sound — often with a message about the audio format. The container was accepted. The audio codec was not.
• The picture stutters or drops out after a few seconds. That is usually bitrate or a video profile the decoder can read but cannot sustain, not the container.

The fastest way to know what is actually inside the file is to read its streams. Drop the MKV onto the MKV to MP4 converter and it reports the container, the video codec and profile, the resolution, the frame rate, the audio codec and channel layout, and how many subtitle and extra audio tracks are riding along — all before you convert anything. If you want the reasoning behind that readout, the guide on checking a video's codec in the browser walks through what each line means.

Why an MKV gets refused when the video inside it is fine

MKV — Matroska — is a container, not a video format. Inside almost every MKV you download or rip is an ordinary H.264 or H.265 stream, exactly the kind your TV decodes all day from streaming apps and MP4 files.

TVs are inconsistent about MKV because the firmware ships with a hard-coded list of containers it knows how to demux and index, decided at manufacture. Some manufacturers include Matroska — Samsung's media specifications list MKV alongside MP4, AVI, MOV and TS. Plenty of budget panels, older sets and hotel TVs do not, and no firmware update is coming for them.

"Supported" is not binary either. A TV can accept the MKV container and still refuse a particular stream inside it — Samsung's specification restricts HEVC video to the MKV, MP4 and TS containers only. A set that plays one MKV can reject the next for reasons that have nothing to do with Matroska.

The DTS audio problem, and the only real fix

If the picture plays in silence, the audio track is almost certainly DTS or DTS-HD. It is common in Blu-ray rips and almost absent from streaming files, which is why one downloaded film fails where everything else on the stick works.

DTS is a licensed codec, and paying that licence on every set sold stopped making commercial sense. Samsung's developer documentation says it outright: DTS is not supported on current model-year TVs, and content should carry a selectable alternative track. There is no setting to turn it on. The track has to be converted.

This does not force a full re-encode. Video and audio are separate streams, so the picture is copied untouched while only the sound becomes AAC, which every modern TV decodes. The converter does this automatically when it sees DTS heading into an MP4: it tells you the picture can be copied but the audio must be re-encoded, then does exactly that. AC-3 and Dolby Digital Plus tracks are copied across untouched.

Silence with a working picture is not always DTS — several other causes produce the same symptom, and the guide on video that plays but has no sound works through them in order.

Converting it here, without uploading the film

The converter here runs FFmpeg compiled to WebAssembly inside your browser tab. The file is read from disk by the page, processed in a worker, and written back out as a download. It is never uploaded, so there is no queue, no upload wait, and nothing to delete afterwards.

1. Open the MKV to MP4 tool and drop the file in.
2. Read the summary. It names the video codec, the audio codec and whether this run will be a copy or a re-encode.
3. Leave the quality preset alone if the summary says the video will be copied — quality settings only apply to a re-encode.
4. Convert, then drag the MP4 onto the USB stick.

Two limits to know first. Files over 2 GB are refused, because a 32-bit WebAssembly heap cannot address them, and past roughly 300 MB the page warns you that the job needs around three times the file size in free memory. And subtitle tracks and extra audio tracks are dropped — only the first video and first audio stream survive, and the tool says so before it starts. Some TVs pick up an external .srt placed beside the video with a matching name, but that varies by brand.

If you are nervous about degrading a good rip, converting MKV to MP4 without losing quality covers how to tell a copy from a re-encode before you commit.

The USB stick itself: FAT32, exFAT and NTFS

A good share of "the TV won't see my film" problems are not the video at all. They are the file system on the stick.

The 4 GB ceiling on FAT32 belongs to the file system, not the TV, and it is why a 6 GB film refuses to copy across or arrives truncated. If the film is over 4 GB and the stick is FAT32, no amount of converting will help — reformat to NTFS or exFAT, whichever your TV's manual lists, and copy it again. Also keep the video in the root folder or one level down, avoid punctuation in the file name, and eject the stick properly so the file table is written out.

The same thinking applies beyond televisions — car head units are fussier still about USB video, and usually want a smaller resolution on top of the container change.

When the film is bigger than the browser can handle

Full rips regularly run past 2 GB, and the in-browser tool declines them rather than crashing your tab halfway through. That is a real limitation, worth stating rather than dressing up.

Two honest options. A desktop remuxer — FFmpeg itself, or MKVToolNix — repackages a 20 GB file in a minute with no size ceiling and no quality change, and it is the right tool for a large library. Or the Video Converter app on a phone or tablet, which uses the device's hardware encoder and has no file-size limit. The trade-off matters: the app always re-encodes and has no stream-copy mode, so a big high-bitrate rip comes back smaller and softer. For a film you care about, remux on a computer.

Still not playing after the conversion

If the MP4 is now visible but misbehaves, work down this list.

• 10-bit HEVC. Many sets decode 8-bit H.265 but not the 10-bit Main 10 profile that anime and HDR rips use. Converting to H.264 fixes it, but that is a real re-encode — slow, and it costs some quality.
• 4K or very high bitrate on a 1080p panel. The decoder has a ceiling. Re-encoding to 1080p in the tool's advanced options brings it under.
• Odd frame rates. Rips with variable frame rate can play out of sync on hardware decoders that assume a constant rate.
• Skip USB entirely. A media player app on the TV, or a laptop over HDMI, sidesteps the firmware's codec list altogether.

One note on privacy, since a whole film is involved: all of the above happens on your own machine because the converter has no server behind it. The reasoning in what online converters do with your files is architectural rather than a promise — a file that is never uploaded cannot be retained.