MOV File Not Playing for Your Client? Fix It With One Browser Link
A MOV file not playing is usually a codec or file size problem on the client's side. These are the quick fixes, and the browser link I now use so it stops happening.
Three minutes of 1080p ProRes 422 HQ comes out to roughly 5 GB, right, because that codec runs at around 220 megabits a second, and 220 times 180 seconds is about 39,600 megabits, which divided by eight is close to 5,000 megabytes. That's one file I used to expect a client to download and double-click on a Windows work laptop or an iPhone in the back of a cab. Then the reply would come in, a screenshot of a black window and a line saying MOV file not playing, can you resend, and the round would stall on something that had nothing to do with the edit.
To be very honest, for my first couple of years running the agency I treated this as a client problem, right, like they needed a better laptop or some player installed, so I would send a download link and a second export and a little instruction note, and so on. The catch here is that every one of those emails cost us most of a day on the round, and I'm pretty sure no client ever enjoyed learning what a codec is from their editor.
So this is the full troubleshooting pass from my side of the desk, and then the fix I use now in PlayPause and in my own agency, which is to stop sending files for review and send a browser link instead.
Why clients hit the MOV file not playing wall
A MOV file is basically a box, right, Apple's QuickTime container, and whatever sits inside that box decides whether a given computer can play it. A lot of agency presets export ProRes by default, because ProRes is lovely to edit and grade with, so the editor never thinks twice about it. The catch here is that ProRes was designed for editing machines, so when a finance manager double-clicks it on a work laptop, the default player finds no decoder and shows something like this video file cannot be played, or plays the audio over a black screen.
The same thing happens with HEVC, right. iPhones record in HEVC by default and plenty of editors export in it because the files come out small, but a lot of Windows machines need an extra extension to decode it, and older phones and locked down corporate laptops often can't play it at all. So the client sees a video codec not supported message, assumes I sent something broken, and replies to the whole thread asking for a new file.
Then there's size, because a 20 GB master stalls on a phone long before the codec even matters, and cloud previews tend to give up on big files and show a grey box with a download button. So the client downloads 8 GB over hotel Wi-Fi and we're right back at the default player problem, you see what I mean here.
Most of the time the MOV plays perfectly on your machine and the client's default player simply has no decoder for the ProRes or HEVC inside it.
Codecs, containers and file size in plain English
I explain this to new editors in my agency with a very very simple picture, right. The container is the envelope, MOV or MP4 or MXF, and the codec is the language the letter is written in, ProRes or H.264 or HEVC. A player has to open the envelope and also read the language, so a MOV with H.264 inside plays almost anywhere, while a MOV with ProRes 422 HQ inside plays beautifully on a Mac and fails on a lot of the machines your clients own.
The Apple ProRes format page explains why it's an intermediate codec built for editing rather than delivery, and the HEVC standard page covers why decoder support is still patchy on older hardware. At the end of the day, the rule I repeat constantly is that intermediate codecs stay in the edit bay and delivery codecs go to humans.
Bitrate drives size, so a codec running at about 220 megabits a second fills roughly 1.6 GB every minute, while an H.264 review copy at 10 megabits a second fills about 75 MB a minute. That's why the same three minute cut can be 5 GB or a couple of hundred MB depending purely on the export dialog, and I wrote a whole piece on compressing a MOV file if you want to go deeper.
Phones add their own trouble, right, because in my agency most first reactions to a cut happen on a phone, on mobile data, with a fussier built in player than your editing Mac. I dug into that side in getting precise notes from a phone, because the mobile problem turns out to be bigger than playback.
Quick fixes when a MOV file won't play on Windows
So the client is stuck and the call is in an hour, right, and the worst thing I can do is guess, because a guessed fix usually means a second wrong export and a second annoyed email.
Check what's inside the file first
On a Mac I open the file in QuickTime Player and choose Window, then Show Movie Inspector, and the Format line shows the codec and frame size straight away. On Windows, the free MediaInfo tool shows the same details. For instance, if the inspector says Apple ProRes 422 HQ at 1920 by 1080, that one line tells me the fix before I've even opened my editor.
ProRes means the client's player has no decoder, so I re-export. HEVC means either a missing Windows extension or a re-export. An H.264 file that still won't play is usually a 10-bit 4:2:2 file from a newer camera, which a lot of laptops and phones struggle with even though the codec name looks friendly. And if the client's copy is smaller than the one on my drive, the download simply didn't finish, which no codec fix will ever solve.
Re-export a review copy that plays everywhere
The fix that solves most cases is a review copy as H.264 in an MP4 container at 8-bit 4:2:0, which plays in basically every browser, phone and default player around. In Premiere I set the format to H.264, match frame size and rate to the sequence, and choose VBR 1 pass at about 10 megabits for 1080p with AAC audio. In Resolve I pick MP4 and H.264 on the Deliver page and restrict quality to 10,000 Kb/s. The YouTube recommended upload encoding settings put standard frame rate 1080p at 8 megabits and ask for 4:2:0 with the moov atom at the front of the file, which makes a handy sanity check.
Fixes on the client's side
If a re-export isn't possible, the client can try VLC, which carries its own decoders and will play ProRes and HEVC when the default Windows app refuses. On Windows it's also worth checking whether HEVC Video Extensions are installed from the Microsoft Store, because plenty of machines ship without them. For phones on weak Wi-Fi, a review copy under a few hundred MB is the move.
The catch here is that every one of these fixes puts work on the wrong person, right. Either I'm re-exporting and re-uploading on a deadline, or the client is installing software on a work laptop, which many corporate clients simply aren't allowed to do, and that's why skipping the file entirely is the fix I built my process around.
- Read the codec in QuickTime or MediaInfo
- Export a review copy as H.264 in MP4
- Try VLC or add the HEVC extension on Windows
- Shrink the review copy to a few hundred MB
- Or skip the file and send a browser link
Why sending the master file is the wrong move
Even when the master plays, sending it for review is the wrong move. The master is the most valuable file in the project, right, and sending it over a transfer link for notes means handing over the final deliverable while the cut is still unapproved and the invoice is still open. I wrote about this for colour work in why you never send a raw ProRes master, and the same logic applies to any cut.
Then there's the feedback that comes back, because a client watching a downloaded file sends notes as an email with rough timecodes, or a WhatsApp message saying the bit near the end feels slow. In my agency, notes over WhatsApp basically double the round, since the editor spends the first hour working out which moment each note means. Does that make sense, right, the playback problem and the vague notes problem both come from the review happening outside a proper review tool.
My large video file guide walks through every transfer option, and the PlayPause vs WeTransfer comparison is honest that a transfer link is fine for final files and just the wrong shape for notes. If your whole pipeline lives in ProRes, there's a ProRes sharing guide in this series too.
Send a 5 GB MOV, wait for the download, then decode vague notes from email and WhatsApp
Send one link, the client presses play in any browser and comments on the exact frame
Reviewing in the browser from a streaming copy
This is the part that actually fixed it for me, right. In PlayPause I upload the export once and it plays in the browser from a streaming copy while the original stays untouched, so the client never downloads anything or needs to know what ProRes is. They open one link in a browser, with no account and no install, and watch on whatever device they have.
Streaming to browsers is how video on demand services work and why protocols like HTTP Live Streaming exist, and for an editor the useful part is that the client's device stops deciding whether the round moves forward.
When the client presses pause, clicks on the frame and types, the comment sticks to that exact frame, and they can draw on the frame to circle the logo that's slightly off. My next cut stacks on the same card as MV2 and then MV3, so nobody digs through an inbox, and on the Agency plan I also lean on side-by-side version compare and AI transcription for notes about a spoken line. The Proxy & Transcoding page covers the streaming copy in detail, and replacing email review walks through the whole switch.
The client's device never has to understand your master, because the only thing it needs is a browser.
A link is only as good as its controls, right, so every plan has password-protected links and instant link revoking, and on Creator and up the who-watched analytics show who opened it, when and from which city. Trust me on any level, knowing the client watched it twice before the call changes how that call goes, and it's really really useful when someone says they haven't looked yet.
Uploading large exports without babysitting them
Uploading a big master used to be its own headache for me, with a browser tab left open all night. PlayPause has a Mac and Windows desktop app, so a heavy export goes up in the background while I keep working, and bulk upload takes 100 plus files at once when I'm dropping a batch of social cutdowns into one project.
On limits, Creator caps a single upload at 10 GB while Agency and Enterprise have no max upload size, so if your masters run bigger than that, Agency is where I'd start. Creator links last 30 days and the files expire with them, Agency links last 90 days and Enterprise links never expire. Pricing is flat per workspace with 10, 50 or 150 members included, so adding another editor doesn't change the bill while you stay inside that count.
If you cut in Premiere, the Premiere Pro panel lets you upload straight from the timeline and read comments inside Premiere, where clicking one jumps the playhead to that frame. For Resolve, Final Cut Pro and After Effects, the workflow is export, upload, review in the browser, then work through the notes in your editor, which is still far calmer than chasing a transfer link.
Frequently asked questions
Why is my MOV file not playing on Windows?
Most of the time the MOV is perfectly healthy and Windows simply lacks a decoder for what's inside it, usually ProRes or HEVC, right. The default player opens the container, finds a codec it can't read, and shows an error or plays sound over a black screen. VLC or the HEVC extension often sorts it, re-exporting as H.264 in MP4 almost always works, and a browser review link skips the question entirely.
What does this video file cannot be played actually mean?
It's a generic error that usually means the player couldn't decode the file, and less often that the file really is damaged from an interrupted export or download. I always check whether the file plays on my own machine and whether the client's download finished at full size. If both look fine, it's a codec issue on the client's side, and a lighter review copy or a browser link sorts it out.
Can a client watch ProRes without installing anything?
Not reliably from the raw file, right, because plenty of Windows machines and phones can't play ProRes out of the box. In PlayPause the client never has to, since playback happens in the browser from a streaming copy and your ProRes original stays untouched. They open the link, press play and comment on the frame with no account and no install.
How do I send a video any client can play?
For a final file, H.264 in an MP4 container at 8-bit 4:2:0 is the safest single export, using the review settings above with the bitrate raised. For review, I'd skip the file completely and send a browser link, because it plays on any device the client owns and the notes come back pinned to the exact frame, which saves a whole round of guessing.
Where I'd start this week
If a client tells you this week that the file won't open, upload that same cut to PlayPause and send them a link instead, and notice how different the round feels. Every plan starts with a 7-day free trial, the plan breakdown is on the PlayPause pricing page, and my notes on presenting a rough cut pair nicely with this one.
So yeah. That's my way of saying it.
Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free