Compress Video for Google Drive Before Uploading
By Mark Fulton · 2026-09-10 · 10 min read
Google Drive will not reject your video. That is the part almost every page answering this question gets wrong.
Drive stores single files up to 5 TB, so file size is almost never the reason to compress before uploading. The three real reasons are upload time, which is directly proportional to the number of bytes you send; storage quota, which on a free Google account is 15 GB shared with Gmail and Google Photos; and playback, because Drive builds its own transcoded copy of your video for its in-browser player and caps that copy at 1920 x 1080. What a viewer streams inside Drive is never the file you uploaded. Compressing on purpose beforehand means you choose the quality of the version people actually watch, and the untouched original stays on your own disk.
That last point is the one that surprises people. You upload a crisp 4K export, open it in Drive to check, and it looks soft. Nothing has damaged your file. You are simply watching a different one.
Does Google Drive have a video size limit?
There is a ceiling, and it is high enough that most people will never meet it. Every figure below was read off Google's own pages on 10 September 2026, because these change and the date matters more than the number.
| What | The limit | Google's own page |
|---|---|---|
| Any single file that is not converted to a Google format | Up to 5 TB | Files you can store in Google Drive |
| What you can actually store | Whatever quota you have left; a video cannot exceed your available storage | Store and play video in Google Drive |
| Free personal account storage | 15 GB, shared across Drive, Gmail and Google Photos | How Google storage works |
| Upload and copy in any 24 hours, Google Workspace | 750 GB per user, after which uploads stop until the window resets | Storage and upload limits for Google Workspace |
| Playback resolution in Drive's own player | Maximum 1920 x 1080 | Store and play video in Google Drive |
| Minimum file size for playback | 4 KB | Store and play video in Google Drive |
Two of those rows do the real work. The 15 GB is shared, so a folder of phone videos competes with your inbox, and Google's own documentation warns that content can be removed after two years over quota. And the 1920 x 1080 is a playback ceiling, not a storage ceiling. Drive will happily hold your 4K master. It just will not stream it to anyone at 4K.
Why does a Drive video look worse than the file you uploaded?
Because after an upload there are two videos, not one.
The first is your file, stored byte for byte. Download it again and you get exactly what you sent, which is why Drive is a perfectly good place to keep an original.
The second is what Drive makes for itself. To play a video inside a browser tab, Drive needs a stream it can deliver progressively in a format the browser can decode, so it transcodes a copy at upload time. That copy is capped at 1920 x 1080 per Google's own page, and its bitrate is chosen by Google, not by you. There is no setting for it anywhere in Drive. That is also what the "Video is still processing. Try again later." message refers to: the renditions are not built yet. Google notes that a video can start playing for you while it is still processing for other devices and for the people you shared it with.
So the chain a viewer experiences is: your encode, then Google's re-encode of your encode, then their screen. Every compression pass after the first works on a picture that already has compression artifacts baked in, and it spends bits preserving those artifacts. That is the generational loss problem covered in our post on compressing without losing quality, and it is the reason a clean, moderate export beats a bloated one here. Hand Drive's encoder a tidy 1080p file and it has very little damage left to do. Hand it a noisy, over-sharpened, high frame rate 4K file and it will make choices you would not have made.
One more source of confusion worth clearing up: Google Photos is a different product with a different policy. Photos gives you explicit backup quality tiers, and Google's documentation on backup quality says Storage saver resizes video above 1080p down to 1080p, while Express resizes anything above 480p down to 480p. Drive does not do that to your stored file. Most of the "Google compressed my video" folklore online is really about Photos.
What should you compress to before uploading?
The answer depends entirely on how the person on the other end is going to consume it. This is the decision, laid out:
| How the viewer gets it | What Drive does with your file | Compress first? | Sensible export |
|---|---|---|---|
| Streams the preview in a browser | Serves its own transcode, 1080p ceiling | Yes | H.264 in an MP4, 1080p or lower, moderate CRF, AAC audio |
| Clicks Download and opens it locally | Serves your exact bytes | Only to spare their download time | Keep it high quality, a low CRF |
| Watches it embedded in Slides or a Google Site | The preview pipeline again | Yes | Same as the streaming row |
| Will re-edit or grade the footage | Nothing useful | No | Send the master, or a link to it |
| Nobody watches it, it is an archive | Nothing | Only if quota is tight | Compress if you are near 15 GB, otherwise keep the master |
| A whole shoot being backed up in bulk | Nothing | Yes, for the upload window | Whatever gets the batch under the daily cap and finishes overnight |
Three notes on filling that in.
Resolution first, then quality. If the ceiling is 1080p, exporting 4K buys the streaming viewer nothing and costs you upload time and quota. Downscale to 1080 and every bit you then spend goes into pixels that will actually be shown.
CRF is the quality control, not a size slider. Constant Rate Factor asks the encoder to hold a consistent perceived quality and spend whatever bits each scene needs. It is documented as the crf option on libx264 in the FFmpeg codec reference, and it is what sits behind the high, medium and small presets in most tools, including the three presets in our compressor, which map to CRF 23, 28 and 32. Lower number, more bits, larger file. For something a viewer will stream in Drive, the moderate end is the right place to sit, because Drive is about to re-encode it anyway. If you need to hit a specific number of megabytes rather than a quality level, that is a different job and the arithmetic is in our post on compressing to an exact size.
Check the codec, not just the extension. Google lists the formats its player handles, and for MP4, 3GPP and MOV it names h264 and MPEG-4 video with AAC audio. H.265 and HEVC do not appear on that list. Modern iPhones and many Android phones record HEVC by default, which means a phone video can upload and store perfectly while behaving oddly in the preview. If you are not sure what is inside your file, converting it to an H.264 MP4 removes the question. MDN's guide to web video codecs is the reference for which codec plays where, and H.264 remains the one with the fewest exceptions.
How do you keep a high-quality master?
Keep two files and be deliberate about which one goes where.
The master is your camera or editor output, untouched, living on your own disk or an external drive. The delivery copy is the compressed 1080p H.264 MP4 you upload. Name them so you can tell them apart at a glance six months from now, because the failure mode here is not dramatic. It is compressing the master in place, uploading only that, deleting the original to save room, and then discovering a year later that the best copy you have is the one Drive was going to re-encode anyway.
If Drive is your backup, upload the master too, in its own folder, and accept the quota cost. Downloading it later returns the original bytes. What you cannot do is recover the master from a preview stream, because that stream was never a file you own.
And do not compress the same clip twice for no reason. If you already exported a reasonable H.264 MP4 out of your editor, that is your delivery copy. Running it through another encode adds a generation of loss and usually saves less than you expect.
How do you cut upload time in half?
By uploading half as many bytes. Upload time is close to linear in file size, so this is the one part of the job where the arithmetic is completely predictable.
One gigabyte is 8,192 megabits. Divide by your upstream speed, which on most home connections is a fraction of the download speed you pay attention to:
| Upstream speed | Theoretical minutes per GB |
|---|---|
| 5 Mbps | about 27 |
| 10 Mbps | about 14 |
| 20 Mbps | about 7 |
| 40 Mbps | about 3.5 |
| 100 Mbps | about 1.4 |
Those are floors, not promises. Real transfers run slower because of protocol overhead, retries and whatever else on your network is competing for the same pipe. But the shape holds: halve the file, halve the wait. A 6 GB screen recording cut to 1.5 GB on a 10 Mbps upstream connection goes from roughly an hour and a half to roughly twenty minutes, and the encode that got it there runs on your own machine while nothing is being sent anywhere.
That trade is worth making whenever the upload is long and the connection is slow. It is not worth making for a 40 MB clip on fast fibre, where the encode costs more of your attention than the upload does.
Frequently asked questions
Does Google Drive compress videos?
Not your stored file. Drive keeps the bytes you uploaded and hands them back when someone downloads it. What Drive does compress is the separate copy it builds for its own in-browser player, which Google's help page caps at a maximum playback resolution of 1920 x 1080. Google Photos is the product that genuinely re-encodes what it stores, on the Storage saver and Express tiers.
Why is my Drive video still processing?
The renditions Drive uses for playback have not finished being built. Google's guidance is that a large file can take a while and to try again later. The upload itself is already complete at that point, and sharing the file works even while the message shows, though the people you shared it with may see the same notice until processing finishes. A smaller, already efficient file gives Drive less work to do.
What is the best format for Drive playback?
An MP4 containing H.264 video and AAC audio, at 1080p or lower. That combination sits squarely inside the format list Google publishes for its player, matches the 1920 x 1080 playback ceiling, and is the codec with the widest support across browsers, phones and TVs. MOV files with the same H.264 and AAC contents are on Google's list too, but MP4 travels better everywhere else.
Does compressing before upload save quota?
Yes, and it is a direct saving. Only the files you own count against your 15 GB, and what counts is the size of the file you uploaded, so a 1.5 GB delivery copy uses a quarter of the quota a 6 GB master would. The transcoded preview Drive generates is Google's own overhead and not something you are billed storage for. If quota is the pressure you are under, compressing before upload is the lever, not clearing your trash twice a year.
If the version people watch matters, decide what it looks like before Google does. Compress the clip in the browser first: the file is read into memory and encoded on your own CPU, nothing is uploaded, and there is no account or queue in the way. The free tier handles files up to 200 MB and puts a small mark in the corner of video exports. Pro removes the mark, lifts the cap to whatever your browser's memory allows, and adds compression to an exact target size, at $4 a month billed $24 every six months, or $79 once. Either way the upload is shorter, and the playback version is one you chose.