Mac Slow When OneDrive Is Syncing? Here's Why

OneDrive on Mac has a reputation, and not a flattering one. Long-time Mac users complain about high CPU, fans spinning during sync, beach balls when opening Finder windows, and a “Files On-Demand” implementation that has changed three times in five years and still doesn’t feel native.

Most of the complaints are valid. Microsoft’s OneDrive client uses a different sync architecture than Dropbox or iCloud Drive — one that involves more processes, more file system extensions, and more overhead per file. On a Mac with thousands of synced files, that overhead compounds.

What OneDrive Is Doing in Activity Monitor

While OneDrive is running and syncing, you’ll see in Activity Monitor:

• OneDrive — the main app and menu bar item
• OneDrive File Provider — the macOS File Provider extension that handles Files On-Demand
• OneDrive (Helper) — sub-process for various tasks
• com.microsoft.OneDriveStandaloneUpdater — the auto-updater

The File Provider extension is new-ish — Microsoft moved to it to comply with macOS’s modern file extension architecture. It’s better than the old kernel extension approach, but it still has a noticeable footprint. During heavy sync, it can use 1-2GB of RAM and 30-50% CPU.

The pain points stem from how OneDrive handles file metadata. macOS file system attributes (extended attributes, finder tags, custom metadata) don’t map cleanly onto OneDrive’s metadata model. Every file write triggers metadata translation. Every Finder browse hits the File Provider for placeholder rendering.

Free up RAM in one clickSweep frees inactive memory and pauses runaway processes. Get Sweep free →

Why the First Sync Is Excruciating

When you first set up OneDrive on a Mac with a populated cloud, the initial sync can take days. You’ll see:

• Constant disk activity
• Network usage at maximum sustained rate
• High CPU as files are downloaded, indexed, and verified
• Spotlight reindexing the new files
• Time Machine wanting to back up the new files

This compound effect is real. OneDrive isn’t the only thing reacting to thousands of new files appearing in your home folder.

To minimize the pain:

1. Use Files On-Demand. Settings > Sync and backup > Files On-Demand. Files become placeholders that download only when opened
2. Pause non-OneDrive heavy tasks during initial sync. Quit Time Machine, pause Photos uploads, defer system updates
3. Sign in over a wired connection if available — sustained throughput is better than Wi-Fi for thousands of files

For corporate accounts with hundreds of GB, the initial sync can run overnight and into the next day. Plan accordingly.

Files On-Demand: Saving Space But Not Always CPU

Files On-Demand is the feature where files appear in Finder but aren’t downloaded until opened. It’s how OneDrive keeps a 500GB cloud account from consuming 500GB on your Mac.

Trade-offs:

• Saves disk space — only downloaded files take real space
• Browsing folders is fast — placeholder metadata is local
• Opening files has latency — must download first
• Some apps don’t handle placeholders well — especially older creative tools and some IDEs

If you’ve enabled Files On-Demand and Finder still feels slow, the cause is often:

1. A folder with tens of thousands of files — even placeholders cost something to render
2. Spotlight indexing the placeholders — even though they’re not real files, Spotlight still tries
3. Backup software scanning the OneDrive folder

Spotlight is the sneaky one. To exclude OneDrive from Spotlight: System Settings > Siri & Spotlight > Spotlight Privacy > add your OneDrive folder.

Selective Sync: When You Don’t Need Everything

Even with Files On-Demand, syncing 100,000 files means OneDrive maintains 100,000 placeholders. Each costs a small amount of metadata, plus a Finder integration cost.

Selective sync lets you exclude folders entirely. They won’t appear in Finder.

To configure: OneDrive menu bar icon > Settings (gear icon) > Account > Choose folders. Uncheck folders you don’t need on this Mac.

For a corporate setup with multiple team libraries, this is essential. You probably don’t need every team’s files locally. Sync only the ones you actually use.

The Power Use Case That Isn’t a Use Case

OneDrive does not handle “millions of small files in a single folder” well. If you have a Node.js node_modules with 200,000 files, putting that inside your OneDrive folder is a recipe for disaster. Sync will:

• Take hours, possibly days
• Constantly notify you of “syncing N items”
• Dramatically slow Finder
• Cause file conflicts during npm installs
• Burn battery

Solution: exclude these folders. OneDrive doesn’t have a built-in .gitignore-equivalent (Microsoft has been promising one for years), but you can:

• Move the folder outside your OneDrive directory
• Use Microsoft’s Known Folder Move with care
• Symlink instead of placing actual data inside OneDrive

For developers especially, keep working code repositories outside OneDrive. Use Git for version control instead.

Skip the manual huntSweep finds the buildup slowing your Mac and clears it in seconds. Download Sweep free →

Settings Worth Changing

In OneDrive’s Settings:

• Sync and backup > Sync settings > Files On-Demand: ON
• Sync and backup > Bandwidth: limit upload and download if sync is hammering your connection
• Sync and backup > Pause syncing automatically when this device is on a metered network: ON
• Sync and backup > Battery saver: ON — pauses sync when on battery and below 20%
• Notifications > limit “people share files with you” notifications — they spawn extra background work
• About > Set OneDrive to start automatically: OFF if you don’t need it always running

In macOS:

• System Settings > General > Login Items — verify OneDrive is intentionally there
• System Settings > Notifications > OneDrive — disable noisy notifications
• Spotlight Privacy — exclude OneDrive folder

Why It Sometimes Won’t Stop Syncing

A common frustration: OneDrive shows “Syncing 1 file” for hours, but won’t progress.

Causes and fixes:

1. A specific file with permissions issues — try unchecking the folder containing it, then re-checking
2. A file with characters OneDrive can’t handle — colons, asterisks, certain unicode. Rename
3. A file that’s open in another app with a write lock
4. Sync database corruption — rare but real

The reset procedure for a stuck sync:

1. Quit OneDrive (right-click menu bar > Quit OneDrive)
2. Open Terminal
3. Run: ~/Library/Application\ Support/OneDrive/OneDrive.app/Contents/Resources/ResetOneDriveApp.command
4. Sign in again. OneDrive will rebuild its sync state without re-downloading already-present files

This is heavier than restarting OneDrive but lighter than reinstalling.

There’s a faster waySweep diagnoses what’s eating your performance and clears it in seconds. Try Sweep free →

A Diagnostic for OneDrive-Related Slowness

When your Mac drags whenever OneDrive is syncing:

1. Check Activity Monitor. Look at OneDrive and OneDrive File Provider CPU and memory
2. Check the OneDrive icon’s status — is it actively syncing or “up to date”?
3. Check what’s syncing — click the icon to see the activity panel
4. Pause sync to confirm OneDrive is the cause
5. Check folder sizes — do you have a node_modules or similar massive folder synced?
6. Exclude problematic folders from Spotlight and from sync
7. Reset OneDrive if state seems corrupted
8. Reinstall as a last resort, after backing up your local OneDrive folder

When OneDrive Is the Wrong Tool

If your workflow involves:

• Hundreds of thousands of files in a single folder
• Frequent rapid file changes (compilation outputs, log files)
• Files that you want to be reliably and immediately available offline
• Heavy Mac-specific metadata you can’t lose

Consider whether OneDrive is the right sync tool. Dropbox handles many small files better. iCloud Drive handles Mac metadata better. Git is better for code.

For document storage, occasional sharing, and corporate compliance reasons, OneDrive is often unavoidable. Tune it as described above and it stays out of your way most of the time.

Long-Term Habits

To keep OneDrive from quietly degrading your Mac’s performance:

• Audit synced folders quarterly. What are you actually using?
• Update OneDrive promptly. Microsoft’s improvements are real, especially the File Provider migration
• Don’t sync developer working directories. Use Git, keep code separate
• Watch for “syncing forever” states and reset OneDrive when they happen

Sweep keeps the surrounding macOS environment healthy — when OneDrive is doing heavy initial sync, having a Mac with clean caches and trimmed login items means more headroom for OneDrive to work without dragging everything else down. Combined with sensible sync settings, OneDrive becomes a quiet background tool instead of a daily aggravation.