By Lucas, founder of FixMyVideos · Updated
QuickTime Error -2048: Why QuickTime Won't Open Your Video
QuickTime Player has a few ways of refusing a video. Older versions show Error -2048: Couldn't open the file because it is not a file that QuickTime understands. Recent macOS says The document "clip.mov" could not be opened or The file isn't compatible with QuickTime Player. All of them mean the same thing at the start: QuickTime looked for a movie it could play inside the file and did not find one.
That sentence covers two very different situations. Sometimes the file is perfectly healthy and QuickTime just doesn't support what's inside. Sometimes the file really is damaged. The fixes have nothing in common, so the first job is telling them apart.
Find out what the file actually is
Three commands answer most of it. ffprobe comes with FFmpeg (brew install ffmpeg on a Mac).
file clip.mov
ffprobe -v error -show_format -show_streams clip.mov
xxd -l 64 clip.mov
file reads the first bytes, not the extension. If it says Matroska, RIFF (little-endian) data, AVI or MPEG sequence, the file was never a QuickTime movie, whatever its name. If ffprobe prints streams with a codec and a duration, the file is structurally readable and the problem is compatibility. If it prints moov atom not found or Invalid data found when processing input, the file is damaged. And if xxd shows nothing but 00 00 00 00 rows, skip ahead to the section "When there is nothing to recover" below.
When the file is fine and QuickTime is the obstacle
Wrong container. QuickTime opens MOV and MP4 (plus M4V and a few relatives). It does not open MKV, WebM, FLV or WMV, it refuses most AVI files, and renaming one of those to .mov changes nothing. VLC or IINA will play it directly. To get a file QuickTime accepts, rewrap or convert it:
ffmpeg -i clip.mkv -c:v copy -c:a aac clip.mp4
If the video codec is one MP4 can't carry (Motion JPEG in an AVI, for instance), drop -c:v copy and let FFmpeg re-encode to H.264.
Codec QuickTime doesn't decode. VP9 and many professional or legacy codecs are refused even inside a correct MP4. HEVC needs macOS High Sierra or later, and AV1 depends on your Mac's chip and macOS version. If the file plays in VLC, it isn't broken. A re-encode to H.264 (-c:v libx264 -crf 18) gives you something every Apple app plays. You don't need a repair service for this, and you shouldn't pay for one.
When VLC plays it and the Mac refuses
FFmpeg, VLC and most Windows players are forgiving. AVFoundation, the engine under QuickTime, Photos, Final Cut and Safari, is not. A file can decode cleanly with FFmpeg from first frame to last and still be refused or mis-played on a Mac. Each case below was caught on a real Mac after every FFmpeg-based check had passed it.
- HEVC tagged
hev1instead ofhvc1. Both tags are legal for H.265 in MP4. FFmpeg writeshev1by default, and QuickTime, iOS and Safari refuse it. Check withffprobe -v error -select_streams v:0 -show_entries stream=codec_tag_string clip.mp4. If it sayshev1, this rewrap fixes it without touching the picture:ffmpeg -i clip.mp4 -c copy -tag:v hvc1 fixed.mp4. - B-frames with no composition offsets. iPhone HEVC uses B-frames, so pictures are stored in a different order from the one they're shown in. A small table in the file (
ctts) tells the player how to reorder them. Rebuild an iPhone stream without it and QuickTime opens the file but plays the frames in storage order, so motion jitters back and forth. FFmpeg reorders internally and never notices. With FFmpeg 6.1 or newer,ffmpeg -i clip.mp4 -c copy -bsf:v dts2pts fixed.mp4rebuilds the table. Watch the result before keeping it: on a stream that declares reordering but never uses it, we have measured this filter making the motion worse instead of better. - MP3 audio inside an MP4. It is allowed by the MP4 standard and FFmpeg plays it. On a Mac, QuickTime played one of our deliveries with picture and no sound at all. Converting the soundtrack to AAC fixes it:
ffmpeg -i clip.mp4 -c:v copy -c:a aac fixed.mp4. - 4K all-intra H.264 written as
aivxwith no decoder configuration. When FFmpeg's MOV muxer stream-copies a 4:2:2 10-bit all-intra stream at 3840x2160, it ignores the requestedavc1tag, writesaivxand leaves out the box that tells a player how to decode the stream. A Canon 4K recording we rebuilt this way opened green on a Mac, with eight horizontal coloured bands, one per slice of the picture. The missing box was one of two defects behind it; the other was parameter sets written only once, at the head of the file. Re-muxing into MP4 (ffmpeg -i clip.mov -c copy fixed.mp4) writesavc1with its configuration, and that version played on the same Mac. - Missing reference frames. When a few pictures that later frames depend on are absent, FFmpeg quietly paints over the holes and reports nothing. Apple's hardware decoder refuses the file outright ("Cannot Decode"). This one has no command-line fix, because the frames have to be found in the raw data again.
When the file really is damaged
A missing index is what an interrupted recording leaves behind. An MP4 or MOV keeps its picture and sound in one big block (mdat) and the map of where every frame sits in another (moov). Cameras and phones write the map last, when recording stops. If the battery dies or the card is pulled before that moment, the frames are on disk with no map. QuickTime finds no movie and says -2048 or "could not be opened". Our moov atom not found page covers that case in depth. FFmpeg can't fix it with a rewrap either, because there is nothing for it to copy from.
A subtler version is an index that exists but points at the wrong bytes. On a 287 MB Sony A7S III 4K test clip whose chunk-offset table we scrambled on purpose, our engine first recovered only 7 of 240 frames. The frame sizes in the index were still correct, so we now walk the media block guided by those sizes and rebuild the offsets. The same clip comes back with all 240.
Rebuilding the index from raw frames also means recovering the codec settings (resolution, profile, parameter sets) the decoder needs. When those settings are wrong, FFmpeg can still exit without an error and write a file with an audio track and no video track at all, which plays as a black screen. We had exactly that in a preview once. Every rebuild now counts the video packets it wrote and throws the file away if the count is zero.
When there is nothing to recover
Some files can't be saved by anyone, and you should know that before you pay for any tool.
- All zeros. A 30 MB DJI file that reached us had every one of its bytes set to
00. The name and size looked right. Where the zeros came from cannot be read from the file itself, only that nothing else is in it. - A header with nothing behind it. A 24-byte upload held one file-type box declaring an MP4 and not a single byte after it.
- A few sectors repeated. A 20 MB dashcam file held 12,288 bytes of distinct data (24 blocks of 512 bytes), each one repeated over and over until the file reached its full size. It looks like a transfer that kept reading the same few sectors.
All three show up in QuickTime as a file that won't open. If your copy looks like this, go back to the card or the original device, because the data you need may still be there and not in the copy.
What happens when you upload it
Our engine reads the file's bytes, not its name, so a real AVI or MKV is converted rather than treated as a broken MOV (an MKV that lost its header is rebuilt first, see repairing a corrupted MKV). If the file turns out to hold nothing recoverable, the analysis says so and offers no repair. What we deliver is built for Apple players: HEVC as hvc1, reordered streams with their timing table, never MP3 inside an MP4, H.264 with its decoder configuration.
Upload the file, up to 150 GB, and look at the free 5-second preview first. If it shows your footage playing, the full file costs €6 under 2 GB, €18 from 2 to 20 GB, €35 from 20 to 50 GB and €59 above that, VAT included. Uploads are deleted automatically after 48 hours.
FAQ
The file plays in VLC but QuickTime says it can't be opened. Is it corrupted?
Probably not, and you can check. VLC reads almost any container and codec. Run the ffprobe command above; if it lists streams and a duration, the file is readable and you have a compatibility problem. Check the codec tag, the audio codec and the container against the list on this page before paying anyone.
Why does it open on my newer Mac but not on my older one? That is a codec support difference, most often HEVC on a Mac older than High Sierra, or AV1 on a chip without support for it. Converting to H.264 gives you a file both Macs play.
QuickTime opens it, so why does the picture jitter or have no sound? That is not error -2048, but it comes from the same strictness. Jittering motion on an iPhone or HEVC file points to missing composition offsets, and silence points to an audio codec QuickTime won't play. MP3 is the one we caught doing this. Both have the one-line fixes above.
Will renaming the file from .mp4 to .mov help?
Only if the extension was wrong in the first place, which file clip.mov tells you. QuickTime decides by what is inside, so renaming a damaged MOV changes nothing.
Can I fix a missing moov myself? Sometimes, with a healthy reference clip from the same camera and settings and a tool such as untrunc (we compare the two approaches in untrunc vs FixMyVideos). If you don't have one, or the result plays badly, upload it and look at the preview.
Is my footage safe? The file goes over HTTPS to servers in the EU and is deleted automatically after 48 hours. Nobody opens it unless you ask us to or the automatic repair fails, and then only to recover it and to fix our repair software so the next file like it repairs on its own. It is never shared or used to train AI. See the privacy policy.
Related
- Moov atom not found
- Cannot decode H.265 on a Mac
- Video plays but there is no audio
- Black screen when playing a video
- Recover a MOV file
- Recover an HEVC file
Free preview · No commitment
Ready to recover your video?
Upload your file and get a free 5-second preview in about a minute. Pay only if the preview looks right.
Upload your file →