Why an MKV says “Try to play”
When playback failsWhy an MKV says “Try to play”; When playback starts and then fails.
Matroska sits between the two clear answers. Chrome and other Chromium browsers demux it and play the H.264 and AAC most .mkv files carry. Firefox and Safari refuse the container regardless of what is inside it.
Rather than promising something that will fail for half of visitors, or hiding a file that would play perfectly well for the other half, the row says “Try to play” and names the attempt as an attempt.
If it does not work
- Try the same file in a Chromium-based browser.
- If that fails too, the file is likely using a codec inside the container that no browser will decode — HEVC and some audio tracks are common causes.
- Download it and use a desktop player, which will handle it.
Note: A failed attempt still uses some of your monthly allowance, because the player has to fetch part of the file before it can discover it cannot decode it.
When playback starts and then fails
Usually a codec inside a supported container. The player says so and offers a download.
A file can be in a container your browser supports and still contain a track it cannot decode. The most common case is video in HEVC, and the second most common is a surround audio track with no stereo alternative — which plays as silence.
What the player does
It stops, says what happened in a sentence, and offers the file as a download. It does not leave you looking at a black rectangle wondering whether it is still loading.
Other reasons playback stops
- Your monthly downloads-and-streaming allowance ran out mid-file.
- Your session expired — “Your session has expired — sign in again to play this file.”
- Playback is paused for maintenance; the status page will say so.