MKV Won't Play on Your TV, Roku or Fire Stick? Here Is the Fix

You copied a movie to a USB stick, plugged it into the TV, and got "unsupported file format". Or the Fire Stick shows video with no audio. Or the same file plays perfectly on your laptop and on your friend's Fire Stick, but not on yours. Frustrating — and almost always misdiagnosed.

Here is the short answer: when an MKV won't play on your TV, the .mkv extension is rarely the problem. MKV is just a container — a box. What breaks playback is what's inside the box: HEVC 10-bit video, DTS or TrueHD audio, or PGS image subtitles that the chip in your stick can't decode. Fix the contents and the file plays everywhere.

Why the same MKV plays on one device and fails on another

Streaming sticks decode video in hardware. Each model ships with a different decoder block, and support is wildly inconsistent:

• Fire TV Stick (older HD models) often choke on HEVC 10-bit while newer 4K models handle it fine — that's why the same file "works for your friend".
• Roku is the strictest of the bunch. Its USB media player and many channels reject MKV files outright or refuse specific audio tracks, which is what produces the classic Roku unsupported file format message.
• Smart TVs (Samsung, LG, Sony) each have their own list. A 2017 panel may play H.264 in MKV but silently drop DTS audio — giving you picture with no sound.
• Casting adds a second bottleneck: the app re-encodes or refuses the stream before it even reaches the stick.

So "does my device support MKV?" is the wrong question. The right question is: which video codec, audio codec and subtitle format are inside this particular file?

Step 1: Find the real culprit with MediaInfo

Install MediaInfo (free, Windows/macOS/Linux), open your file and switch to View → Text. You'll get something like this for a typical 4.2 GB release:

Video
Format               : HEVC
Format profile       : Main 10@L5@Main
Bit depth            : 10 bits
Width / Height       : 3840 x 2160

Audio
Format               : DTS
Channel(s)           : 6 channels

Text
Format               : PGS

Three red flags in one file. Here's how each one shows up on your TV:

• HEVC 10-bit / Main 10 → black screen, stutter, or "file not supported" on older sticks.
• DTS, DTS-HD, TrueHD, E-AC-3 → video plays, no sound. This is the number one cause of MKV no sound on smart TV.
• PGS or VobSub subtitles → subtitles simply never appear (they're images, not text).
• 4K / high bitrate → buffering or dropped frames even when the codec is supported.

If you prefer the command line, mediainfo --Output="Video;%Format% %BitDepth%bit" Movie.mkv prints the critical line in one shot.

Step 2: Remux if you can, transcode only if you must

There are two very different repairs, and picking the right one saves you an hour of CPU time.

Remuxing copies the existing video and audio streams into an MP4 container without re-encoding. It takes 30–60 seconds for a 4 GB file, loses zero quality, and works when your device supports the codecs but not the MKV container — which is exactly the Roku scenario.

Transcoding decodes and re-encodes the stream. It's slow (10–40 minutes for a feature film) and costs a little quality, but it's the only way to turn HEVC 10-bit into H.264 or DTS into AAC.

The sweet spot most people need is a hybrid: copy the video, re-encode just the audio. That fixes the no-sound problem in about a minute.

Step 3: The ffmpeg commands that actually fix it

Install ffmpeg and run one of these from the folder containing your file. All of them include -movflags +faststart, which moves the index to the front of the MP4 — important for smooth seeking over a network.

A. Container swap only (H.264 + AAC already inside, Roku rejects the MKV):

ffmpeg -i Movie.mkv -map 0:v:0 -map 0:a:0 -c copy -movflags +faststart Movie.mp4

B. Picture fine, no sound (DTS or TrueHD audio):

ffmpeg -i Movie.mkv -map 0:v:0 -map 0:a:0 -c:v copy \
  -c:a aac -b:a 192k -ac 2 -movflags +faststart Movie.mp4

-ac 2 downmixes 5.1 to stereo, which is what you want when the TV speakers are the end of the chain. Keep -ac 6 if you pass audio to a receiver.

C. Full rescue (HEVC 10-bit 4K → universally safe 1080p H.264):

ffmpeg -i Movie.mkv -map 0:v:0 -map 0:a:0 \
  -c:v libx264 -preset medium -crf 20 -pix_fmt yuv420p -vf scale=1920:-2 \
  -c:a aac -b:a 192k -ac 2 -movflags +faststart Movie.mp4

-pix_fmt yuv420p forces 8-bit output — skip it and you'll produce a 10-bit H.264 file that fails on the exact devices you're trying to fix. A 4.2 GB HEVC source typically lands around 2.5–3 GB at CRF 20.

D. Subtitles that never show up. PGS subtitles can't live in MP4. Burn them into the picture (this forces a video re-encode):

ffmpeg -i Movie.mkv -filter_complex "[0:v][0:s:0]overlay" \
  -c:v libx264 -crf 20 -pix_fmt yuv420p -c:a aac -b:a 192k Movie-subs.mp4

If the subtitles are SRT or ASS text, convert them instead: -c:s mov_text keeps them as a selectable track inside the MP4.

No command line? Convert MKV to MP4 in the browser

If you just want the file to play tonight and don't fancy installing anything, run it through our MKV to MP4 converter — drop the file in, download an MP4 with H.264 video and AAC audio, copy it to the USB stick. It's the same output as command B or C above, without the setup.

This is the right route for a handful of episodes or a single movie. For a 400-file library, scripting ffmpeg is still faster. If you also need to deal with AVI, MOV, WMV or WebM files on the same drive, the broader video converter hub covers those formats too.

The Plex and Jellyfin angle: aim for Direct Play

Running a media server changes the equation but not the physics. Plex and Jellyfin will happily transcode an HEVC 10-bit DTS MKV on the fly — but that leans on your server CPU, and a low-powered NAS will buffer, stutter or drop to 480p under load.

Open the playback dashboard while a problem file streams. If it says Transcode next to video or audio, that stream is the bottleneck. Converting those files once to H.264 + AAC flips them to Direct Play, and your server stops breaking a sweat. A useful habit: keep the original MKV for archive, serve a converted MP4 to the TV.

The settings that play on virtually every stick

When in doubt, target this profile. It plays on Roku, every Fire TV generation, Chromecast, Apple TV, game consoles and TV USB ports:

• Container: MP4 with faststart
• Video: H.264 High profile, 8-bit (yuv420p), 1080p or lower
• Bitrate: CRF 20–23, roughly 4–8 Mbps for 1080p
• Audio: AAC-LC, 192 kbps, stereo (or 5.1 AC-3 if a receiver is in the chain)
• Subtitles: mov_text for text, burned in for PGS/VobSub
• USB drive: formatted exFAT or FAT32 — note FAT32 caps single files at 4 GB

Convert one problem file first, test it on the actual device, then batch the rest. Thirty seconds of verification beats re-encoding a season twice.

FAQ

Does Roku support MKV at all?<br>Roku's support is narrow and model-dependent — many MKVs trigger unsupported file format even when the video codec is fine. MP4 with H.264 and AAC is the reliable choice.

Why does my MKV play with no sound on my smart TV?<br>Almost always DTS, DTS-HD or TrueHD audio that the TV can't decode. Re-encode just the audio track to AAC (command B) — it takes about a minute and the video stays untouched.

Will converting MKV to MP4 lose quality?<br>Not if you remux with -c copy: the streams are copied bit for bit. Quality only changes when you re-encode, and CRF 20 is visually very close to the source.

Why does the file work on my Fire Stick but not my partner's?<br>Different hardware decoders. Older Fire TV Stick models lack HEVC 10-bit support that the 4K models have. One 8-bit H.264 copy serves both.

Can I just rename .mkv to .mp4?<br>No. The extension doesn't change the internal structure, and the player will fail to parse it. You need a real remux or conversion.

My 6 GB MP4 won't show up on the TV's USB input.<br>Check the drive format. FAT32 can't store files over 4 GB; reformat to exFAT or lower the bitrate.