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:
- 01Check 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.
- 02Check your remaining Drive storage. Uploads fail silently or with a generic error once you're at quota.
- 03Open the browser console (or just the browser's own error banner) for a specific error rather than guessing.
- 04Confirm 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
| Symptom | Likely cause | Fix |
|---|---|---|
| Stuck at 99% indefinitely | Server-side processing (virus scan, indexing) on a large file | Wait it out on files over a few GB; if it never completes, retry |
| "Upload failed — network error" | Connection dropped mid-transfer, no resume | Retry on a stabler connection; prefer wired over Wi-Fi for large files |
| "Storage quota exceeded" | Account is at its storage limit | Free up space or upgrade storage before retrying |
| Error 403 | Permission issue on the destination folder, or a script's OAuth token expired | Re-check folder sharing settings or re-authorize the script |
| Error 500 / 503 | Temporary server-side issue on Google's end | Wait a few minutes and retry — usually resolves on its own |
| Upload silently stops with no error | Browser tab was backgrounded or the device slept mid-upload | Keep the tab active and the device awake for large transfers |
| Upload button does nothing, or the picker never opens | An ad blocker or privacy extension is blocking Drive's upload frame | Retry in a private window with extensions off, then re-enable them one at a time |
| "Waiting to upload" that never advances | Almost always the mobile app: a corrupted app cache, or a queue that never started | Force stop the Drive app, clear its cache, reopen it; in a browser, clear the site cache and re-add the files |
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.
- A single file can be up to 5 TB, provided your account has the storage to hold it — high enough that almost nothing hits it, but worth knowing before you blame the network for a failure on a very large file.
- 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.
When it fails on the Drive mobile app
Phone uploads fail for reasons that have nothing to do with the ones above, and every desktop fix on this page is useless against them. Four causes cover almost all of it:
- 01Battery saver or background app limits suspended the app the moment you switched away from it. A phone upload is not a background job — leave the Drive app in the foreground, screen on, until it finishes.
- 02The phone handed the connection from Wi-Fi to mobile data (or back) mid-transfer, which drops the upload rather than resuming it. Turn the other radio off for the duration of a large upload.
- 03The Drive app is out of date. Uploads are one of the first things to break on an old build; update it before spending time on anything else.
- 04The device is out of local storage. Drive stages the file before sending it, so a full phone fails an upload that has nothing to do with your Drive quota.
When it is Drive for desktop, not the browser
The desktop sync client fails quietly by design — it retries in the background and shows nothing but a paused icon. If files you dropped into a synced folder never appeared online, check in this order: whether sync is paused (the menu bar or system tray icon says so), whether that folder is actually included in the folders you chose to sync, whether a single oversized or open-and-locked file is blocking the queue behind it, and whether the account signed into the client is the account you are looking at in the browser. Quitting and relaunching the client clears a stuck queue more reliably than waiting does.
Practical fixes, in order of impact
- 01Use 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.
- 02Upload files in smaller batches rather than all at once, especially near the daily cap.
- 03Keep the browser tab active and the device from sleeping during long uploads — some browsers throttle or suspend background tabs.
- 04For 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. A file request link for Google Drive does this on the sender's side.
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 — and the options for collecting files from clients matter more than any single upload setting: 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.