A download stuck in Chrome is usually one of three problems, and the stuck percentage tells you which one. Stuck at 0% and never starting suggests the download can’t even initiate — permissions, antivirus blocking the request, or a network issue. Stuck at 100% and not completing is almost always antivirus scanning the finished file before Chrome can mark it done. Stuck partway through at a consistent percentage points to antivirus triggering at a specific file size. Stuck at a random, varying percentage is a network stability problem. For the bigger picture, our Google Chrome Errors pulls everything together.
The single fastest thing to try first: right-click the stuck download in Chrome’s download bar (or at chrome://downloads) and look for a Resume option. Many Chrome downloads are resumable — clicking Resume picks up exactly where the download left off without starting over. If that’s not available, cancel and retry. For most one-off download failures, that’s the complete fix.
Antivirus Is the Most Common Cause of Stuck Downloads
Windows Defender and third-party antivirus products scan files as they’re downloaded. This creates a dependency: Chrome can’t mark a download as complete until the antivirus scanner releases the file. When the scanner takes too long, encounters a file format it wants to inspect more deeply, or blocks the file outright, the download bar shows the file stuck at 100% with a spinner that never resolves — or stuck at a specific percentage where the scanner triggered.
The test: temporarily disable real-time protection in Windows Security → Virus and threat protection → Real-time protection → toggle Off. Retry the download immediately. If it completes, antivirus was the problem. Re-enable protection right after the download finishes.
The permanent fix (better than disabling protection every time): add your Downloads folder to Windows Defender’s exclusion list. Windows Security → Virus and threat protection → Manage settings → scroll to Exclusions → Add an exclusion → Folder → select your Downloads folder. With the Downloads folder excluded from real-time scanning, Chrome can complete downloads without antivirus holding the file — you can still manually scan downloaded files afterward if you want to verify them before running them.
Stuck at 0%: Permissions and Space
Downloads that don’t start at all usually point to one of two causes: Chrome doesn’t have permission to write to the download folder, or the destination drive doesn’t have enough free space.
Check disk space first — it takes five seconds. Open File Explorer, right-click the C: drive (or whatever drive holds your Downloads folder) → Properties → look at free space. Chrome needs enough room for the entire file plus some overhead. If space is tight, clear some files before retrying.
For permissions: navigate to the Downloads folder in File Explorer, right-click → Properties → Security tab → confirm your user account has Full Control. If not, click Edit → select your account → tick Full Control → Apply. Also try changing the Chrome download location to a different folder: three-dot menu → Settings → Downloads → Change → choose Desktop or Documents. If the download completes in the new location, the original Downloads folder had a permissions issue.
Network Stability for Random Percentage Failures
Large downloads failing at inconsistent, random percentages — 23% one time, 67% the next — indicate packet loss on the network connection. Browsing tolerates packet loss well because individual page elements are small and retry automatically. Large file downloads require a sustained TCP connection throughout, and dropped packets can cause the connection to terminate.
Run this test: open Command Prompt and type ping 8.8.8.8 -n 100. This sends 100 pings and shows any that time out. More than 2–3 timeouts in 100 indicates packet loss. The fix: if on Wi-Fi, switch to a wired Ethernet connection for the duration of the download — Ethernet eliminates wireless packet loss entirely. If on Ethernet and still losing packets, restart the router and retry.
Extensions That Block Downloads
Download manager extensions, ad blockers that intercept download URLs, and privacy tools that strip referrer headers can all prevent downloads from initialising or completing. Test in Chrome Incognito (which disables extensions) — if the download completes in Incognito, an extension is interfering. Go to chrome://extensions, disable all, retry the download in a normal Chrome window. Re-enable extensions one at a time to find the culprit.
Chrome’s Safe Browsing Download Checks
Chrome’s Safe Browsing feature checks download URLs against Google’s database of known malware. When Chrome can’t complete this check — due to network issues, a Safe Browsing service outage, or network filtering blocking Safe Browsing traffic — it may hold the download in a “pending” state indefinitely while it waits for the safety check to complete or time out.
If downloads show “pending” without progress: Settings → Privacy and security → Security → Safe Browsing → switch from “Enhanced protection” to “Standard protection.” Enhanced protection does real-time URL checks that can add latency; Standard protection uses a local list that doesn’t require a live network check for every download. If the download completes after switching, the Safe Browsing real-time check was timing out.
When Chrome’s Downloader Is the Problem
Some servers send download responses with headers that Chrome’s built-in downloader handles incorrectly — unusual Content-Disposition headers, chunked transfer encoding without proper termination, or redirect chains that Chrome’s downloader doesn’t fully resolve. When Chrome’s downloader is the specific issue, the same file downloads successfully through other methods.
Alternatives that bypass Chrome’s downloader: try Microsoft Edge for the specific file — Edge uses a different download implementation. Or use curl, which is built into Windows 11: open Administrator Command Prompt and run curl -L -o "%userprofile%Downloadsfilename.ext" "paste-the-URL-here" — curl handles redirect chains and unusual headers more robustly than Chrome’s downloader. Free Download Manager (free, from fdm.io) is another option that splits downloads into multiple parallel connections and handles interruptions with automatic retry.
Our guide on Chrome download failed network error covers the related “Failed — Network error” message that appears when downloads are actively blocked rather than just stalled. For general Chrome network instability affecting downloads, the DNS not responding guide addresses the DNS failures that sometimes cause download servers to be unreachable. Google’s Chrome documentation covers the download safety check mechanism and how to manage Safe Browsing settings for enterprise deployments where download policies are managed centrally.
Windows Attachment Manager is worth knowing about for downloads that complete successfully but then immediately disappear from the Downloads folder or show as “blocked” when you try to open them. Windows Attachment Manager applies security zone restrictions to files downloaded from the internet — files with certain extensions (particularly executable files like .exe, .msi, .bat) get an “internet zone” mark embedded in the file metadata that causes Windows to block them from running without additional confirmation. This is a Windows security feature rather than a Chrome issue, but it manifests during the download process in confusing ways. If a completed download disappears or won’t open: navigate to the file in File Explorer, right-click → Properties → check for an “Unblock” checkbox near the bottom of the General tab. Ticking Unblock removes the zone restriction and allows the file to run normally.
Downloads stuck because of HTTPS certificate errors on the download server produce a specific symptom: the download never starts (stuck at 0%), Chrome shows no error message in the download bar, but checking chrome://downloads shows “failed” with no further explanation. This happens when Chrome encounters a certificate problem with the download server’s domain — which may be different from the main site’s domain if the file is hosted on a CDN or file storage service. The diagnostic: try the download URL directly in the address bar instead of clicking the download link. If Chrome shows a certificate error on that URL, the download server’s SSL certificate is the issue. The fix lies with the site owner rather than Chrome settings — but temporarily disabling Chrome’s Safe Browsing Enhanced Protection (which performs stricter certificate checks) may allow the download to proceed if the certificate is technically valid but flagged by enhanced scanning.
Parallel download acceleration is a Chrome feature that can sometimes cause stuck downloads on servers that limit concurrent connections. Chrome’s experimental parallel download feature splits large files into chunks and downloads them simultaneously. When a server enforces connection limits (common on file hosting sites, corporate file servers, and bandwidth-managed CDNs), Chrome’s multiple simultaneous connections for the same file can all be rate-limited or blocked simultaneously, causing the download to stall. The fix: go to chrome://flags/#enable-parallel-downloading and set it to “Disabled.” This forces Chrome to use a single connection for downloads, which works with connection-limited servers. Note that parallel downloading genuinely improves download speed on unlimited-connection servers, so re-enable it after resolving the stuck download issue if your typical download sources support it.
Corporate proxy servers with download size limits cause Chrome downloads to stop at a consistent file size regardless of how much of the file has been downloaded. Some corporate web gateways enforce maximum file download sizes (commonly 100MB, 500MB, or 1GB limits) as part of data loss prevention or bandwidth management policies. If downloads consistently fail after reaching the same approximate size, a proxy size limit is the likely cause. Check with IT about the proxy configuration — they may be able to whitelist specific download domains, increase the limit for your account, or provide an alternative download path for large files.
Download directory on a network share (NAS, mapped drive, or UNC path) is a frequent but underexplored cause of Chrome download failures. When Chrome’s configured download location is a network path, any instability in the network drive connection — brief timeouts, permission changes, the NAS going to sleep — appears to Chrome as a network error for the download itself, even though Chrome was successfully downloading the file from the internet. Chrome can’t distinguish between a network error connecting to the download server versus a network error writing to the destination drive. If Chrome downloads are failing intermittently and the download destination is a network location, changing the download folder to a local path (Settings → Downloads → Change → select a local folder) and retrying confirms whether the network destination is the issue.
Server-side download throttling is distinct from network packet loss and produces a specific symptom: the download starts and progresses, but slows dramatically after a certain point and eventually stalls. Free tiers of file hosting services (Dropbox, Google Drive public shares, MediaFire, Mega) often apply per-file bandwidth limits for unauthenticated downloads. Once the per-file bandwidth allowance is exhausted, the download throttles to near-zero and eventually times out. Signing into the hosting service with an account, using a different download mirror, or downloading at off-peak hours (when the bandwidth allowance has reset) are the practical fixes for server-side throttling — Chrome settings changes won’t help because the limitation is entirely server-controlled.
Chrome’s download shelf and download manager (chrome://downloads) provide useful diagnostic information that the basic download bar doesn’t show. When a download fails, chrome://downloads usually shows a more specific failure reason than the small “Failed” text in the download bar — “Server disconnected,” “Insufficient permissions,” “Virus scan failed,” and other specific messages appear on the detailed download page. Clicking “Show more” or hovering over the failed download entry in chrome://downloads often reveals this additional context. The specific failure message directly suggests the fix: “Virus scan failed” confirms antivirus is the issue, “Insufficient permissions” confirms the folder permissions problem, “Network disconnected” confirms a connection instability, and “File too large for filesystem” (relevant for FAT32-formatted drives) indicates the destination drive can’t store files larger than 4GB.
4GB file size limitation on FAT32 drives is a specific cause of Chrome download failures that’s easy to overlook. External USB drives and older flash drives are often formatted as FAT32, which has a maximum individual file size of 4GB. Downloading a file larger than 4GB to a FAT32 drive will fail when the download reaches the 4GB mark — Chrome writes 4GB successfully and then fails because FAT32 can’t store the remainder. The fix is either downloading to a local NTFS drive (C: drive or any modern internal drive), reformatting the destination drive to exFAT (which has no practical file size limit and is compatible with most operating systems), or using a file split tool to break the download into chunks smaller than 4GB before transferring to the FAT32 drive.
Resume capability in Chrome depends on both Chrome’s implementation and the server’s support for HTTP range requests. When a download can be resumed (most modern download servers support this), Chrome sends a range request asking for the file starting at the byte position where the previous download left off. When a server doesn’t support range requests, Chrome has to start from the beginning — there’s no resume, only restart. Chrome indicates this in the download bar: if “Resume” appears as an option after a failed download, the server supports range requests and resumption will work. If “Resume” is absent and only “Retry” appears, the server doesn’t support range requests and Chrome will download from byte zero. For large files from servers without range request support, a download manager like Free Download Manager that can implement its own resume mechanisms is worth using — it splits the download into smaller chunks that can be individually retried even when the server doesn’t support standard HTTP range requests. Our guide on Google Drive Not Syncing covers an adjacent issue.
