Mac

Optimize Mac Storage: the iCloud backup trap

Why 'Optimize Mac Storage' can leave your Time Machine backup full of empty placeholders instead of real files — how iCloud dataless files work, whether Time Machine backs up iCloud, and the safe settings.

Problem summary

I'm here because I'm not sure whether my files are actually safe — I use iCloud Drive (maybe Desktop & Documents too) with 'Optimize Mac Storage' on, and I want to know if Time Machine is really backing them up. Here's the trap: Optimize Mac Storage replaces files you haven't used recently with empty placeholders that download on demand, and Time Machine can only back up what's physically on the disk. So your local backup can be full of stubs, not data. This page explains exactly how that works and the settings that keep your files genuinely protected.

Operator snapshotEvidence first

First proof

Check whether 'Optimize Mac Storage' is on for iCloud.

Screen to open

brctl status

Expected signal

Off (everything kept local) means Time Machine backs up real data.

Stop boundary

Assuming Time Machine protects optimized iCloud files (it backs up stubs).

Layer path

1Two facts collide into the trap. First, 'Optimize Mac Storage' replaces older iCloud files with dataless placeholders — stubs that download on demand and occupy almost no local space. Second, Time Machine backs up the bytes physically on disk. A placeholder has no bytes, so Time Machine backs up the stub, not the file.

2The consequence is a local backup that looks complete but isn't: optimized files are present as icons yet absent as data. The gap only bites optimized files — anything currently downloaded is backed up normally — so the risk scales with how aggressively macOS has optimized, which rises as the disk fills.

3Underneath sits the bigger framing: iCloud Drive is sync, not backup. The live copy lives in iCloud; recoverable history must come from Time Machine (of real local data) plus a cloud backup. Resolving the trap means making important files local (so Time Machine captures them) or explicitly designating the cloud copy as their authoritative backup.

Runbook

Step-by-step runbook

Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.

Understand the mechanism

Check: Optimize Mac Storage leaves dataless placeholders; Time Machine backs up bytes.

Expected result: You see why optimized files aren't truly backed up locally.

If not: Downloaded files are fine; placeholders are the gap.

Find the placeholders

Check: Spot cloud icons in Finder / check local sizes.

Expected result: You know which files are stubs.

If not: If none, files are local for now — re-check as the disk fills.

Make critical files local

Check: Download Now the important files, or turn off Optimize (disk permitting).

Expected result: Time Machine captures real data for what matters.

If not: If the disk is too small, make the cloud copy authoritative.

Place iCloud correctly

Check: Treat iCloud as sync; keep Time Machine + cloud backup as real recovery.

Expected result: A synced deletion has a safety net.

If not: Don't count iCloud as the backup.

Verify with a restore

Check: Restore an optimized file's data and confirm it's content, not a stub.

Expected result: You've proven the trap isn't silently affecting you.

If not: If you get a stub, fix the setting or rely on the cloud copy.

Decision tree

If: Optimize Mac Storage on, disk near-full, important files show cloud icons.

Then: Your local Time Machine is backing up placeholders, not data.

Action: Turn off Optimize (if disk allows) or Download Now the critical files so Time Machine captures them.

If: Optimize on but disk has ample free space.

Then: Files are likely still local for now, but the risk is latent.

Action: Keep an eye on free space; downloading-critical-files or disabling Optimize removes the risk.

If: About to sign out of iCloud / erase / migrate.

Then: Placeholders won't carry real data through a local backup/restore.

Action: Download everything first, then proceed.

If: iCloud is the only 'backup'.

Then: Sync has no versioned recovery for deletions/corruption.

Action: Add Time Machine + a cloud backup; keep iCloud as the live copy.

If: Disk too small to keep everything local.

Then: You can't both optimize and have Time Machine hold all data.

Action: Designate the cloud service's backup/versioning as authoritative for optimized files; keep must-have-local files downloaded.

Evidence

Evidence table

Symptom	Evidence to collect	Likely layer	Next action
Restored an iCloud file from Time Machine and got an empty stub.	File was a dataless placeholder when backed up.	Optimize Mac Storage + Time Machine gap.	Download the file; disable Optimize or rely on the cloud copy.
Files show a cloud/download icon.	They're optimized placeholders, not local.	Dataless materialization.	Download Now what matters; reconsider Optimize.
Important folders (Desktop/Documents) are mostly placeholders.	Desktop & Documents in iCloud + Optimize on.	Same trap at folder scale.	Keep those folders downloaded, or make cloud the authoritative backup.
Deleted iCloud file is gone with no recovery.	iCloud treated as backup.	Sync, not backup.	Add real backups (Time Machine + cloud).
Optimization kicked in suddenly.	Disk filled and macOS started removing local copies.	Capacity-driven optimization.	Free space or rely on the cloud copy for those files.

Reference

Commands and settings paths

Inspect iCloud local sync state

brctl status

Where: Terminal on the Mac.

Expected: Shows iCloud (CloudDocs) sync/eviction activity and local materialization.

Failure means: Heavy eviction means files are being turned into placeholders.

Safe next step: Download critical files or disable Optimize Mac Storage.

Find dataless placeholder stubs

find ~/Library/Mobile\ Documents -size -1c 2>/dev/null | head

Where: Terminal on the Mac (placeholders report near-zero local size).

Expected: Lists files with almost no local bytes — likely placeholders.

Failure means: Many hits means much of iCloud isn't local (so not in Time Machine).

Safe next step: Download what you need guaranteed-local.

Force a real local copy

Finder → right-click the file → Download Now

Where: Finder on the Mac.

Expected: Materialises the file's bytes locally so Time Machine can back it up.

Failure means: If it won't download, check network/iCloud sign-in.

Safe next step: Re-run Time Machine afterward to capture the real data.

Hardware boundary

Hardware and platform boundary

Change only when

Move to a larger internal disk (next Mac) if you want everything kept local AND iCloud convenience — Apple Silicon storage isn't upgradeable later.
Add a cloud backup with versioning so optimized files have a real recovery path even when they're not local.

Evidence that matters

Enough internal storage to keep important files local so Time Machine captures them.
A real cloud backup (with history) as the authoritative copy for optimized files.
Clarity about which copy is authoritative for each file.

Evidence that does not matter

iCloud storage tier as 'backup size' — iCloud is sync, not backup.
Apparent folder sizes in Finder — placeholders understate real data.
The convenience of Optimize over the integrity of your backup, on a Mac you rely on.

Avoid

Assuming Time Machine protects optimized iCloud files (it backs up stubs).
Treating iCloud Drive as a backup.
Signing out / erasing / migrating with important files still placeholders.

Related tool/checklist

Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.

Backup plan builder

Last reviewed

2026-06-02 · Reviewed by HomeTechOps. Reviewed against Apple's 'Optimize storage space' and Time Machine documentation; explains why dataless iCloud placeholders aren't captured by Time Machine (it backs up local bytes), and resolves the trap by keeping important files local or designating the cloud copy as authoritative — while reinforcing that iCloud Drive is sync, not backup.

Sources/assumptions

Assumes a Mac (including macOS Tahoe / macOS 26) using iCloud Drive (optionally Desktop & Documents) with Optimize Mac Storage available.
Time Machine backs up locally-present file data; dataless iCloud placeholders have no local content to capture.
iCloud Drive is a sync service, not a versioned backup; recoverable history comes from Time Machine and a cloud backup.

Source-backed checks

HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.

Apple Support: Optimize storage space on your MacUsed for how 'Optimize Mac Storage' keeps only recently-used iCloud files locally and replaces the rest with dataless placeholders downloaded on demand — which Time Machine cannot back up because no local content exists.Apple Support: Back up your Mac with Time MachineUsed for the supported Time Machine setup, choosing a backup disk, and that macOS backs up over SMB to a network disk (the sparsebundle model) on modern macOS.Apple Support: Free up storage space on MacUsed for the native Storage settings breakdown (System Data and other categories) and Apple's supported ways to reclaim space without third-party cleaner apps.

Diagnostic rule

1. Check the simplest signal first.
2. Change one thing at a time.
3. Avoid unsafe electrical or data-loss steps.
4. Stop when the evidence says the risk moved.

FAQ

Does Time Machine back up my iCloud files?

Only the ones currently stored locally. Time Machine backs up the bytes on your disk, and if 'Optimize Mac Storage' has replaced a file with a dataless placeholder, there are no bytes to back up — Time Machine saves the stub, not the content. Files you keep downloaded are backed up; optimized placeholders are not.

Should I turn off 'Optimize Mac Storage'?

On a Mac you rely on as the home of important files, yes — if the disk has room. Turning it off keeps everything downloaded locally, so Time Machine captures real data instead of placeholders. If the disk is too small, keep Optimize on but make sure critical files are downloaded and that a cloud backup is your real recovery for the rest.

How do I tell if a file is a placeholder or a real local copy?

In Finder, optimized files show a small cloud/download icon. Right-click → Download Now (or just open the file) forces a real local copy. You can also compare a folder's apparent size to actual on-disk usage — placeholders take almost no local space.

Is iCloud Drive a backup?

No — it's sync. If you delete a file it's removed everywhere, and there's no deep version history like a real backup. Keep iCloud as the live copy, and rely on Time Machine plus a cloud backup for recoverable history. See the 3-2-1 backup plan for how the pieces fit together.