Google Drive web downloads can fail when Chrome blocks the third-party cookies used by Drive’s secure download service. First confirm that downloading is actually permitted, then consider a Drive-specific exception instead of weakening privacy settings for every website.
Check permission before browser settings
Open the file with the intended account and look for a download or security restriction. Owners, shared-drive managers, and organizations can intentionally disable exporting actions. A cookie change cannot appropriately remove those policies.
If Download is available but nothing starts, inspect Chrome’s download list and any visible error. Confirm that the expected file was not already saved to a different folder.
Use the current site-specific controls
Google’s download guide explains that Drive uses third-party cookies to communicate with its download server. In Chrome’s current privacy or site controls, inspect whether those cookies are blocked for Drive and whether a narrow exception is permitted.
Use the current interface’s site-specific setting for Drive rather than copying an old settings path blindly. On a managed browser, ask the administrator if policy controls the setting. Do not remove unrelated site restrictions or enable third-party cookies globally for this one test.
Test and document the result
Retry one authorized file and check the completed local download. If a relevant extension appears involved, use an approved narrow diagnostic approach rather than turning off every security control. Preserve any malware or suspicious-file warning and verify the source with the owner. If the issue persists, record the Chrome version, policy status, exact message, and whether other Drive downloads work. Keep local and cloud originals intact while investigating.
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.