Why your iPhone opens one video file and refuses the next
Two files are both “videos”, both a couple of gigabytes, both downloaded from the same place. One plays the moment you tap it. The other shows a grey screen, or nothing at all. The difference is almost never the file being broken — it is what is wrapped around the picture, and which of those wrappers Apple decided to support.
- Plays out of the box
- MP4 and MOV holding H.264 or HEVC video with AAC audio.
- Usually refused
- MKV, AVI, WebM, FLV, WMV — whatever is inside them.
- The reason
- iOS reads the container before the video, and only a short list of containers is supported.
A video file is a box with several things in it
The word “format” gets used for two completely different things, which is where most of the confusion starts. A video file is a container: a box that holds a video track, one or more audio tracks, possibly subtitle tracks, chapter marks, cover art and a table telling a player where each of those begins. MP4, MKV, AVI, MOV and WebM are containers. They are the box, not the contents.
What is inside the box is encoded with a codec — the compression scheme that turns forty gigabytes of raw frames into two. H.264, HEVC (H.265), AV1, VP9 and MPEG-4 Part 2 are video codecs; AAC, MP3, AC-3, E-AC-3, DTS, FLAC, Opus and Vorbis are audio codecs. A single MKV file might hold HEVC video, one AC-3 audio track in English, one AAC track in Turkish, and three subtitle tracks.
So “can this device play an MKV?” is really two questions stacked on top of each other. Can it open the box, and can it decode what it finds inside? A player has to answer both with yes. Apple’s built-in playback answers no to the first question for most boxes, which is why the file never even gets far enough to fail on the second.
The words worth knowing
Five terms cover almost every conversation about video files. They are worth ten minutes because they turn “it doesn’t work” into a specific, answerable question.
- Container
- The file wrapper — MP4, MKV, AVI, MOV, WebM, TS. It decides what a file can hold (how many audio tracks, whether subtitles fit inside, whether chapters exist), not how good the picture looks.
- Codec
- The compression of the actual picture or sound: H.264, HEVC, AV1, VP9, AAC, AC-3, DTS, FLAC. Hardware decoding exists for a few of these; the rest have to be decoded by the processor, which costs battery.
- Bitrate
- How many bits per second the file spends. It is the single biggest driver of both quality and file size — a 4K film at 8 Mbps and the same film at 60 Mbps are the same resolution and nowhere near the same picture.
- Remux
- Moving the existing tracks into a different container without touching them. Fast, lossless, and the whole trick behind turning a live stream into a normal file. Nothing is re-encoded, so nothing is lost.
- Transcode
- Actually re-encoding the video into another codec. Slow, hot, battery-hungry, and lossy every single time — a converted copy is always a generation behind the original.
What Apple’s own playback accepts
This is the practical list as of iOS 17 and macOS 14 — the same rules the Files app, Quick Look, Safari and QuickTime all follow, because they share one media stack.
| Container | iPhone / iPad | Mac (QuickTime) | Typical contents |
|---|---|---|---|
| MP4 / M4V | Yes | Yes | H.264 or HEVC video, AAC audio |
| MOV | Yes | Yes | Apple’s own container, same codecs |
| MKV (Matroska) | No | No | Anything at all — the most flexible container in use |
| AVI | No | No | Older DivX/Xvid material, MP3 or AC-3 audio |
| WebM | No | No | VP9 or AV1 video, Opus or Vorbis audio |
| FLV / WMV | No | No | Legacy web and Windows video |
| TS / M2TS | Partly | Partly | Broadcast and Blu-ray streams |
| HLS (.m3u8) | Yes | Yes | Not a file — a playlist pointing at segments |
Even inside a supported container, a codec can still be refused: AC-3, E-AC-3 and DTS audio are common in films and are not decoded by the system player, which is why some MP4 files play with picture and no sound.
Why the list is that short
It is not an oversight. Apple ships hardware decoders for the codecs it supports, so an iPhone can play a 4K HEVC film for hours on one charge — the video never touches the main processor. Supporting every container and codec in the world would mean decoding a lot of it in software, with the battery and heat cost that comes with it, and taking on patent licensing for formats Apple has no interest in.
The consequence is that a general-purpose media player on iOS has to bring its own engine. Practically every one of them is built on the same open-source foundation — FFmpeg and its libraries — which understands roughly every container and codec that has ever shipped. That is the whole reason a third-party player opens files the system will not: it is not doing something clever, it is doing the decoding itself.
This also explains a difference you will notice between players. One that decodes in software will play anything but runs warm on a long film; one that hands the work to the hardware decoder whenever the codec allows it stays cool and lasts. A good player does both — hardware where it can, software where it must, and switches without asking you.
Three ways to watch a file iOS refuses
In order of how much they cost you in time and quality.
What actually separates a good player from a bad one
Nearly every media player on the App Store claims “all formats”. These are the things that differ once you are past that headline.
- Hardware decoding where it is possible
H.264 and HEVC should go to the hardware decoder, not the CPU. You can tell within two minutes: the device gets warm, or it does not.
- Every track exposed, not just the first
A film with three audio languages and five subtitle tracks should let you switch between all of them mid-playback, without reopening the file.
- Resume that actually resumes
Position saved per file, restored on reopen, and kept when the file is renamed or moved. Surprisingly rare, and the thing you will miss most.
- Sane behaviour on huge files
A 20 GB remux should scrub smoothly rather than freeze for four seconds at each seek. That is an indexing question, not a decoding one.
- Background audio and Picture in Picture
Being able to lock the screen and keep listening, or shrink the video into a corner while you reply to a message, is what makes a player usable on a phone at all.
- No re-encode step hiding anywhere
If an app “imports” or “optimises” your file for a few minutes before playing it, it is converting — with the quality loss and the wait that implies.
The same file across the three devices
The rules are identical because iOS, iPadOS and macOS share a media stack. What differs is what you can comfortably do around playback.
Storage is the constraint, so files usually arrive, get watched and get deleted. Background audio and Picture in Picture matter more here than anywhere else.
The natural place for long films, and the one device where an external USB-C drive full of video can be played in place, without copying anything onto the device first.
No storage pressure and no thermal ceiling, so software decoding of an awkward codec is essentially free. This is where a 40 GB remux belongs.
The questions this usually turns into
Is MKV better quality than MP4?
Neither is better — they are boxes, and quality lives in the codec and bitrate inside. MKV files often look better in practice because MKV is what people use for high-bitrate rips, while MP4 is what streaming services deliver at a fraction of the bitrate. Put the same video track in both and they are pixel for pixel identical.
Does converting MKV to MP4 lose quality?
Only if the tracks are re-encoded. If the video and audio codecs inside are already ones MP4 can carry, a remux just moves them across untouched — lossless and usually under a minute. If HEVC has to become H.264, or DTS has to become AAC, that is a re-encode and quality is lost.
Why does my 4K file stutter when a smaller one plays fine?
Either the codec is being decoded in software when it could use the hardware decoder, or the file is on slow storage — a network share or an external drive over a weak connection cannot always feed 80 Mbps. Copy it locally once as a test; if it plays, the decoding was never the issue.
What is the safest format to keep a library in?
MKV, if you want to keep everything the source had — multiple audio languages, subtitle tracks, chapters. MP4 with H.264 or HEVC, if maximum compatibility with every device in the house matters more than keeping the extra tracks. The one to avoid for anything new is AVI, which cannot carry modern codecs properly.
How FoxDL handles this
FoxDL carries its own media engine, so the container question never comes up. You put the file on the device and open it. The same engine plays music, so a film and a FLAC album sit in one library.
- MKV, AVI, WebM, FLV, WMV, MP4, MOV, TS and HLS open directly — nothing is converted, imported or re-wrapped first.
- Hardware decoding is used wherever the codec allows it, with a software path behind it for the ones it does not, so an ordinary film does not cost you battery.
- AC-3, E-AC-3, DTS, FLAC, Opus and Vorbis audio are decoded too, which is what fixes the silent-film problem — and the same decoders play FLAC and ALAC albums in that library.
- Every embedded audio and subtitle track is listed and switchable during playback.
- Position is remembered per file and survives renaming or moving it, because the library tracks files by identity rather than by path.
- Picture in Picture and background audio are there, and on iPad an external drive plays in place without copying.
Playback of your own files is part of the free version on every device — it is not metered and it is not a Pro feature.
Questions people ask about this
- How do I play MKV files on iPhone, iPad or Mac?
- Which video and audio formats does FoxDL play?
- Can I switch the audio track on a dual-audio file?
- Does FoxDL support Picture in Picture and background playback?
Keep reading
Subtitles, audio tracks, and the three ways they go wrong
Embedded versus separate files, the encoding that mangles accented letters, and how to fix drift.
Lossless, bitrate and the equalizer: what changes the sound and what does not
What lossless changes, what an equalizer really does, and what improves listening first.
Where your files actually live on an iPhone, and who can see them
The sandbox, where downloads actually go, and why renaming a file breaks so many apps.
Your library, finally in one place.
Free to download. No account, no sign-up, and the whole feature set is in the free version.