Google Drive Upload Problems: Failed, Stuck, or Slow Uploads

Stuck, failed, and slow uploads almost always trace back to one of four things: a dropped connection with no resume, a daily or per-file size limit, a browser tab losing focus during a long transfer, or ordinary upload bandwidth being the bottleneck. Each has a different fix.

Diagnose before you retry

Retrying blind wastes time on a large file. Check these first, in order:

1. Check Google Workspace's status dashboard for an active incident — this is rarer than people assume, but it happens and it's a five-second check.
2. Check your remaining Drive storage. Uploads fail silently or with a generic error once you're at quota.
3. Open the browser console (or just the browser's own error banner) for a specific error rather than guessing.
4. Confirm the file itself isn't the problem — a corrupted or partially-downloaded source file will fail to upload anywhere, not just Drive.

Common errors and what they mean

Why uploads are slow in the first place

Upload speed is capped by your connection's upload bandwidth, which on most home connections is far lower than download bandwidth — a connection advertised as "200 Mbps" is usually describing download speed, with upload sitting anywhere from 10–20 Mbps unless it's a symmetric fiber plan. A rough example: a 1 GB file over a 10 Mbps upload connection takes roughly 13–14 minutes under ideal conditions, before accounting for any network overhead or contention from other devices on the same connection.

Google's own limits worth knowing

• Google enforces a daily upload cap per account — commonly cited around 750 GB per user per day — intended to prevent abuse of the service. Large batch uploads can hit this on active accounts.
• Individual file size limits exist and are generally well above what most people upload, but very large single files (multi-terabyte) can run into them.
• Uploading many files in parallel from the same account can trigger rate limiting even before you hit a size cap, since Drive throttles concurrent requests per account.

Practical fixes, in order of impact

1. Use a wired connection instead of Wi-Fi for anything over a few hundred MB — Wi-Fi's higher packet loss disproportionately hurts large sustained transfers.
2. Upload files in smaller batches rather than all at once, especially near the daily cap.
3. Keep the browser tab active and the device from sleeping during long uploads — some browsers throttle or suspend background tabs.
4. For transfers you don't control end-to-end — like collecting files from other people — use a tool that resumes automatically after a dropped connection instead of restarting from zero.

When the bottleneck isn't your own connection

If you're the one collecting files from several other people rather than uploading yourself, the failure mode changes: senders on flaky connections drop uploads mid-transfer, several people uploading into the same shared folder at once can compound Drive's per-account rate limits, and there's no visibility into which upload actually finished without checking the folder by hand. Drive File Request handles the sender-side transfer in resumable, ~8 MB chunks with automatic retries, so a dropped connection on their end doesn't mean starting over — and the transfer into your Drive happens as a background job you can see the status of, rather than something that fails silently in someone else's browser tab.

Frequently asked questions