Why Mac Storage Stays Full After You Turn On iCloud Optimization

The Quick Answer

If you turned on Store in iCloud (or the older "Optimize Mac Storage" toggle) and your Mac still reads as full, the setting almost certainly worked exactly as designed. It just was not aimed at whatever is actually filling your drive.

"My Mac says Optimize Storage is on, so why is it still full" is one of the most common storage complaints on Apple's own community forums, and the confusion is reasonable. The feature changed names and location at least once, two separate settings share overlapping language, and neither Apple's marketing copy nor most third-party guides spell out what the toggle is scoped to. This is a plain accounting of what it actually does, checked against Apple's current documentation and a Mac running macOS 27 Golden Gate, dated October 16, 2026.

Why the Setting Has Two Different Names

Search for "Optimize Mac Storage" today and you will find years of forum threads, guides, and screenshots describing a checkbox that used to live inside the iCloud pane of System Preferences, next to iCloud Drive. That pane is gone in current System Settings. Apple's live Mac Help guide, which we checked on October 16, 2026, now documents the equivalent behavior under a different name: open the Apple menu, choose System Settings, click General, then Storage. Inside Storage, a recommendation called Store in iCloud is what now does the job the old checkbox used to do.

The naming confusion gets worse because a second, differently scoped setting sits right next to it with a near-identical name. Apple's own page describes Optimize Storage as a setting that "automatically removes movies and TV shows that you've already viewed from your Mac," full stop, nothing broader. It has nothing to do with your Desktop, your Documents, your Mail attachments, or any of your working files. If you turned on "Optimize Storage" expecting it to behave like the old "Optimize Mac Storage," you turned on the wrong one of two settings that sound almost the same.

No release notes we could find for macOS 27 Golden Gate, which shipped September 14, 2026, mention a change to this part of Storage settings, and the menu path above matched what we saw on a Golden Gate Mac during this check. Intel Macs that stayed on macOS 26 Tahoe (Golden Gate dropped Intel support entirely) use the identical General > Storage layout, unchanged since at least Tahoe 26.2.

What Store in iCloud Actually Moves

Apple's current guide describes Store in iCloud as a setting that "turns on iCloud Drive and stores most files in iCloud, saving storage space," keeping only recently used files fully downloaded on your Mac. The same guide's iCloud Drive entry spells out what that mainly means in practice: "it may also contain files in your Desktop and Documents folders if you store them in iCloud Drive." In plain terms, every file in those two folders gets uploaded to iCloud Drive. As long as you have room, full copies stay local too. Only when your disk actually gets tight does macOS start removing the local copies of older, less-recently-opened files, leaving a cloud placeholder with a small download-arrow icon in Finder in their place.

Your Photos library gets the same treatment through a separate toggle that lives in a different place: Photos app's own Settings, under the iCloud tab, labeled "Optimize Mac Storage" there. Turn it on and Photos keeps every thumbnail local while downloading full-resolution originals from iCloud on demand, the same demand-driven pattern as Store in iCloud, just reached through the Photos app instead of General > Storage. Both are genuinely useful if the bulk of your storage problem really is a Desktop full of project files or a decade of full-resolution photos.

One honest caveat before you flip this on for the first time: a community-reported pattern worth knowing is that Time Machine needs to download an evicted iCloud file before it can back it up. If your disk is too full for that download to happen, the only surviving copy of that file can end up being the one sitting in iCloud, not a local backup. That is not a documented Apple warning, it is a pattern reported by users troubleshooting backup gaps, so treat it as a reason to check your backup coverage before relying on heavy iCloud eviction, not as a reason to avoid the feature outright.

What It Never Touches

Everything below sits outside the Desktop, Documents, and Photos scope Store in iCloud covers, so turning the setting on or off has no effect on any of it, no matter how long you wait.

• Developer caches. node_modules folders, Xcode's DerivedData, and Flutter or Gradle build artifacts live wherever your project folders are, almost never inside Desktop or Documents specifically, and are not iCloud Drive content even when they happen to sit there. See our guide to cleaning Xcode's cache for what typically accumulates here.
• Duplicate files. Store in iCloud does not compare file contents or remove redundant copies anywhere. It only decides whether a file's one existing copy sits locally or in the cloud.
• Local Time Machine snapshots. These are an APFS-level mechanism entirely separate from iCloud, managed by tmutil and Disk Utility, not by any iCloud setting. They are frequently the real cause behind "I deleted files and nothing changed."
• Old installers, DMGs, and app leftovers. None of this is routed through iCloud Drive unless you manually dragged it into a synced folder.
• Unused applications and their support files. An app you have not opened in two years stays exactly where it is regardless of any Storage recommendation you accept.

For a fuller breakdown of what typically lives in each of these buckets and how much space is normal to see, see our guide to what System Data actually is on a Mac.

Why the Storage Pane's Own Numbers Can Mislead You

Even once you know what Store in iCloud does and does not cover, the Storage pane itself has a documented blind spot that makes the whole picture harder to read. The Eclectic Light Company's explainer on the redesigned Storage settings, tested against macOS Tahoe 26.2 and published December 20, 2025, found that the category breakdown leaves purgeable space and local snapshots out of its displayed figures entirely, dumping whatever it cannot otherwise categorize into a catch-all System Data bucket the article calls the pane's single greatest weakness. Disk Utility's own APFS Snapshots view, reached by selecting your Data volume, choosing View, then Show APFS Snapshots, and pressing Calculate, is the more reliable place to see what a snapshot is actually holding.

A follow-up piece from the same author, published August 24, 2026 against macOS Tahoe 26.6.2, measured this directly: a Time Machine snapshot held roughly 94.8GB of files on a 100GB APFS test container after those files had already been deleted, and on at least two occasions macOS failed to purge that snapshot automatically even when copying a large file should have forced it to free the room. If your Storage pane shows little progress after a cleanup, including after enabling Store in iCloud, a stuck local snapshot is a more likely explanation than the iCloud setting having failed.

How to Tell Whether It Actually Helped

1. Open System Settings > General > Storage and note the total used figure before making any change.
2. Turn on Store in iCloud if it is not already on, then give it time. Eviction of older files is gradual and tied to how tight your disk actually is, not instant the moment you flip the switch.
3. Check Finder for the cloud-download icon next to files in Desktop and Documents. A small cloud arrow means that file's local copy has genuinely been removed.
4. Open Disk Utility and check for snapshots on your Data volume before concluding the setting failed. If a large purgeable total shows up there that the Storage pane never mentioned, that is very likely where your missing space actually is.
5. Look at what is left with a category scan, not just the total. If what remains is mostly developer caches, duplicates, and old installers, no iCloud setting was ever going to touch it, and that is where a dedicated local cleanup pass comes in.

Method Comparison: iCloud Optimization vs Manual Cleanup vs Files Magic AI

None of these three replace each other. Store in iCloud and System Cleaner solve different categories of the same complaint, and the manual route can reach a few things neither tool does, most notably forcing a stubborn local snapshot to thin with tmutil, at the cost of real Terminal time. The honest sequence for most people: turn on Store in iCloud first since it costs nothing, check Disk Utility for snapshots second, then run a cleaner for the developer caches, duplicates, and leftovers that neither of the first two steps reaches.

Where Files Magic AI Fits, and Where It Cannot Help at All

Files Magic AI's System Cleaner scans your drive for duplicate files, unused applications, old installers and DMGs, and developer caches, including node_modules folders, Xcode DerivedData, and Flutter or Gradle build artifacts, groups what it finds by category with sizes shown, and waits for you to review before anything moves to the Trash. For node_modules specifically, it saves a restore note listing the package-manager commands to rebuild the folder if you ever need the project again. It is included on every plan, from the $2.49 first month (then $4.99/month) through the $34.99 yearly plan and the $59.99 one-time lifetime license, each with a 3-day free trial.

Here is the limit we want to state plainly rather than gloss over: System Cleaner can only act on what is physically present on your disk. Once Store in iCloud has evicted a file to the cloud, it is a placeholder, not local data, and there is nothing left for System Cleaner, or any local cleanup tool, to scan, deduplicate, or remove. If your entire storage problem really is a Desktop and Documents folder that Apple's own free setting can legitimately offload, Store in iCloud is the correct fix by itself, and paying for a cleaner would add nothing. System Cleaner also cannot thin a local Time Machine snapshot (that is a tmutil and Disk Utility job) and cannot fix the Storage pane's own reporting gaps described above. It earns its place specifically in the categories iCloud optimization was never built to reach.

Sources & Further Reading

Frequently Asked Questions

The Bottom Line

Store in iCloud, the modern name for what most people still call Optimize Mac Storage, does exactly one job well: it keeps Desktop, Documents, and Photos from piling up on local disk by moving older copies to iCloud. It was never built to touch developer caches, duplicates, old installers, unused apps, or a stuck local snapshot, so when a full Mac does not shrink after turning it on, the setting almost certainly worked, it just was not aimed at your actual problem. Check Disk Utility for snapshots, then run a local scan for the categories iCloud was never going to reach.

Published October 16, 2026 · More guides · What is System Data on Mac · How to reduce System Data · How to free up disk space · Files Magic AI