iCloud Drive Auto-Downloads Every File in macOS Tahoe 26.4: Cause, Workarounds, and What's Next

You open your ~/Documents folder in Finder, scroll past a few files, and notice something odd: every single item — hundreds of PDFs, Keynote decks, photos, archives — is suddenly downloading. Not the one you double-clicked. All of them. The little cloud icons turn into download arrows, your fan starts spinning, and your menubar Wi-Fi indicator lights up. By the time you realize what is happening, your 256 GB MacBook Air has eaten 40 GB of your iCloud library, and your hotspot data plan has cratered.

This is the bug that has dominated Apple Community threads since macOS Tahoe 26.4 shipped in late March 2026. It affects users who rely on Optimize Mac Storage — the very feature that is supposed to keep iCloud Drive lightweight on disk by leaving rarely-used files in the cloud. After 26.4, simply browsing a folder is enough to trigger a full local download of its contents, defeating the entire purpose of the feature.

Apple has not acknowledged the bug publicly as of this writing. There is no release-note line item, no hotfix, no AppleSeed ticket the average user can file results against. What we do have is a growing pile of reproductions on Apple Discussions thread 256273434, Reddit, and developer forums — plus four workarounds that actually reduce the damage while we wait for 26.5.

This article walks through what is happening, why it is probably happening, and how to keep your bandwidth and SSD intact in the meantime.

Key Takeaways

• The bug: After macOS Tahoe 26.4 (and the follow-up 26.4.1), navigating into an iCloud Drive folder in Finder triggers downloads of every file inside, even if Optimize Mac Storage is enabled.
• Who is affected: Anyone using iCloud Drive with Optimize Mac Storage on. The damage is worst for users with small SSDs (128 GB / 256 GB MacBooks) and metered connections (hotspot, cellular, capped home plans).
• Suspected cause: A regression in the file-coordination layer used by bird (the CloudDocs daemon) and Finder's QuickLook prefetch — files that were previously hydrated only on read are now hydrated on directory enumeration.
• Workarounds available today: Toggle Optimize Mac Storage off and back on, manually evict downloaded files with the brctl evict Terminal command, disable Optimize Mac Storage entirely and live with full local copies, or use iCloud.com for selective access.
• Long-term fix: Community testers report partial improvement in macOS 26.5 beta 4, with general availability expected late May 2026. Apple has not formally confirmed the fix.

What Users Are Actually Seeing

Before we get into causes, let us be precise about the symptom because there are several adjacent iCloud bugs floating around and they are easy to confuse.

The reported behavior, consistent across multiple reports on the Apple Discussions thread:

1. User has System Settings → Apple Account → iCloud → iCloud Drive → Optimize Mac Storage turned on.
2. Files in iCloud Drive that have not been opened recently show the small cloud-with-down-arrow badge in Finder, indicating they are stored remotely.
3. User opens a folder in Finder — for example ~/iCloud Drive/Documents/Invoices/2024/ — that contains, say, 200 PDFs.
4. Within seconds, every file in that folder begins downloading. Finder's status bar shows a cumulative progress bar ("Downloading 200 items, 4.2 GB of 12.8 GB"). The cloud badges flip to blue progress rings.
5. If the user navigates into a subfolder, the same thing happens recursively.

This is not the normal "fetch a thumbnail for QuickLook" behavior that Finder has always done. Thumbnail fetches were small (kilobytes per file at most) and did not change the file's "stored locally" state. The 26.4 behavior fully hydrates the file — meaning the entire payload lands on disk and counts against your local storage.

A handful of users on the thread report that the bug does not always trigger immediately. Sometimes it kicks in when Spotlight indexing touches the folder. Sometimes it happens only when a Finder column-view preview pane is open. Sometimes it happens only after the Mac has been idle and bird runs a maintenance pass. The trigger is inconsistent, which is part of what makes the bug hard to confirm and harder to file a clean bug report for.

What is consistent is the outcome: files that should have remained as cloud placeholders end up fully downloaded.

Why This Matters More Than It Sounds

If you have a 2 TB Mac Studio on Gigabit fiber, this is annoying but not catastrophic. For everyone else, the bug is genuinely painful.

Storage pressure on small SSDs. Apple still ships 256 GB as the base configuration on most consumer Macs. A 200 GB iCloud library that hydrates aggressively will fill the disk in minutes. Once disk usage crosses ~90 percent, macOS itself begins to misbehave — Spotlight rebuilds fail, swap thrashes, app launches slow down, and the system may forcibly evict cached files in unpredictable order.

Bandwidth bills on metered connections. A startling number of Mac users work from coffee shops, coworking spaces, hotels, or rural homes where bandwidth is metered or capped. A single accidental browse of a Photos library backup folder can blow through a month's data allowance in an afternoon. Cellular hotspot users are particularly exposed because there is no warning before the download begins.

Backup chaos. If you use Time Machine or a third-party clone tool, every newly-hydrated file is now a "changed" file from the backup tool's perspective. Your next backup run becomes massive — sometimes terabytes — even though nothing meaningful has changed about the content. We discuss the backup angle further in our Mac backup strategy guide.

Battery and thermals. Continuous downloads keep the Wi-Fi radio active and the SSD writing constantly. On laptops, this measurably reduces runtime and can trigger thermal throttling on fanless models like the MacBook Air.

In short, this is one of those bugs where the underlying defect is small but the downstream cost is large.

Confirming You Have the Bug

Before applying any workaround, take five minutes to confirm the bug is actually what is happening on your Mac. The symptoms can be confused with normal iCloud sync after a fresh login, or with the deliberate hydration that happens when an app like Spotlight or Backup tries to read a file.

Test procedure:

1. Open System Settings → General → Storage. Note your current free disk space.
2. Open Activity Monitor → Network tab. Sort by "Bytes Received" descending. Note the current value for bird (the CloudDocs daemon process).
3. In Terminal, run brctl status and confirm Optimize Mac Storage is enabled.
4. Open Finder and navigate to an iCloud Drive folder you have not visited in at least a week. Choose one with many files (50+) of meaningful size (1 MB+ each).
5. Wait 60 seconds. Do not click any individual file.
6. Return to Activity Monitor. Has bird received hundreds of MB or more?
7. Return to Storage settings. Has free disk space dropped noticeably?
8. Back in Finder, look at the file badges. Have cloud icons been replaced with progress rings or fully removed?

If the answer to questions 6, 7, and 8 is yes — and you did not click any file — you are seeing the bug.

If you want a more rigorous trace, you can run brctl monitor com.apple.CloudDocs in a Terminal window before step 4. You will see live events for every file bird decides to materialize. Under normal behavior in older macOS releases, only files you explicitly opened would generate materialize events. Under the 26.4 bug, you will see materialize events firing for every file in the directory you just opened, in rapid succession.

Root Cause: What Probably Changed in 26.4

Here is where we have to be honest about what is and is not known.

Apple has not published anything about this regression. The clearest signal from the developer-facing release notes for 26.4 is that the file-coordination layer received changes related to "improvements to iCloud Drive responsiveness" — that exact wording, with no further detail. Community speculation, based on careful observation of bird log output, suggests two related changes:

First, the prefetch heuristic that Finder uses to populate column-view previews and icon-view thumbnails appears to have been broadened. Previously, Finder asked bird for metadata — file size, modification date, thumbnail — for each visible file, and bird returned that without hydrating the full file. Under 26.4, the thumbnail subsystem appears to be requesting full file content for any file type where the thumbnail generator might need to examine the body — which in practice means almost everything: PDFs, images, videos, Office docs, even some plain text files.

Second, the eviction policy that normally re-offloads files to the cloud after a period of disuse has become much less aggressive. Files that should be evicted within hours are sticking around for days. This means that even if you trigger the bug just once, the damage compounds: the disk fills up faster than bird is willing to clean up.

Both observations are consistent with what users report: the trigger is folder navigation (because that is when Finder asks for thumbnails) and the damage persists (because nothing is evicting the files afterwards).

We want to flag clearly: this is community-derived speculation, not an official cause analysis. It is consistent with the symptoms but Apple has not confirmed it. If you are filing a Feedback Assistant report, describe the symptoms you observed, not the speculated cause.

For broader context on how iCloud Drive sync is supposed to work in Tahoe, our iCloud Drive complete guide covers the normal architecture. The current bug is a deviation from the documented behavior described there.

Workaround 1: Toggle Optimize Mac Storage Off Then On

This is the lowest-effort fix and works for some — some — users. It does not address the underlying bug, but it appears to reset the prefetch state in bird and buys you a temporary reprieve.

Steps:

1. Open System Settings → Apple Account (your name at the top) → iCloud.
2. Click iCloud Drive in the list of apps using iCloud.
3. Toggle Optimize Mac Storage off. Wait for the spinner to settle. macOS may warn that local copies will be downloaded — in this case ignore the warning because we will toggle back before that completes.
4. Wait 30 to 60 seconds.
5. Toggle Optimize Mac Storage back on.
6. Open Activity Monitor and watch bird for a minute. Network throughput should drop to near zero.

In the best case, this resets the daemon's internal state and folder browsing stops triggering downloads for a few hours or days. In the worst case nothing changes and you need to move to Workaround 2.

Caveat: If macOS did start downloading files between your two toggles, those files are now local. They will not be re-evicted automatically for some time (see the eviction policy issue above). You may want to follow up with Workaround 2 to manually free the space.

Workaround 2: Manually Evict Files with brctl evict

If files have already been auto-downloaded, you can push them back to the cloud manually using the brctl command-line utility. brctl is a real, shipped, Apple-provided tool — man brctl will confirm it on any Mac running Tahoe.

The relevant command is brctl evict, which "evict[s] the local copy of the document at this path" — exactly what we want.

Single file

brctl evict ~/Library/Mobile\ Documents/com~apple~CloudDocs/Documents/old-invoice.pdf

The path inside ~/Library/Mobile Documents/com~apple~CloudDocs/ is where macOS actually stores iCloud Drive contents. The Finder shortcut "iCloud Drive" in the sidebar maps to that path. You can also drag a file from Finder into a Terminal window to paste its full path automatically.

Entire folder, recursively

brctl evict does not have a built-in -R recursion flag, so we combine it with find:

find ~/Library/Mobile\ Documents/com~apple~CloudDocs/Documents/Invoices -type f -exec brctl evict {} \;

This walks the entire Invoices folder and evicts every file it finds. For a folder with hundreds of files this can take a minute or two — that is normal.

Free up the largest files first

If you are in a hurry to recover disk space, target large files only:

find ~/Library/Mobile\ Documents/com~apple~CloudDocs -type f -size +100M -exec brctl evict {} \;

The -size +100M filter restricts to files larger than 100 MB. Adjust to taste.

Check status before and after

brctl status

This prints a snapshot of the CloudDocs daemon's state, including how many files are local versus cloud-only. Run it before and after your eviction pass to confirm the change.

What brctl evict does not do

It does not delete the file from iCloud. It only removes the local copy on this Mac. The file remains in the cloud and the Finder placeholder stays in place — you can re-download it any time by double-clicking it (assuming the bug does not retrigger).

It also does not work on files that have unsaved changes or are currently open in an application. Close the relevant apps first.

A sanity check before you run wide eviction

Before you run find ... -exec brctl evict {} \; against a large tree, do a smaller dry run to confirm paths and behavior:

# List files that would be targeted, no eviction yet
find ~/Library/Mobile\ Documents/com~apple~CloudDocs/Documents/Invoices -type f -size +100M

# Then, once you have confirmed the list looks right, evict them
find ~/Library/Mobile\ Documents/com~apple~CloudDocs/Documents/Invoices -type f -size +100M -exec brctl evict {} \;

If bird is unable to evict a particular file (because it has uncommitted changes, is open elsewhere, or is part of an active iCloud sync operation) it will print an error and move on. Errors are non-fatal and do not stop the loop.

You can also use brctl dump com.apple.CloudDocs to print the full database state — this is verbose and mostly useful as a forensic tool, but if eviction is failing for non-obvious reasons it may help you spot which files are stuck.

A common pattern from frustrated users on the Apple thread is to wrap the eviction in a daily LaunchAgent — essentially a scheduled job that runs brctl evict against the entire iCloud Drive every night, on the assumption that the bug will refill the local cache during the day. We do not recommend this for most users because it is brittle and can interact badly with files you actually want offline. But if you understand launchd and want to try it, the recipe is straightforward.

Workaround 3: Disable Optimize Mac Storage Entirely

If your bandwidth situation is dire and you cannot afford even an accidental download, the nuclear option is to disable Optimize Mac Storage and accept that everything in iCloud Drive will live locally.

Trade-off analysis:

• Pro: No more surprise downloads. What is on disk is on disk. Network usage for iCloud Drive becomes purely the delta of files you create or modify.
• Pro: Predictable backups. Your nightly Time Machine and clones see only the files that actually changed.
• Con: You need free disk space equal to the full size of your iCloud Drive library. If you have 500 GB in iCloud and a 256 GB SSD, this is not an option for you.
• Con: The initial download after disabling Optimize Mac Storage is a one-time bandwidth hit equal to your entire library minus what is already local. For a 100 GB library, that is 100 GB of download.
• Con: You lose the convenience of opening any file in your library from any device — you now need to be more deliberate about what lives in iCloud Drive at all.

Many users in this situation use the moment as a forcing function to archive aggressively. Old projects, old invoices, old screenshots — move them to an external drive or an archive cloud (Backblaze B2, Wasabi, Dropbox cold storage) and remove them from iCloud Drive entirely. The storage management guide walks through tools to identify what is taking up space.

If you decide to go this route, expect the initial sync to take a long time — often days for a large library — and to keep your Mac plugged in and connected to power-friendly Wi-Fi during that period.

Workaround 4: Use iCloud.com for Selective Access

For files you only need to access occasionally — old tax documents, archived projects, reference PDFs — there is no rule that says you have to access them through Finder at all. iCloud.com gives you a web-based file browser that downloads only what you actively click.

When this works well:

• You need one specific file from a folder, not the whole folder.
• You are on a metered connection and want to be deliberate about every byte.
• You are on a borrowed Mac or one with very little free disk space.

Steps:

1. Visit iCloud.com in any modern browser and sign in.
2. Click iCloud Drive.
3. Navigate to the file you want. Click it once to preview, or click the download icon to save it to your local Downloads folder (not your iCloud Drive folder — important to keep it out of the sync loop).

This bypasses bird and Finder entirely. The download happens via standard HTTPS to your browser, and the file does not become part of your iCloud Drive cache on this Mac.

The downside is obvious — for daily working files, swapping into a browser tab is friction you do not want. But as a release valve for occasional access while the bug persists, it is genuinely useful.

Workaround 5: Third-Party Cloud Mounters as Alternatives

A handful of community members have switched to third-party tools that mount iCloud Drive (and other cloud services) as proper network volumes with strict on-demand semantics. The two most commonly mentioned:

• CloudMounter: Mounts iCloud Drive (and Dropbox, Google Drive, OneDrive) as a virtual disk. Only files you explicitly open are fetched. There is no Finder thumbnail prefetch because the mount uses a different protocol.
• Mountain Duck: Similar concept, with stronger emphasis on developer/SFTP workflows but with iCloud Drive support.

Important caveats: Neither tool has the same level of system integration as Apple's native iCloud Drive. Photos library sync, app sandbox container sync, and ~/Desktop and ~/Documents redirection do not work through these tools — those still go through the native Apple stack. They are useful for a specific archive or document folder you want strict control over, not as a wholesale replacement.

We have not personally tested these against the 26.4 bug, so treat reports as anecdotal until you confirm on your own setup. If you do experiment, do it on a non-critical folder first.

For more on power-user iCloud workflows in general, see iCloud Drive advanced workflows.

Bandwidth and Storage Impact: Rough Math

It helps to put numbers on the cost so you can prioritize.

Bandwidth scenario. Assume a 100 GB iCloud Drive library where 70 GB was previously stored as cloud placeholders (Optimize Mac Storage was working as designed). If the bug triggers a wholesale rehydration over the course of a week of normal Finder browsing, you redownload up to 70 GB. On a 50 Mbps connection that is roughly three to four hours of saturated download — or one month of a typical 100 GB cellular plan, gone in a week.

Storage scenario. Same 100 GB library, same 70 GB previously remote. After the bug runs its course you have 100 GB on disk. On a 256 GB SSD with the OS, apps, and other documents already taking 120 GB, you go from 66 GB free to nothing — and macOS will start refusing to save new files, evicting caches randomly, and warning about low disk space.

Multi-Mac scenario. This is the one that hurts the most. If you have two Macs — say a desktop and a laptop — both running 26.4 with Optimize Mac Storage on, the bug triggers on each independently. Browsing your library on the laptop hydrates files there; browsing on the desktop hydrates the same files there too. That is 2× the bandwidth cost. If your iCloud library lives on a NAS-backed Time Machine, you are also paying the storage cost on the backup target.

These are rough numbers, but the order of magnitude matches what people are reporting in the threads.

A worked example. Consider a freelance designer with a 250 GB iCloud Drive that holds completed client projects going back several years. Under normal Optimize Mac Storage behavior, only about 40 GB lived locally on her 512 GB MacBook Pro at any given time — recent projects, current invoices, a handful of references. After upgrading to 26.4 she opened her Clients/2023/ folder one evening to find a screenshot for a new pitch deck. Within 20 minutes her free disk space dropped from 180 GB to 60 GB. By morning, after Spotlight finished re-indexing the newly-downloaded files, she was at 28 GB free, with macOS warning her that startup disk was almost full. She had to spend an hour running brctl evict against years of archived projects she did not need locally just to recover working space. None of those files had been touched intentionally. None of that bandwidth had been planned for.

This is the lived experience of the bug for users with larger libraries and meaningful work to do. The numbers are not theoretical.

Storage Strategy Going Forward

Even after Apple fixes this specific regression, the episode is a reminder that "Optimize Mac Storage" is not a magic spell — it is a heuristic that can fail. Building some defense in depth into your storage strategy is worth it.

Be deliberate about what lives in iCloud Drive. If a folder is truly archival — you reference it once a year — it does not belong in iCloud Drive at all. Move it to an external SSD or an object-storage service. iCloud Drive should be reserved for files you actively work with across devices.

Use Photos library and iCloud Photos separately. Photos has its own optimization model that is more robust than iCloud Drive's. If your photo library is the bulk of your iCloud usage, the iCloud Drive bug does not directly affect it.

Monitor bird periodically. Add a quick check to your routine — once a week, run brctl status and du -sh ~/Library/Mobile\ Documents/com~apple~CloudDocs to see what is local. If the local size is creeping up unexpectedly, you can intervene early.

Set up disk-space alerts. macOS does warn about low disk space but only when it is critical. A more proactive monitor (DaisyDisk's free space widget, OmniDiskSweeper, or even a small shell script with osascript notifications) can catch problems while you still have time to react.

For a deeper treatment of these patterns, see our storage management optimization guide.

When Will Apple Fix This?

The next macOS release in the Tahoe cycle is 26.5. As of early May 2026, beta 4 is in the hands of developers and public testers. Multiple users on the Apple Discussions thread report that the auto-download behavior is less severe in beta 4 — folder browsing no longer triggers wholesale hydration in their tests. However, eviction still appears slower than pre-26.4 baseline, suggesting Apple has addressed the most acute symptom but not necessarily restored the original behavior.

Based on Apple's typical release cadence, 26.5 general availability is expected in late May 2026, possibly the week of May 18 or May 25. Apple has not formally confirmed the date, and historically dot-releases can slip into early June if late-stage regressions show up in beta.

We have a separate breakdown of what is in 26.5 beta 1 that we will update as betas progress. We will also update this article when 26.5 GA ships and we can confirm whether the iCloud Drive behavior is back to pre-26.4 levels.

In the meantime: do not assume the fix is in 26.5 GA. Test it on your own setup before re-enabling Optimize Mac Storage if you have disabled it. Apple's release notes for dot-releases are notoriously sparse and a fix may or may not be called out explicitly.

Best Practices While the Bug Is Live

To summarize the recommended posture for the next month or so:

1. Know your library size. Run du -sh ~/Library/Mobile\ Documents/com~apple~CloudDocs to see how much is local right now, and check System Settings → Apple Account → iCloud to see your total iCloud Drive usage.
2. Decide your tolerance. If you have plenty of disk and unmetered bandwidth, you can afford to leave Optimize Mac Storage on and clean up periodically with brctl evict. If either is constrained, disable Optimize Mac Storage and live with full local copies — or move the most archival content out of iCloud Drive.
3. Avoid casual browsing of large iCloud folders. Until 26.5 ships and is confirmed, treat Finder navigation into archive folders as a deliberate act, not idle clicking.
4. Watch your backups. A bug-driven hydration storm can multiply backup sizes by 10× or more for a single run. If you have backup quotas, watch them.
5. File a Feedback Assistant report. Even if Apple is aware of the bug, additional reports with reproducible cases and sysdiagnose attachments add weight. Use Feedback Assistant on macOS, file under iCloud → iCloud Drive, and describe your symptoms specifically.
6. Update your reference docs. The 26.4 / 26.4.1 update guide and the iCloud Drive complete guide are worth bookmarking — we update both as the situation evolves.

FAQ

Q1. Is this bug confirmed by Apple? No. As of early May 2026, Apple has not made any public statement about the iCloud Drive auto-download behavior in 26.4. Acknowledgment exists only in community threads such as Apple Discussions thread 256273434.

Q2. Does this affect iOS or iPadOS? The Finder-specific trigger does not exist on iOS or iPadOS because they use a different file browser. However, some iPadOS users report similar increased downloads in the Files app after recent updates. The cause may or may not be related — it is a separate investigation.

Q3. If I disable Optimize Mac Storage, will my files in the cloud be deleted? No. Disabling Optimize Mac Storage only changes the local-cache policy. Your files remain in iCloud. The change just means more of them live on your Mac at the same time as in the cloud.

Q4. Does brctl evict work on Photos library files? The Photos library has its own optimization model and does not use the same bird placeholders as iCloud Drive. brctl evict is not the right tool for Photos. For Photos space management, use System Settings → Apple Account → iCloud → Photos and the Optimize Mac Storage toggle there, which is a separate setting from the iCloud Drive one.

Q5. Can I script brctl evict to run automatically? Yes, via a launchd LaunchAgent or even a simple cron entry. We do not recommend it as a default because it can evict files you actually want offline. If you do, scope it tightly — for example only files larger than 100 MB and not modified in the last 30 days.

Q6. Does the bug happen with third-party cloud services? No. Dropbox, Google Drive, and OneDrive use their own daemons and have not been reported to exhibit similar behavior. The bug is specific to Apple's iCloud Drive stack on macOS 26.4.

Q7. Will rolling back to 26.3 fix it? Technically yes, but Apple does not officially support rolling back point releases. You would need to reinstall from a USB installer of an earlier macOS, which means erasing and restoring from backup. For most users this is a worse option than living with the bug for a few weeks.

Q8. What about Safe Mode — does the bug occur there? Safe Mode disables Spotlight indexing and many background services. Some users report the bug is less severe in Safe Mode, which supports the theory that Spotlight indexing or thumbnail prefetch is involved. Safe Mode is not a usable long-term workaround but it is a useful diagnostic.

Q9. I bought extra iCloud storage to deal with this — is that the right move? No. Extra iCloud storage gives you more cloud space. The bug is about your local disk and bandwidth. Buying more iCloud storage does not help. If anything it makes the worst case worse because there is more potential data to redownload.

Q10. Will the eventual 26.5 fix re-evict already-downloaded files? Probably not automatically. The fix is most likely to address the trigger (preventing future over-aggressive downloads) rather than retroactively cleaning up the cache. After 26.5 ships, you will likely still want to do a one-time brctl evict pass on folders you do not need offline.

Conclusion

The iCloud Drive auto-download bug in macOS Tahoe 26.4 is a textbook example of how a small regression in a low-level service — file coordination, in this case — can cascade into real costs for end users. The fix is in Apple's hands and appears to be partially in place in the 26.5 beta. Until then, the four workarounds outlined here can substantially limit the damage:

1. Toggle Optimize Mac Storage off and back on as a quick reset.
2. Use brctl evict to manually free space after files have auto-hydrated.
3. Disable Optimize Mac Storage entirely if your bandwidth situation requires it.
4. Use iCloud.com for selective access of archival files.

For ongoing context, our iCloud Drive complete guide, advanced iCloud workflows, and backup strategy guide cover the longer-term posture. The 26.4 update guide and 26.5 beta 1 guide track the broader release picture. We will update this article when 26.5 ships and confirm whether the bug is fully resolved.

If you have additional reproductions or details to share, the best place to add them remains Apple Discussions thread 256273434 — the more concrete reports there, the more pressure on Apple to ship a clean fix.