When a Google Drive upload hangs at "Less than a minute remaining" or 99%, the file data has already been uploaded, but your browser is failing to receive Google's final HTTP 200/201 closure handshake. To fix it immediately: do not close the tab. Open a new browser tab, go to Google Drive, check the target folder, and refresh. In 80% of cases, the file is already finalized. If it has truly hung, clear your browser cache, disable aggressive antivirus SSL inspection, or use SaveInDrive Remote Upload (https://saveindrive.com) to bypass browser socket timeouts completely.
You have been waiting for an hour while a crucial 18GB client video, database dump, or software build uploads to Google Drive. The progress circle slowly completes, reaches 99%, and displays the agonizing status message: "Less than a minute remaining..."
Ten minutes pass. Then thirty. The progress circle remains frozen. If you cancel the upload, you waste hours of time and gigabytes of internet bandwidth. If you leave it alone, it sits indefinitely without completing.
Why does this happen so consistently across Chrome, Edge, Safari, and Firefox? In this comprehensive troubleshooting guide, we dissect the exact technical cause behind the 99% upload freeze and provide actionable fixes to rescue your upload right now.
The Technical Culprit: The "Final Handshake" Failure
When you upload a file through Google Drive's web interface, Google divides the upload into two distinct phases:
- Data Transmission Phase: Your browser transmits binary data packets across WebSocket or HTTPS chunks to Google's upload servers (
upload.video.google.comorwww.googleapis.com/upload/drive/v3/files). This is the portion represented by the progress circle. - Finalization & Checksum Phase: Once 100% of the bytes arrive at Google's data center, Google's backend runs an MD5 cryptographic checksum on the assembled file, verifies metadata, allocates storage quota in your account, and sends an HTTP 200 OK / HTTP 201 Created response packet back to your browser.
The freeze at "Less than a minute remaining" occurs when the data has successfully reached Google, but the return confirmation packet is blocked or dropped before your browser can process it. Common reasons include browser memory exhaustion, third-party Chrome extensions interrupting WebSocket connections, or local antivirus firewalls scanning the outgoing buffer.
Immediate Fix 1: The "Ghost Upload" Check (Do Not Cancel!)
Before you do anything drastic, check if your upload has already succeeded on Google's servers:
- Keep the uploading tab open—do not refresh or close it!
- Open a brand-new tab in your browser.
- Navigate to
https://drive.google.com. - Open the destination folder where your file was being uploaded.
- Sort files by "Last modified" descending.
In roughly 8 out of 10 cases, you will find your file sitting safely in the folder with its full file size and correct name! The browser upload UI simply failed to update its visual status. If you see the file in your other tab, you can safely close the stuck tab.
Immediate Fix 2: Flush Browser Network Sockets Without Killing the Tab
If the file is not visible in the other tab, your browser's internal network socket may be in a deadlocked state. In Google Chrome or Microsoft Edge, you can force the browser to reset its network socket pool without terminating active tabs:
- Open a new tab and paste the following internal URL:
chrome://net-internals/#sockets(oredge://net-internals/#socketsfor Edge). - Click the Flush socket pools button.
- Switch back to your Google Drive uploading tab. In many instances, clearing the socket deadlock immediately allows the pending HTTP 200 handshake to complete, turning the circle into a green checkmark!
Immediate Fix 3: Disable Hardware Acceleration & Third-Party Extensions
Certain Chrome extensions—particularly ad blockers, VPN extensions, and download managers—inspect outgoing HTTP traffic. When a file upload reaches several gigabytes, the extension's background memory script can crash, blocking the final closure response.
- Temporarily disable extensions like uBlock Origin, Privacy Badger, or browser VPNs.
- Go to Chrome Settings > System and toggle off "Use graphics acceleration when available". Browser GPU memory leaks are a documented cause of frozen long-running uploads on Windows 11 and macOS.
Immediate Fix 4: Bypass Browser WebSockets via SaveInDrive Remote Upload
If you frequently upload large files (over 5GB) and suffer from repeated browser freezes, your internet service provider (ISP) or local Wi-Fi router may be dropping persistent TCP connections during long idle states.
The definitive solution is to bypass your browser's fragile upload engine entirely. If your file is hosted on another server, a cloud seedbox, or a direct web link, you can use SaveInDrive Remote Upload:
Paste the File's Direct Web Link into SaveInDrive
Instead of downloading the file to your computer and manually re-uploading through Chrome, copy the direct download link (e.g. from WeTransfer, Dropbox, GitHub, or any remote server).
Stream Directly Into Google Drive via Data Center Fibers
SaveInDrive executes the upload from high-bandwidth cloud servers directly into your Google Drive via Google's official Resumable Upload API. Because the transfer runs server-to-server, there is zero risk of browser crashes, Wi-Fi drops, or socket freezes.
Security software such as Avast, Kaspersky, Bitdefender, and AVG include a feature named "HTTPS Scanning" or "Web Shield". These utilities act as a local man-in-the-middle proxy, intercepting and buffering all outgoing SSL traffic. For uploads over 10GB, the antivirus cache often runs out of virtual memory, freezing the upload at 99%. Temporarily disabling HTTPS Web Shield during large file transfers resolves the issue permanently.
Troubleshooting Checklist: Preventing Upload Freezes
| Action Item | Why It Helps | Recommended For |
|---|---|---|
| Check Google Drive in a New Tab | Verifies if file already finalized in background | Always (First Step) |
| Flush Sockets (chrome://net-internals) | Clears frozen TCP socket deadlocks | Chrome & Edge Users |
| Disable Antivirus Web Shield | Stops local buffer memory exhaustion | Windows Users with 3rd-party Antivirus |
| Use Google Drive for Desktop | Syncs via background OS daemon instead of browser | Daily Heavy Uploaders |
| Use SaveInDrive Cloud Transfer | Transfers server-to-server with zero local Wi-Fi dependency | Files over 5GB & Remote Links |
Frequently Asked Questions (FAQ)
Will pausing and resuming the upload fix the 99% freeze?
Unfortunately, no. Clicking pause on a browser upload that is already hung at the finalization stage usually breaks the socket connection completely, resulting in an "Upload Failed" error. Always check a second tab first before touching the pause/cancel button.
Why does this happen more frequently on large files than small files?
Google takes significantly longer to compute the MD5 integrity checksum for a 20GB file across its distributed storage chunks than for a 50MB PDF. If that checksum verification takes longer than your browser's HTTP timeout window (typically 60 to 120 seconds), the browser assumes the connection died, even though Google is still processing the file.
Can I resume a failed Google Drive upload without starting over?
Google Drive's web interface does not support resuming failed browser uploads from scratch. However, if you use the official Google Drive for Desktop application or API-based tools like SaveInDrive, transfers utilize chunked resumable endpoints that pick up exactly where they left off.
Does uploading in Incognito Mode prevent this error?
Yes, frequently. Because Incognito mode disables all third-party extensions and runs with a clean memory cache, it prevents extension-related WebSocket crashes during the final upload handshake.
Final Advice
The next time your Google Drive upload freezes at "Less than a minute remaining", resist the urge to smash the cancel button. Check your destination folder in a separate tab, flush your browser's network sockets, and consider switching to robust server-to-server streaming solutions like SaveInDrive for your multi-gigabyte file transfers.
📚 Recommended In-Depth Cloud Guides:
- Google Drive Upload Failed or Server Error? 8 Proven Fixes (2026) — Google Drive (8 min read)
- How to Download Large Files When Google Drive Can't Scan for Viruses — Google Drive (8 min read)
- Google Drive 750 GB Daily Upload Limit: How It Works & How to Bypass It — Google Drive (11 min read)
- Why Is Google Drive Download So Slow? 9 Fixes to Get Maximum Speed (2026) — Google Drive (11 min read)
