A Google Drive upload may stop because of the account, the destination folder, the local file or the connection. Retrying the same large file does not tell you which one failed.
Upload one small, ordinary file to your own My Drive first. If that works, compare it with the original file and destination; if it does not, focus on the browser, storage and connection before changing folder permissions.
Keep the original until the uploaded copy opens correctly. Seeing a filename in Drive does not by itself prove the transfer is complete.
Guide reviewed: October 8, 2026. Interface labels may vary by version, account and device.
Use one small upload to narrow the failure
| Comparison | What it narrows down | Next check |
|---|---|---|
| Small file works, large file stalls | Size or sustained transfer | File limits and connection stability |
| My Drive works, shared folder fails | Destination access or organization rule | Folder permission and shared-drive restrictions |
| File cannot open locally | Placeholder or unfinished source file | Download/save a stable local copy |
| Browser works, desktop sync fails | Desktop synchronization | App’s exact error and file availability |
| Clean browser works | Session or extension | Test the relevant browser setting individually |
A small test can narrow the problem
- Confirm the active Google account.
- Open My Drive and use New → File upload for a small harmless file.
- Wait for completion and open that file.
- Try the intended destination with a similarly small file if you have permission.
- Record whether failure depends on the file, destination or upload method.
Try a small, ordinary file in your own My Drive. If that succeeds, compare it with the failed upload: size, local location, destination folder and browser session are all useful differences.
For example, a small PDF that uploads successfully while a large video repeatedly stalls suggests a different investigation from every file failing immediately. The first pattern may involve sustained connection quality or limits; the second may involve access, storage or the session.
Keep a short note of the exact error and when it occurs. An error before transfer begins is different from a connection failure near completion, and that distinction helps when you contact support.
Check the account and destination together
Confirm which Google account is active and how much storage it has available. A browser with several signed-in accounts can make it easy to inspect the storage of one account while uploading through another.
A folder shared with you is not necessarily a folder you can upload into. Check your permission and the destination’s rules. Shared drives and organization-managed storage may have different restrictions from a personal My Drive folder.
If uploading to your own folder works but the shared destination fails, give the folder owner or administrator that comparison. It is more useful than repeatedly changing the local file.
Make sure the local file is available
Example: a file visible in another cloud service’s folder may be an online-only placeholder. Open it locally and confirm its contents are downloaded before uploading to Drive. Finish any editing and save a stable copy so the source does not change during transfer.
Files being written by another app can also change during transfer. Finish and save the work, then upload a stable copy. Avoid replacing the only original while experimenting with another format or a compressed version.
File-size and upload limits depend on the operation and account environment. Uploading a file and converting it to a Google document are different operations. Check Google’s current limits for the one you are attempting instead of treating one number as a limit for every file type.
Separate browser trouble from connection trouble
A fresh session in a supported browser can help identify whether stored site data or an extension is involved. If that session succeeds, return to the usual browser and test the likely cause individually.
A second trusted network provides a separate comparison. Large uploads need a connection that stays available for the whole transfer; loading a small webpage normally does not establish that the connection will remain stable for a video upload.
On a work or school network, restrictions may be intentional. Ask the administrator about the failed transfer rather than broadly disabling security software. The destination, file size and failure time provide useful context without exposing the file’s private contents.
Drive for desktop needs its own checks
If the browser upload works but Drive for desktop does not synchronize, inspect the desktop app’s reported error. Account selection, local disk space, file access and paused synchronization may explain the difference.
Before unlinking accounts or removing local folders, understand whether the files are mirrored, streamed or available only locally. Changing those arrangements without checking can make it harder to know which copy is complete.
Confirm the result before retrying again
| File | Meaningful completion check |
|---|---|
| Document | Open it and check the last page |
| Spreadsheet | Confirm expected sheets and a known final row |
| Video | Check playback near the end after processing finishes |
| Archive | Check its expected size and accessible contents |
Once the upload reports completion, open the destination file and check a meaningful part of it. For a document, that might be its last page; for a spreadsheet, its expected sheets; for a video, playback near the end.
Repeated retries can create duplicates. Compare filenames and contents before removing any extra copy. If the problem remains, the most useful support summary includes the upload method, destination type, file size, exact error and whether the small-file test succeeded.
Google Drive references and follow-up checks
Keep the failed attempt distinguishable
Record method, account, destination type, file size, error and result of the small-file comparison. Check duplicates before retrying or removing copies. Google’s Drive troubleshooting guide covers browser and connection checks; organization-managed destinations may also require an administrator.