Guide

iCloud “Optimize Mac Storage” and Your Backups

Turning on Optimize Mac Storage frees up disk space by leaving placeholder files behind. Most backup tools handle those placeholders badly — quietly, not obviously. Here's what's actually happening, and what to check before you trust a backup tool with an iCloud-heavy Mac.

Updated August 9, 2026.

Key takeaway

Optimize Mac Storage evicts file content from your disk and leaves a placeholder behind. Many backup tools either skip these placeholder files or copy the near-empty placeholder instead of the real content — so it's possible to end up with only placeholders in two places, your Mac and your "backup," with the one real copy sitting in iCloud alone. ThirdCopy detects real dataless files, downloads only what a given run needs, copies the actual content, and re-evicts only what it downloaded — with guardrails so this never overloads a nearly-full disk.

What "Optimize Mac Storage" actually does

The setting lives at System Settings → Apple Account → iCloud → iCloud Drive. When it's turned on, files stored in iCloud Drive that you haven't opened in a while get evicted from your Mac's local disk to free up space. What's left behind is a dataless placeholder: it still shows up in Finder, still has the right name and icon, and still opens fine when you double-click it, because macOS quietly downloads it on demand at that point. But until you open it, the actual file content isn't on your disk — it exists in iCloud only. Finder marks these with a small cloud icon next to the filename, if you look closely, but it's easy to miss in a folder full of otherwise-ordinary-looking files.

Why this breaks backups quietly

Most backup and sync tools handle dataless files in one of two ways, and both are a problem if you're not expecting them. Some skip placeholder files entirely and just don't back them up. Others copy the placeholder itself — a stub with little or no actual data — as though it were the real file. The second case is the more dangerous one, because it looks like it worked: the file shows up in your backup with the right name and a plausible-looking entry, but if you ever actually needed to restore it, you'd get a broken or empty file, not your document.

Why do tools default to this rather than just downloading everything? Because the alternative has a real cost of its own. Optimize Mac Storage usually gets turned on precisely because a Mac has a small local disk and a large iCloud library. A backup tool that unconditionally force-downloads a user's entire iCloud Drive just to run a backup could fill that disk without warning, on a Mac that turned the setting on for exactly that reason. So being cautious by default — skipping or only partially handling iCloud placeholders — is generally intentional, industry-wide behavior, not a bug specific to any one product.

The real risk, stated plainly

If you're not careful, it's possible to end up with only placeholders in more than one place: the dataless placeholder on your Mac, plus a copy of that same near-empty placeholder in whatever you think of as your backup. The one real copy of your data — the actual bytes — is sitting in iCloud, and iCloud alone. That might be fine as a matter of pure data survival, but it isn't 3-2-1, and it isn't even really 2 independent copies. It's one copy in iCloud, with two decoys nearby that look like backups but aren't.

How ThirdCopy handles it

ThirdCopy detects dataless files properly — not by guessing from file size, but by checking the file system's own dataless-file flag together with iCloud's own download-status API for that file. That's the same signal macOS itself relies on, not a heuristic layered on top.

When a backup run actually needs a dataless file's content, ThirdCopy downloads (materializes) just that file, copies the real content to your destination, and then — the part most tools skip — re-uploads and re-evicts only the files it downloaded itself, best-effort, once the copy is done. Files you weren't already keeping local stay that way after the backup finishes; ThirdCopy doesn't leave your disk more full than it found it.

It also guards against a genuinely nasty failure mode: downloading a lot of iCloud content onto a disk that's nearly full can get an app silently terminated by macOS's own disk-space-reclaim system. ThirdCopy skips materializing files when free space is running low, and caps how much un-evicted data it will hold onto at once, degrading to skipping rather than risking that. Any files skipped this way are counted and reported to you in plain language — never silently.

What to check before you trust a backup tool with an iCloud-heavy Mac

Whether it explicitly downloads (materializes) dataless files before copying them — not just whether it "supports iCloud Drive," which is a much weaker claim that's compatible with silently skipping every placeholder.
Whether it cleans up after itself. A tool that materializes files but never re-evicts them will quietly fill your disk back up over repeated backups, undoing the reason you turned Optimize Mac Storage on.
Whether it protects against downloading onto a nearly-full disk, or whether it just tries and hopes, risking the kind of silent termination described above.
Whether skipped files are reported to you, or simply left out without a word.

If a vendor can't answer these specifically, assume the naive path is what's happening: files you think are backed up are either missing or present only as empty placeholders.

Questions

Does Time Machine back up iCloud placeholder files properly?

Time Machine's handling of iCloud Drive placeholder files isn't something Apple documents in much detail, and user reports on exactly what ends up in a Time Machine backup have been inconsistent over the years. The safe assumption is not to take it on faith: don't assume a dataless file's real content is sitting in your Time Machine backup just because the file appears to be included. If you rely heavily on Optimize Mac Storage, it's worth spot-checking that files you'd actually need are recoverable with real content, not just confirming they show up in the backup at all.

Will turning off Optimize Mac Storage fix backup problems?

In a blunt sense, yes — with it off, every file stays downloaded locally, so any backup tool that just walks the filesystem sees real files instead of placeholders, and the whole problem disappears. But that defeats the reason most people turn Optimize Mac Storage on in the first place: freeing up disk space when an iCloud library is bigger than the local disk. It's less a fix than a trade. A backup tool that handles dataless files properly lets you keep Optimize Mac Storage on and still get real file content in your backups.

What happens to my disk space if a backup tool downloads all my iCloud files?

If a tool force-downloads everything to back it up and never re-evicts it, your disk usage creeps back up toward wherever it was before you turned Optimize Mac Storage on — a real problem on a Mac with a small SSD. In a worse case, downloading a lot of content onto an already nearly-full disk can get an app terminated outright by macOS's own disk-space-reclaim system. A careful tool downloads only what a given backup run actually needs and re-evicts what it downloaded once it's done, so local disk usage ends up back where it started.

Try ThirdCopy free for 14 days — no card required.

Then $19.99 once. No subscription.