When a user reports that uploading files through the OneDrive website works in Microsoft Edge but fails in Google Chrome, the issue is almost always caused by a browser-specific setting or extension conflict. Chrome’s strict privacy features, third-party cookie blocking, or an interfering extension can break the upload dialog. This article provides a checklist for IT administrators to diagnose and resolve Chrome-only upload failures in OneDrive for Business.
Key Takeaways: Diagnosing Chrome Upload Failure in OneDrive
- Chrome > Settings > Privacy and security > Third-party cookies: Blocking third-party cookies breaks the OneDrive upload dialog; set to “Allow all cookies” or add office.com and sharepoint.com to allowed sites.
- Chrome > Extensions > Manage extensions: Ad blockers, privacy tools, and script blockers like uBlock Origin or Ghostery can block the upload script; test with all extensions disabled.
- OneDrive settings > Sync and backup > Advanced settings > Files On-Demand: Enabling Files On-Demand can reduce browser upload issues by offloading large file handling to the sync client.
Why OneDrive Web Upload Fails Only in Chrome
The OneDrive web interface uses a combination of JavaScript, cookies, and browser storage to open the file picker and initiate the upload. Chrome enforces stricter defaults for third-party cookies and storage partitioning than Edge or Firefox. Starting with Chrome 80, the SameSite cookie attribute defaults to Lax, which can prevent the OneDrive upload dialog from receiving the authentication token it needs. Additionally, Chrome’s built-in pop-up blocker or an installed extension may intercept the file picker request. The result is a non-functional upload button or a dialog that opens but fails silently.
Cookie Blocking and Storage Partitioning
OneDrive relies on cross-site cookies to maintain the session when the upload dialog opens. Chrome’s “Block third-party cookies” setting prevents these cookies from being set. When the user clicks Upload, the dialog may appear blank, fail to open, or close immediately. Storage partitioning, introduced in Chrome 115, isolates storage per-site, which can break the OneDrive upload process if the user is authenticated via a federated identity provider.
Extension Conflicts
Extensions that block scripts, ads, or trackers often remove the JavaScript files that power the OneDrive file picker. Extensions like uBlock Origin, Ghostery, Privacy Badger, and NoScript are common culprits. Even extensions that modify the user agent string or enforce HTTPS-only mode can interfere with the upload endpoint.
Administrator Checklist to Diagnose and Fix Chrome Upload Failure
Follow these steps in order. Test after each step to isolate the cause.
- Check Chrome cookie settings
Open Chrome, go to Settings > Privacy and security > Third-party cookies. If the setting is “Block third-party cookies” or “Block third-party cookies in Incognito,” change it to “Allow all cookies.” Alternatively, add the following sites to the allowed list: login.microsoftonline.com, sharepoint.com, onedrive.com, and office.com. Click the Add button next to “Sites that can always use cookies.” Apply the change and restart Chrome. - Disable all extensions
Type chrome://extensions in the address bar. Toggle off the switch at the top of each extension to disable it. Do not remove extensions yet. Restart Chrome and test the upload. If the upload works, re-enable extensions one by one to find the conflict. - Clear Chrome cache and cookies for Microsoft domains
Go to Settings > Privacy and security > Clear browsing data. Select “All time” for the time range. Check “Cookies and other site data” and “Cached images and files.” Click “Clear data.” Then visit the OneDrive site and sign in again. This removes corrupted session data that may block uploads. - Disable Chrome pop-up blocker for Microsoft sites
Go to Settings > Privacy and security > Site settings > Pop-ups and redirects. Change the default behavior to “Sites can send pop-ups and use redirects.” Alternatively, add sharepoint.com and office.com to the “Allowed to send pop-ups” list. - Verify Chrome is up to date
Type chrome://settings/help in the address bar. Chrome will automatically check for updates. If an update is available, click “Relaunch.” Outdated Chrome versions may have bugs that affect the OneDrive upload dialog. - Test with Chrome Incognito mode
Open an Incognito window (Ctrl+Shift+N) and sign in to OneDrive. Incognito mode disables extensions and uses default cookie settings. If the upload works in Incognito, the cause is either an extension or a corrupted profile. If it fails in Incognito, the cause is a Chrome setting or a network issue. - Check Group Policy or managed browser settings
If the user is on a managed device, an IT policy may enforce cookie blocking or extension blacklists. Go to chrome://policy in Chrome to view active policies. Look for policies like “BlockThirdPartyCookies” or “DefaultPopupsSetting.” Contact your IT administrator to adjust these policies if needed.
If OneDrive Still Has Issues After the Main Fix
Upload hangs at 99 percent in Chrome
A stalled upload at 99 percent is often caused by a large file size or a file with special characters in the name. OneDrive for Business has a file size limit of 250 GB per file. Files with names containing ~ ” # % & : < > ? / \ { | } may fail. Rename the file to remove special characters and try again.
Upload button is grayed out or missing in Chrome
A missing upload button usually indicates that the user does not have edit permissions for the target folder. Check the folder permissions in the SharePoint admin center. The user must have at least Contribute permission. Also verify that the folder is not set to read-only at the document library level.
OneDrive page shows “Something went wrong” in Chrome
This generic error in Chrome can be caused by an incompatible Chrome flag. Type chrome://flags in the address bar and search for “Partitioned cookies” or “Storage partitioning.” Set any flag related to partitioned storage to Disabled. Restart Chrome and test the upload again.
OneDrive Web Upload vs Desktop Sync Client: Key Differences for Chrome Users
| Item | OneDrive Web Upload in Chrome | OneDrive Desktop Sync Client |
|---|---|---|
| File size limit | 250 GB per file | 250 GB per file |
| File name restrictions | Blocks ~ ” # % & : < > ? / \ { | } | Same restrictions |
| Browser dependency | Requires cookies and JavaScript enabled | No browser dependency |
| Extension interference | Ad blockers and script blockers can break upload | No extension interference |
| Upload experience | Drag and drop or file picker dialog | Automatic sync from local folder |
| Offline access | Not available | Files On-Demand provides offline access |
For users who frequently encounter Chrome upload failures, switching to the desktop sync client eliminates browser-based issues entirely. The sync client handles large files and special characters more reliably.
By following this checklist, you can isolate whether the Chrome upload failure is caused by cookie settings, an extension, a corrupted profile, or a managed policy. Start with cookie settings and extension testing, as these are the most common causes. If the problem persists, consider directing users to install the OneDrive sync client for a more stable upload experience. As an advanced tip, configure a Chrome policy that forces third-party cookies to be allowed for Microsoft domains by using the CookiesAllowedForUrls policy in the Chrome admin console.