Google Drive Video Still Processing? Fixes and a Better Client Review Path
A Drive upload that never finishes processing can quietly eat two days of a delivery week. Here is what the status means, the fixes I run in my agency, and the review path I moved to.
The Google Drive video still processing banner sat on a client cut for an entire weekend because I sent the link on a Friday evening without opening it myself, so my client watched nothing, and on Monday morning I got a polite message asking whether we had delivered anything at all. That one banner cost my agency two working days on a campaign with a hard air date, right, and I had to absorb the delay in front of a client who had already paid, which is the kind of mistake you really really only need to make once.
The part that stung was that the file itself was fine, and anyone who clicked download would have had a perfect 12 GB ProRes master in about twenty minutes. The only thing that had failed was the browser preview, right, and for my client the browser preview was the whole product, because nobody downloads 12 GB just to leave one note about a logo.
So this is the post I wish someone had handed me that Monday, covering what the status actually means, the fixes I run in order, the export settings that play, what to tell a stuck client, and how I moved review off Drive while keeping Drive for storage.
What Google Drive video still processing actually means
When you upload a video to Drive, two separate jobs happen one after the other. The file lands first, which is usually the quick part, right, and then Drive starts building its own playable copy so the video can run inside the preview window of a browser tab. So your file is stored, safe and downloadable the whole time, and the banner is basically Drive telling you that the one action your client wants to take is not available yet.
Why Google Drive video processing takes too long
How long the wait runs depends on things you mostly do not control, like the duration, the file size, the codec, the load on Google's side at that moment, and so on. In my agency a light H.264 export of a 90 second ad usually comes back quickly, while a 14 GB master of a 40 minute interview can sit there for a very very long time, and sometimes Drive never produces a preview at all, which is when your client sees a playback error instead of a spinner. To be very honest, the error and the endless spinner are the same problem wearing different clothes, and the fix for both starts with what you uploaded.
Your file is already stored and downloadable while the banner shows. What is missing is the browser playable copy, which is the only thing your client actually needs.
Quick fixes when a Google Drive video is not playing
I run these in order, right, and I run them before I send anything rather than after the client complains. The first one is simply to open the link yourself in a private window, because the preview often finishes while you are still writing the email, and a private window shows you roughly what someone outside your account sees.
If it is still stuck after a genuine wait, re-uploading helps more than waiting longer, but only if you re-upload something different. Uploading the identical 14 GB master a second time hands Drive the identical hard job, right, so it tends to fail in the identical way, whereas a lighter export of the same cut is a much easier job. The catch here is that people delete the stuck file and upload it again out of frustration, so for instance I now leave the master where it is, export a lighter review version next to it, and share only the lighter one.
It is also worth trying a different browser, because an extension or a cached player sometimes breaks playback on one machine and not another, and an MOV master with a professional codec inside is a much harder preview job than a plain MP4. If the client is truly blocked today, send the download path and say so plainly while the lighter file goes up.
A sharing problem and a processing problem also look almost identical from the client's side. When you share a video with a client on Google Drive and general access is still set to restricted, only the people you added by email can open it, so a client who forwards the link to their boss gets a wall that looks like a broken video, and the fix is a sharing setting rather than a new export. I went through that mess in my notes on shared drive links for eLearning review, because the pattern repeats in every team that treats a storage folder as a review room.
Export settings that play more reliably for clients
The single biggest lever you have is what you hand over, because a browser has to decode whatever you upload and some codecs are friendlier to that job than others. An H.264 file at a sane bitrate plays nearly everywhere, right, while the newer HEVC compression standard is more efficient on size but its playback support varies across browsers and devices, so for a review copy I stay conservative and keep the fancy codec for the master.
Keep the frame rate of the review export matched to your timeline, because a conversion on the way out occasionally introduces stutter that your client will report as a bug in your edit. Keep the review copy at 1080p even when the master is 4K, and put a version number in the file name. For a rough cut or an animatic, none of your notes depend on resolution anyway, right, they depend on timing and structure and whether the joke lands.
A worked example with real file sizes
Here is the math I actually use, because it turns a vague instruction like keep the bitrate sensible into a number you can check before you hit export. File size in megabytes is roughly the bitrate in megabits per second, times the duration in seconds, divided by eight, plus a little for audio. So that 40 minute interview exported as H.264 at 8 Mbps is 8 times 2,400 seconds, which is 19,200 megabits, divided by eight, so about 2.4 GB instead of 14 GB, and a 90 second ad at the same bitrate lands near 90 MB. Those are illustrative numbers from the formula rather than a Drive benchmark, but in my experience shrinking the file that much is the change most likely to get a stuck preview playing.
If you cut in Resolve, I wrote up the specific settings in my Resolve export settings for review, and the habit of shipping a light proxy while the heavy original stays locked down is covered in my piece on sharing low-res proxies safely.
- H.264 rather than an exotic codec for the review copy
- 1080p even when the master is 4K
- Frame rate matched to the timeline, no conversion
- About 8 Mbps so a 40 minute cut lands near 2.4 GB
- A file name with the version number in it
What to tell a client who cannot play the video
Say it in one message, right, own it, and give them something to do. Something like this works: the file is uploaded and safe, the browser player is still building, here is a direct download if you want to watch now, and a lighter copy is going up in the next half hour that should play in the browser without the wait. That message stops the client from concluding that you missed the deadline, which at the end of the day is the conclusion you are really fighting.
What you want to avoid is the slow drip of can you try again messages, because each one moves the problem onto a client who did not choose your codec. I have had rounds die because a client tried twice, got nothing, and quietly moved the review to the following week, and nobody complained, the time just slid off the schedule.
A review round does not fail loudly, it fails quietly when the client tries once, sees a spinner, and moves on to something else.
Why client review links need reliable playback
When I looked at where my rounds were actually leaking, the leak was almost always in the mechanics around the feedback rather than in the feedback itself. A client who cannot press play cannot leave a note, and a client who watches a download in their own player leaves notes like the bit near the start with the music, because there is no shared clock between us, right, and that guessing game is exactly what frame-accurate commenting exists to kill.
Drive has been adding timestamps to video comments, which I weighed up in my piece on Google Drive timestamped video comments, but a timestamp on a spinner is still a spinner. Does that make sense, right? And if you are weighing storage rather than review, I covered that in comparing Google Drive and Dropbox, where the short answer is that both are good at storage and neither was built to run a review round.
client waits on a preview, downloads a heavy file, sends vague notes in WhatsApp
client presses play in the browser, comments land on the exact frame, replies thread under them
Streaming copies for review while the original file stays untouched
I moved the review step off Drive because I wanted the thing my client clicks to be built for playing. When you upload to PlayPause instead of Google Drive, the cut plays in the browser from a streaming copy while your original file is never touched, so the client gets a version made for playback and your archive stays exactly as you exported it. Streaming services have long kept the master in storage and sent viewers a version encoded for smooth playback, which is the idea behind HTTP Live Streaming and most video on demand platforms, so you see what I mean here, a storage product and a player have different jobs.
On top of that, comments stick to the exact frame, your client can draw on the frame to point at the logo they mean, and new versions stack on the same card as MV1, MV2, MV3 and so on, so nobody hunts through a folder for the latest file. The client opens one link in a browser with no account and no install, and the mechanics of how those playback copies are made live on the proxy and transcoding page.
Pricing is flat per workspace rather than charged per person, and for this problem the part of the Agency plan I lean on is the Google Drive integration, because viewers can save a file to Drive straight from the review link and you keep a Drive backup without making Drive the review room. For a head to head, I laid it out in Google Drive vs Frame.io, and for the Vimeo route there is my take on Vimeo private links for review.
Keeping Drive for storage and backups
None of this means dropping Drive, right, I still use it every day because it is a genuinely good place for finished masters, project archives and brand assets. What changed is the job I give it, so Drive holds the files, the review link carries the round, and if you would rather keep review media and archives under one roof there is also PlayPause media storage to look at.
Practically, the master goes to Drive for the archive, a light H.264 copy goes up for the round, notes come back on the frame, and only the approved final gets dropped into the client's Drive folder, which my guide on sending large video files to clients covers in more detail. I'm pretty sure most of the processing pain people report comes from asking one tool to do two jobs, and trust me on any level, once you split them the Monday morning panic messages mostly stop.
Frequently asked questions
How long should a Google Drive video take to process?
There is no fixed number, because it depends on duration, file size, codec and load on Google's side. In my experience a small H.264 export often previews within a few minutes, while a large master can take much longer or never produce a preview at all. My working rule is that if a file is not playable in the time it would take me to export a lighter version, right, I export the lighter version instead of waiting.
What does a video processing error in Google Drive mean?
Usually it means Drive could not build a browser playable copy, which happens most with very large files or less common codecs, and occasionally it is a permission issue wearing the same face. Check the link yourself in a private window first, and if it fails there too, re-upload a smaller H.264 version rather than the same master, because the identical file basically gives Drive the identical problem.
Can my client still download the file while it is processing?
In most cases they can, because the upload and the preview are separate jobs, so the file is complete and downloadable once the upload itself finishes. That download is your emergency path when a client is blocked and needs to see the cut today. It is a poor review path though, right, because notes taken in the client's own player come back without timestamps and cost you time to decode.
Should I just move client review off Drive completely?
I moved the review step and kept the storage exactly where it was. Drive is excellent at holding masters and archives, but it was never built to run a round where a client presses play, leaves a note on frame 412, draws on the logo, and then checks version three against version two. Splitting those two jobs was the single change that stopped my delivery weeks from wobbling, right, and I would make it again tomorrow.
If your rounds keep stalling on playback rather than on creative disagreement, you can see the plans on the PlayPause pricing page, where every plan comes with a 7-day free trial, and the honest test is to put one real cut in front of one real client and see whether the notes come back sharper than they did from a folder.
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