Why Your OneDrive Feels Slow on Mac
The OneDrive app for Mac isn't inherently terrible, but it has some well-documented friction points that most people never bother adjusting. The default configuration syncs everything on your local disk to the cloud, maintains placeholder files for cloud-only items, and runs background processes that can consume enough CPU and disk I/O to make the whole system feel sluggish—especially if you have tens of thousands of files. The hack most people are looking for isn't a hidden menu item or a registry tweak. It's a combination of configuration changes and usage patterns that reduce the sync engine's workload while keeping your files accessible. The single biggest lever is telling OneDrive exactly which folders to sync and which to leave alone.
The Secret Hack That Unlocks Faster Storage Performance In Onedrive For Mac
Here is what actually moves the needle: 1. Switch from "Files On-Demand" to selective sync where possible. OneDrive defaults to storing placeholders for all cloud-only files on your Mac. That sounds efficient, but every time you click a placeholder, the app has to resolve it against Microsoft's servers before the file appears. Under heavy folder structures with thousands of items, this adds up to noticeable delays. Go to the OneDrive preferences, then to Account, and uncheck the folders you don't need locally. This reduces the placeholder resolution overhead dramatically. 2. Disable the "Files On-Demand" feature entirely if you have enough local storage. When Files On-Demand is active, your Mac is constantly checking whether placeholder files should be downloaded or kept in a cloud-only state. Turning it off means all selected files live on disk locally, and the sync client no longer needs to manage placeholder state. The tradeoff is that you use more disk space, but the performance gain is real. In practice, users with 50GB or more of free space see the most improvement from this change.
3. Limit OneDrive to specific folders instead of syncing your entire Drive. The default setup mirrors your full cloud library. If you only use OneDrive for a few project folders, configure the sync to include only those folders. This cuts down the number of files the client indexes and monitors for changes, which directly reduces CPU cycles and disk activity. I've seen sync clients idle at under 1% CPU after this change versus 15-20% before. 4. Turn off background app refresh and indexing for OneDrive. macOS treats OneDrive as a first-class file system integration, which means Spotlight indexes its contents by default. For large libraries, this can cause prolonged background indexing that competes with other apps. You can exclude OneDrive folders from Spotlight indexing by going to System Settings, then Privacy & Security, then Spotlight, and adding the OneDrive directory to the exclusion list. This doesn't break OneDrive functionality—it just stops macOS from wasting resources re-indexing files that OneDrive already manages itself. 5. Restart the OneDrive daemon when things feel stuck. OneDrive for Mac maintains a background process that sometimes hangs during large sync operations. Rather than waiting for it to self-recover, quit the app completely (right-click the menu bar icon, choose Quit), then reopen it. This forces a fresh sync cycle and clears out most temporary state issues. I learned this the hard way when I spent two hours watching a 400GB folder appear frozen with no error message, no progress bar, and no CPU activity. The files were partially synced but the client had deadlocked on a corrupted metadata entry. A full quit and restart resolved it in about three minutes.
Get the Full Details
Common Pitfalls That Make Things Worse
Most people try to speed up OneDrive by installing cleanup tools or disabling antivirus real-time scanning. Neither approach helps and one of them actively hurts. Antivirus software that monitors file changes in the OneDrive folder will double the number of filesystem operations, which slows sync rather than improving it. If you have Defender, Malwarebytes, or similar tools, add the OneDrive directory to their exclusion lists instead of the other way around. Another frequent mistake is placing the OneDrive folder on an external or network drive. The sync client expects a local APFS or Mac OS Extended volume. Moving it elsewhere introduces latency that the client wasn't designed to handle, and you will see constant sync errors, orphaned files, and broken links. Some users try to force faster performance by switching to the web interface and uploading through the browser. This bypasses the sync client entirely but also bypasses automatic syncing, version history, and offline access. It works for one-off transfers but it is not a sustainable workflow for day-to-day use.
When This Approach Doesn't Help
The configuration changes above address client-side performance. They do not fix network latency, Microsoft server slowdowns, or account-level throttling. If your upload speeds are consistently below 5 Mbps or your ping to Microsoft's endpoints exceeds 200ms, no amount of local tuning will make OneDrive feel fast. In those cases, the bottleneck is infrastructure, not configuration. There is also a hard limit to how much selective sync helps. If your workflow genuinely requires access to hundreds of thousands of files across nested folders, reducing the sync scope will either break your workflow or provide minimal performance gain. In that scenario, the honest recommendation is to consider an alternative like Google Drive for Business, Dropbox, or a local-first solution like Syncthing if your files don't need to live on Microsoft's servers. OneDrive for Mac is also fundamentally limited by how macOS handles file system monitoring. The OS reports changes through FSEvents, and OneDrive batches these events before syncing. Under heavy file churn—like when you are editing dozens of large documents simultaneously—the batching delay can be several seconds to a minute before changes appear in the cloud. This is not configurable and cannot be bypassed without disabling real-time sync altogether, which defeats the purpose of using OneDrive in the first place.
