Google Drive video blurry when shared with a client.
Drive caps playback at 1920 x 1080.

Read where the sentence sits, because the placement matters. It is published under playback, on the page that tells you how to play a video in Drive. It is not published about storage. On the separate page about what Drive can hold, Google states that files other than Docs, Sheets, Slides and Sites can be up to 5 TB. Drive is a file locker with a player attached, and the ceiling is written against the player.

That distinction is the practical difference between a bad afternoon and a fixed delivery. The thing your client pressed play on is capped. The thing they would get by clicking download is the file you put there. When a client says the video looks soft, the first question is not about your export settings. It is whether they watched it or downloaded it.

There is a second symptom that gets reported as the same problem. Google publishes the message “Video is still processing. Try again later,” and says it means the video is not yet ready to be played, adding that for a large file “it may take awhile before your video is ready.” A client who opens the link within a few minutes of your upload may get that instead of a film. Google does not publish how long processing takes, in minutes, in minutes per gigabyte, or in any other unit, so there is no honest number to give them.

The right-hand column is the reason this page exists. A download quota is the single most repeated claim about Drive video, and it is not in Google’s documentation. Neither is the 720p figure that gets quoted at filmmakers constantly. Publishing them would make this page rank alongside everyone else and would also make it wrong, and a client who is told a number that turns out to be invented stops believing the rest of the email.

What you can say to a client with a straight face is short: Drive plays video at up to 1920 x 1080, the file in the folder is the file you uploaded, and the download is how you get at it.

The mechanical difference is small to describe and large in effect. There is no encode step in our path, at upload or at playback: the browser cuts the file into parts, the parts are stored, and the player is handed that same stored object. The Terms put it plainly, that the exact file you upload is the file your viewers receive. Nothing is prepared, so there is nothing to wait for and nothing that could come out softer than what went in.

The honest caveat is on the viewer’s side rather than ours. We enforce no codec allowlist, so whether a given file plays in a given browser is decided by that browser and that hardware. H.264, HEVC and AV1 in MP4 or MOV are what we tell members to upload for browser playback. ProRes 422, ProRes 4444 and DNxHR are hosted for client download rather than streamed, so the practical shape of a delivery is a high-bitrate viewing export on the page with the master behind the download switch.

Where the ceiling does cost you is narrow and specific: any moment a client forms a judgement from what is on screen. A grade approval, a compression check, a shot the colourist reworked, a delivery a festival programmer will watch once. In those moments a capped playback is not a convenience, it is a wrong answer presented confidently, and it usually surfaces as an argument about your work rather than about the tool.

One more thing worth saying plainly, since this page is partly about not inventing numbers. Upgrading your Google storage does not lift the playback ceiling. Google states the 1920 x 1080 figure once and does not attach it to a tier, and the Google One plans it does publish buy storage shared across Photos, Drive and Gmail. On the Canadian storefront the 100 GB plan is listed at CA$2.79 a month, which is a fair price for storage and not a price for picture quality. If the picture is the problem, more gigabytes are not the fix.