Field teams using OneDrive for Business often upload files through the web interface when the desktop sync app is unavailable. When uploads fail in one browser but work in another, the issue is typically caused by browser-specific settings, cached data, or extension conflicts. This article explains the root causes of browser-specific upload failures and provides a structured troubleshooting workflow for field support staff. You will learn how to isolate the failing browser, apply targeted fixes, and prevent recurrence without reinstalling software.
Key Takeaways: Fixing OneDrive Web Upload Failures in One Browser
- Clear browser cache and cookies: Resolves corrupted session data that blocks file uploads in a single browser.
- Disable third-party extensions: Ad blockers, script managers, and privacy tools often interfere with OneDrive’s upload endpoint.
- Check browser storage limits: When IndexedDB or localStorage is full, the browser cannot stage large uploads.
Why OneDrive Web Uploads Fail in One Browser but Not Another
OneDrive for Business uses the browser’s Web API stack to handle file uploads. The upload process relies on the Fetch API, IndexedDB for chunked upload staging, and the browser’s cookie store for authentication tokens. When one browser fails while another succeeds, the root cause is almost always a browser-specific state or configuration issue rather than a network or account problem.
The most common technical causes include:
Corrupted or Stale Session Data
The browser stores OneDrive authentication tokens in cookies and local storage. If these tokens become corrupted, expired, or mismatched with the server session, the upload request is rejected. This is why clearing cache and cookies in the failing browser often resolves the issue immediately.
Extension Interference
Extensions such as ad blockers, script blockers, and privacy tools can intercept or block the Fetch API calls that OneDrive uses for uploads. Some extensions modify HTTP headers, remove CORS credentials, or block specific file types. Since extensions are browser-specific, they explain why one browser fails and another works.
Storage Quota Exceeded
OneDrive uses IndexedDB to store upload chunks temporarily. Each browser allocates a limited amount of disk space for IndexedDB. When this quota is full, new uploads fail silently. This is more common on older devices or browsers with aggressive storage limits.
Outdated Browser Version
Older browser versions may lack support for the Fetch API or have bugs in the IndexedDB implementation. Microsoft 365 requires a modern, up-to-date browser. If the failing browser is not updated, the upload process may fail at any stage.
Step-by-Step Fix for Browser-Specific Upload Failures
Follow these steps in order. Test the upload after each step to identify the exact cause.
- Clear browser cache and cookies for the Microsoft 365 domain
Open the failing browser. Go to the settings menu and find the option to clear browsing data. Select Cookies and other site data and Cached images and files. Set the time range to All time. In the site-specific clearing option, enter onedrive.com, microsoft.com, and sharepoint.com and all subdomains. Clear the data and restart the browser. Try uploading again. - Disable all browser extensions temporarily
Open the browser’s extension management page. In Chrome, go to chrome://extensions. In Edge, go to edge://extensions. Disable every extension by toggling the switch off. Restart the browser. Attempt the upload. If it succeeds, re-enable extensions one by one until the failing extension is identified. - Check and clear IndexedDB storage
Open the browser’s Developer Tools with F12. Go to the Application tab. Under Storage, expand IndexedDB. Right-click each OneDrive-related database and choose Delete. Then go to Clear storage and click Clear site data. Restart the browser and test the upload. - Update the browser to the latest version
Check for updates in the browser’s About page. In Chrome, go to chrome://settings/help. In Edge, go to edge://settings/help. The browser will check and install updates automatically. Restart the browser after the update completes. Test the upload. - Reset browser settings to default
If the issue persists, reset the browser to factory defaults. In Chrome, go to Settings > Reset and clean up > Restore settings to their original defaults. In Edge, go to Settings > Reset settings > Restore settings to their default values. This removes all extensions, cookies, and site data without deleting bookmarks or passwords. Restart the browser and test the upload. - Use the browser’s InPrivate or Incognito mode as a workaround
Open a new InPrivate window in Edge or Incognito window in Chrome. Sign in to OneDrive again. Upload the file. If this works, the issue is caused by extensions or cached data in the regular profile. Use InPrivate mode as a temporary workaround until the main profile is cleaned.
If OneDrive Web Upload Still Fails After the Main Fix
File size exceeds the browser upload limit
OneDrive for Business web uploads are limited to 250 GB per file. However, some browsers impose a lower limit on individual file uploads through the Fetch API. If the file is larger than 2 GB, try using the OneDrive desktop sync app instead. If the desktop app is not available, compress the file into a ZIP archive smaller than 2 GB and upload that.
Network proxy or VPN blocks the upload endpoint
Some corporate proxies or VPNs block the specific endpoints used for chunked uploads. The failing browser may be configured to use a proxy while the working browser uses a direct connection. Check the browser’s proxy settings. In Chrome, go to Settings > System > Open your computer’s proxy settings. In Edge, go to Settings > System and performance > Open your computer’s proxy settings. Temporarily disable the proxy and test the upload.
Browser profile corruption
If all previous steps fail, the browser user profile may be corrupted. Create a new browser profile. In Chrome, click the profile icon and choose Add. In Edge, click the profile icon and choose Add profile. Sign in to OneDrive with the new profile and test the upload. If it works, migrate bookmarks and settings from the old profile and delete the corrupted one.
Browser Support Comparison for OneDrive Web Uploads
| Item | Chrome | Edge |
|---|---|---|
| Minimum version | Chrome 90 or later | Edge 90 or later |
| Maximum file size | 250 GB (subject to browser Fetch API limit) | 250 GB (subject to browser Fetch API limit) |
| IndexedDB quota | Up to 60% of available disk space | Up to 60% of available disk space |
| Extension interference risk | High (many ad blockers and privacy tools) | Medium (fewer extensions by default) |
| InPrivate/Incognito mode | Supported | Supported |
| Proxy configuration | Uses system proxy settings | Uses system proxy settings |
Both Chrome and Edge provide equivalent upload capabilities for OneDrive for Business. The key difference is extension ecosystem density. Field teams should standardize on Edge for OneDrive web uploads because it has fewer extension conflicts by default and integrates natively with Microsoft 365 authentication.
You can now identify and resolve browser-specific OneDrive upload failures using the six-step sequence. Start with clearing cache and cookies, then disable extensions, and escalate to profile reset only if necessary. For field teams working in constrained environments, configure Edge with the InPrivate mode always-on Group Policy to bypass extension issues permanently. This policy is available in the Microsoft 365 admin center under Devices > Configuration profiles > Create profile > Settings catalog > Microsoft Edge > InPrivate mode availability.