Google Drive Says "Quota Exceeded" On Your Video — Here's What That Actually Means
A Drive video that played fine yesterday suddenly won't load for anyone signed out. It isn't your sharing settings and it isn't the tool you're using. Here's the real cause and the three ways out.
You share a Google Drive video, it works. A few hundred views later, everyone who isn't signed into a Google account gets nothing — a spinner, a blank player, or an error. You check the sharing settings and they still say "Anyone with the link". Nothing changed.
Nothing you did, anyway. The file hit Google's anonymous viewing quota.
What Google actually says
Behind the player, Drive returns a very specific error. Stripped of the technical wrapping, it reads:
"Playback quota exhausted. Sign into your Google Account to continue to play this video. The limit has been hit for viewers who aren't signed in."
That sentence is the whole story. Google caps how much a single file can be watched by signed-out viewers. Once that cap is reached, signed-out playback stops until it resets. Signed-in viewers with access are unaffected, which is exactly why the owner never notices — you're always signed in when you check.
The three things everyone gets wrong about it
It is not your sharing settings. A file that isn't shared publicly fails differently: Google returns a permission error, not a quota error. If your link genuinely weren't public, you'd get "you need access", not a video that used to work and now doesn't.
It is not the tool you're using. This one costs people a lot of time. The quota belongs to the file, not to whoever is asking for it. We tested this directly: five different Drive files requested from the same machine in the same second returned three successes, one quota error, and one permission error. Same network, same moment, different outcomes — because the limit is per-file. Switching tools, browsers, networks, or VPNs changes nothing.
It is not permanent. The quota resets. Google doesn't publish the window and it appears to depend on file size and traffic, but files that hit the wall generally come back within a day or so.
Three ways out, in order of speed
1. Make a copy of the file. A copy is a new file with its own id, and therefore its own quota. In Drive, right-click the video and choose "Make a copy", then share the copy. This is the fastest fix if you need the link working again right now, and it's why heavily-shared Drive videos often end up with several duplicates.
2. Download it and upload the file directly. If you only need the transcript rather than a working share link, skip the link entirely. Download the video from Drive (you can always download your own file, quota or not) and upload it. On SubGrab this is the same price as a URL, and your browser extracts just the audio before anything is sent, so a 700 MB video becomes a few megabytes in transit.
3. Wait. If the video isn't urgent, the quota clears on its own.
Why a transcript tool can't work around it
It's worth being straight about this: when Drive returns a quota error, there is nothing a transcript service can honestly do. The limit is enforced on Google's side, against the file, for every signed-out request. A different server, a different IP, a different country — same answer.
What a tool *can* do is tell you the truth. For a while ours didn't: a Drive quota error and a genuinely broken link produced the same message, which sent people hunting for a problem with their link that didn't exist. That's fixed — a quota error now says so, and points at the copy-or-upload fix instead of asking you to report a bug.
If you see a Drive error that says the platform may have changed, that one *is* worth reporting. If it names the viewing limit, you've got the three options above.
The one thing worth doing in advance
If you're sharing a Drive video you expect to get real traffic — a course module, a webinar recording, a client deliverable — Drive is a file host, not a video host. It has no CDN behaviour for anonymous viewers and this cap is the result. For anything that needs to survive being popular, put it somewhere built for streaming and keep Drive for the master file.