Short answer: turning on Optimize Mac Storage does not immediately remove every local iCloud Drive copy from your Mac. Apple currently documents the feature as storage-pressure driven: older documents can be kept only in iCloud when more local space is needed, while the full contents of iCloud Drive can remain downloaded when space is not needed. If you want to reclaim space from a specific file now, first verify that the current copy is safely in iCloud, then use Finder's Remove Download action rather than Delete.
That distinction is the entire incident. Optimize Mac Storage is an automatic eviction policy, not a one-click purge command. A downloaded file, a file marked Keep Downloaded, and a file still Waiting to Upload can all legitimately consume local storage for very different reasons. Treating them as the same state is how a storage-cleanup problem turns into a data-loss problem.
First, confirm which storage state the file is actually in
Before changing anything, open Finder → iCloud Drive, switch to List view, and enable the iCloud Status column in View Options. Apple currently exposes several states that are far more useful than the single question “Is this file in iCloud?”
| Finder state | What it tells you | Local-storage implication |
|---|---|---|
| In iCloud | The item is stored in iCloud and is not currently downloaded for offline use | Full file content is not meant to remain locally downloaded |
| Downloaded | The current item is up to date between this Mac and iCloud and can be opened offline | A local copy exists and uses Mac storage |
| Keep Downloaded | macOS has been told to keep this item downloaded even when storage pressure increases | Expect the local copy to remain |
| Waiting to Upload | The item is not yet stored in iCloud | The local copy may be the only current copy; do not remove or delete it |
| Out of Space | iCloud storage is insufficient for the item to be stored remotely | Local cleanup alone does not solve the cloud-side capacity problem |
This is the highest-value diagnostic step because the correct action changes by state.
If a 40 GB project folder is Downloaded, Optimize Mac Storage may eventually evict it when macOS needs space. If it is Keep Downloaded, you have explicitly told macOS not to do that. If it is Waiting to Upload, attempting to “free space” before the upload succeeds can remove the only current copy.
This same principle appears in other cloud clients, although the controls differ. Google Drive's streaming mode also separates cloud visibility from local persistence; see Google Drive Streaming Still Using Disk Space? for the equivalent Google-side model. pCloud uses a different virtual-drive architecture, covered in How pCloud Drive Cache Actually Works.
Why Optimize Mac Storage can be enabled while iCloud Drive still occupies hundreds of gigabytes
The misleading mental model is:
Optimize Mac Storage = every iCloud Drive file becomes cloud-only immediately.
Apple's current macOS documentation says something different. When Optimize Mac Storage is enabled, the Mac can automatically store older documents in iCloud when more space is needed. Apple also states that if space is not needed, the full contents of iCloud Drive remain on the Mac.
That means the feature is reactive to local storage pressure. It is not a guarantee that Finder will instantly evict every downloaded file after you flip the switch.
Consider a Mac with 300 GB free. You enable Optimize Mac Storage and expect a 120 GB iCloud Drive folder to vanish from local storage. macOS may have no reason to evict it yet because the machine is not under enough storage pressure. The folder being downloaded is therefore not evidence that Optimize Mac Storage is broken.
The better question is:
Do I want macOS to manage eviction automatically, or do I need to reclaim space from specific files now?
Those are different jobs.
If you need the space now, use Remove Download—not Delete
For a file that is already safely stored in iCloud Drive, Apple provides a direct action: Control-click the item → Remove Download.
That action removes the downloaded local copy while leaving the item stored in iCloud Drive. The filename remains visible in Finder and can be downloaded again later when you open it or explicitly choose Download Now.
Why this is safer than Delete
Delete changes the synchronized file state. Apple's current Desktop & Documents documentation states that deleting a file on one device deletes it from the other devices signed in with the same Apple Account. Deleted files are normally recoverable from Recently Deleted for a limited period, but that is still a deletion workflow—not a storage-eviction workflow.
Remove Download solves the local-capacity problem without intentionally deleting the cloud item.
Before you use Remove Download
Do not rely only on the filename being inside iCloud Drive. First verify:
- the item is not Waiting to Upload;
- Finder reports an iCloud-backed state such as Downloaded or Keep Downloaded;
- the current version is visible where appropriate from another trusted iCloud view, such as iCloud.com, if the file is important;
- any application that is still writing to the file has finished saving.
If the file has not reached iCloud yet, the local copy is not disposable.
Check Keep Downloaded when one folder refuses to shrink
A common edge case is that Optimize Mac Storage works generally, but one large folder never gives space back.
Apple now exposes Keep Downloaded on iCloud Drive items. When that state is set, the item is deliberately pinned to the Mac even if it is old and the system needs more storage.
To remove the pin:
- Open Finder → iCloud Drive.
- Control-click the file or folder.
- Choose Keep Downloaded so the checkmark is removed.
Removing the pin does not itself guarantee immediate eviction. It returns the item to normal automatic storage management. If you want the local copy removed now and the item is confirmed in iCloud, use Remove Download.
How to verify
After the action:
- the item should remain visible in iCloud Drive;
- its status should no longer indicate a downloaded local copy;
- opening it again should require a download if the local content was successfully evicted;
- Mac free space should increase by approximately the size of the removed local content, allowing for filesystem accounting and other system activity.
Do not use a single Finder window's apparent folder size as the only proof. The operational proof is that the item remains in iCloud while the local downloaded state is removed.
Desktop & Documents can make this feel more confusing than ordinary iCloud Drive
When Desktop & Documents Folders is enabled for iCloud Drive, the familiar Desktop and Documents paths become part of the synchronized iCloud namespace.
That creates two common mistakes.
Mistake 1: deleting a Desktop file to free only this Mac
If the file is in the iCloud-backed Desktop or Documents folder, Delete is a synchronized deletion. Apple explicitly states that deleting one of these files on one device deletes it on the other devices signed in to the same Apple Account.
If your goal is only to free local storage, use Remove Download after confirming the item is in iCloud.
Mistake 2: dragging a file out of iCloud Drive and assuming it remains in iCloud
Apple's current Mac guide says that dragging an item from iCloud Drive to another local Finder location copies it to the Mac and removes it from iCloud Drive on devices using iCloud.
That can be exactly what you intend when moving a file back to local-only storage—but it is not equivalent to Remove Download.
The three operations therefore mean different things:
| Action | Local result | iCloud result | Correct use |
|---|---|---|---|
| Remove Download | Removes downloaded local content | File remains in iCloud | Free Mac storage while keeping cloud copy |
| Delete | Removes file locally | Synchronized deletion propagates | Intentionally remove the file |
| Move out of iCloud Drive | Creates/keeps local copy outside iCloud namespace | Item is removed from iCloud Drive | Convert cloud-managed file to local-only file |
That table is the safety boundary. Do not substitute one operation for another just because all three appear to “make the iCloud Drive folder smaller.”
Waiting to Upload is the state where storage cleanup becomes dangerous
If Finder shows Waiting to Upload, Apple says the item is not yet stored in iCloud.
This can happen for several reasons, including iCloud storage being full. Apple's Mac guide notes that when a document cannot be saved to iCloud Drive because iCloud storage is full, the document stays on the Mac and uploads when space becomes available.
That is a fundamentally different incident from “downloaded files are consuming too much SSD.”
Do not do this
Do not delete the local file, move it to Trash, disable iCloud Drive, or assume that another device can recover it until you have confirmed a current remote copy exists.
For an important file, create an additional local safety copy outside the synchronized iCloud Drive path before troubleshooting the upload state.
Then solve the reason the file is not reaching iCloud: cloud quota, account state, connectivity, file eligibility, or a sync problem.
This is also why Cloud Backup vs Cloud Storage matters. A file sitting in a synchronized folder is not equivalent to a confirmed independent backup copy.
Optimize Mac Storage and iCloud storage quota are two different capacity problems
There are two meters that users often collapse into one:
- Mac local storage — SSD capacity on the device;
- iCloud storage — the remote account quota shared by iCloud services.
Optimize Mac Storage helps manage local pressure by allowing eligible local copies to be removed while keeping cloud copies available.
It does not create more iCloud quota.
If Finder shows Out of Space for an iCloud item, the remote storage problem must be resolved before that item can be safely considered cloud-backed. Apple notes that iCloud Drive shares the account's iCloud storage with other services such as iCloud Photos, device backups, Mail attachments and more.
So a 256 GB Mac with 80 GB free and a completely full iCloud account can still fail to upload files. Conversely, a Mac with a nearly full SSD and plenty of iCloud quota can have a purely local download-state problem.
Diagnose the meter before choosing the fix.
A practical 2 a.m. diagnostic sequence
If iCloud Drive appears to be taking too much Mac storage, use this order:
- Open Finder → iCloud Drive and enable the iCloud Status column.
- Identify the large items that are Downloaded or Keep Downloaded.
- Separate them from Waiting to Upload or Out of Space items. Those need sync/quota diagnosis first.
- Confirm important current versions exist in iCloud before evicting local copies.
- Remove Keep Downloaded if the item is unnecessarily pinned.
- Use Remove Download on confirmed cloud-backed items when you need local space immediately.
- Do not Delete unless the intention is to remove the file from the synchronized iCloud Drive namespace.
- Do not move items out of iCloud Drive unless you intentionally want them to become local-only and disappear from iCloud Drive.
- Recheck Mac free space and the Finder iCloud status after the operation.
Success is not merely “the SSD number went down.” Success is all three of these being true:
- the intended file still exists in iCloud;
- Finder no longer keeps the full local download where you did not want it;
- no important file is left in a Waiting to Upload state without another safe copy.
What not to do
Do not assume Optimize Mac Storage is broken because nothing changed immediately
Apple's own documentation makes the feature conditional on local space pressure. Immediate eviction is not the promised behavior.
Do not empty local storage by deleting synchronized files
Deleting from iCloud-backed Desktop, Documents, or iCloud Drive propagates through the synchronized account. That is a data-management action, not a local-cache action.
Do not remove a file that is still Waiting to Upload
Until the upload succeeds, the Mac may contain the only current copy.
Do not sign out of iCloud just to force an eviction
Signing out changes the account and synchronization state far more broadly than necessary. Apple provides per-item download controls specifically so a local-space incident does not need to become an account-reset incident.
Do not confuse moving out of iCloud Drive with Remove Download
Moving out changes where the authoritative file lives. Remove Download changes only whether a local downloaded copy is retained.
The mechanism to remember
The simplest reliable model is:
Cloud presence and local persistence are separate dimensions.
A file can be safely in iCloud and still be fully downloaded on the Mac. A file can be visible inside iCloud Drive but still be waiting to upload. A file can be intentionally pinned with Keep Downloaded. And a cloud-backed file can have its local content removed without deleting the cloud item.
That is why “iCloud Drive is taking space” is not one technical state.
The diagnostic question is:
Which files are locally persistent by policy, which are locally persistent because macOS has not needed to evict them yet, and which are local because they have not successfully reached iCloud?
Once you answer that, the fix becomes narrow and safe.
Related technical reading
- Google Drive Streaming Still Using Disk Space? — the equivalent local-persistence problem in Google Drive for desktop.
- How pCloud Drive Cache Actually Works — how a virtual drive can still consume local storage through cache and offline access.
- Cloud Backup vs Cloud Storage — why synchronized presence should not be confused with independent recovery protection.
- Cloud Storage vs External Hard Drive — useful when the real issue is whether the archive should live on the Mac, in the cloud, or on separate local storage.
- Google Drive Storage Full — another example of separating remote quota from local disk pressure before deleting files.
Reverse internal link suggestions
When this batch publishes, add contextual links to this article from:
/articles/cloud-storage-vs-external-hard-drive/— in the section discussing local SSD pressure and cloud-only storage./articles/backup-vs-cloud-storage/— where sync-state confirmation and local-only unsynced files are discussed./articles/pcloud-drive-cache-explained/— in the cross-provider explanation of cloud visibility vs local persistence./articles/google-drive-streaming-uses-disk-space/— as the iCloud equivalent of streamed/cloud-only files still interacting with local storage.
Image metadata
1. Hero / storage-state model
- Purpose: Separate cloud-only, downloaded, Keep Downloaded, and Waiting to Upload states.
- Filename:
icloud-optimize-storage-state-model.svg - ALT:
iCloud Drive storage-state model showing cloud-only, downloaded, keep downloaded and waiting to upload files on a Mac - Caption:
Optimize Mac Storage only makes sense after you know whether a file is safely in iCloud or still depends on the Mac copy. - Placement: After introduction.
- Source: Original CloudScope diagram derived from Apple-documented Finder states.
- Dimensions: 1200 × 760.
2. Optimize vs Remove Download
- Purpose: Explain automatic pressure-based optimization versus an explicit per-item local eviction.
- Filename:
icloud-optimize-vs-remove-download.svg - ALT:
Decision tree comparing Optimize Mac Storage with Remove Download for reclaiming local Mac storage - Caption:
Optimize Mac Storage is automatic and pressure-driven; Remove Download is the direct per-item action when the cloud copy is confirmed. - Placement: After mechanism explanation.
- Source: Original CloudScope diagram based on Apple Support documentation.
- Dimensions: 1200 × 760.
3. Safe local-space recovery sequence
- Purpose: Prevent accidental synchronized deletion while freeing disk space.
- Filename:
icloud-safe-local-space-recovery.svg - ALT:
Safe sequence for freeing Mac storage from iCloud Drive while preserving the cloud copy - Caption:
Verify remote state first, then change only the local-download state. - Placement: Beside the 2 a.m. diagnostic sequence.
- Source: Original CloudScope diagnostic diagram.
- Dimensions: 1200 × 760.
CTA
Commercial CTA: None. This is a low-commercial-intent incident-response article. The correct next action is diagnosis and safe local-space recovery, not switching providers.
Sources and verification
CloudScope checked these primary Apple sources on 21 August 2026:
- Apple Support — Store files in iCloud Drive on Mac: https://support.apple.com/guide/mac-help/mchle5a61431/mac
- Apple Support — Work with folders and files in iCloud Drive: https://support.apple.com/guide/mac-help/mchl1a02d711/mac
- Apple Support — Check your iCloud Drive file and folder status on Mac: https://support.apple.com/guide/mac-help/mchlc994344b/mac
- Apple Support — Add your Desktop and Documents files to iCloud Drive (published August 3, 2026): https://support.apple.com/109344
- Apple Support — Turn off Desktop & Documents Folders on your Mac (published April 20, 2026): https://support.apple.com/126628
Source-backed facts used in this draft
- Apple states that Optimize Mac Storage can automatically keep older documents in iCloud when more space is needed, and that if space is not needed, the full contents of iCloud Drive remain on the Mac.
- Apple documents Finder states including In iCloud, Downloaded, Keep Downloaded, Waiting to Upload, and Out of Space.
- Apple documents Remove Download as the action for removing a local download while keeping the item in iCloud Drive.
- Apple states that deleting a file from iCloud-backed Desktop & Documents on one device deletes it on the other devices using the same Apple Account.
- Apple states that moving an item out of iCloud Drive to a local Finder folder removes it from iCloud Drive across devices configured for iCloud.
- Apple states that when iCloud storage is full, a document that cannot be stored in iCloud Drive can remain on the Mac and upload later when storage becomes available.
No undocumented Apple implementation details or invented cache paths are asserted in this article.