Use case · August 10, 2026

Back up iCloud Drive to an external SSD on a Mac

iCloud Drive keeps your files in sync — it does not keep them safe. A deletion, a bad edit or a hijacked account propagates to every device within minutes. Here is why sync is not backup, and how to get a real, verified copy of your iCloud files onto a drive you physically own.

Why iCloud Drive is not a backup

iCloud Drive is a synchronization service. Its whole job is to make every device show the same state: edit a document on your Mac and the edit appears on your iPhone; delete a folder on your iPad and it disappears from your Mac. That is exactly what you want from sync — and exactly what you do not want from a backup.

A backup is an independent copy that does not change when the original does. Sync fails you in precisely the moments a backup exists for:

  • Deletions propagate. Remove a file anywhere — on purpose, by accident, or by a misbehaving app — and iCloud faithfully removes it everywhere. "Recently Deleted" holds items for about 30 days; after that they are gone from every copy at once.
  • Corruption propagates. If a file is damaged or overwritten with a bad version, the damaged version syncs. Ransomware that encrypts your Documents folder syncs the encrypted files upward just as happily.
  • Your account is a single point of failure. Locked out, phished, or billing lapsed — whatever the cause, if the account is unreachable, so is every "copy," because they were never independent copies at all.

None of this is a flaw in iCloud. It is what sync means. The fix is not to abandon iCloud Drive but to add the thing it deliberately is not: a periodic, offline, verified copy on a drive that sits in your desk drawer and answers to nobody's account.

The catch: many of "your" files are not on your Mac

Here is where most people's backup attempt quietly goes wrong. macOS ships with Optimize Mac Storage enabled, which means macOS evicts the local bytes of files you have not touched recently and leaves a small placeholder — the file you see in Finder with a little cloud icon next to it. The listing looks complete, but for a chunk of your library the actual data lives only in Apple's data center.

Copy that folder to an external SSD and one of two things happens: Finder downloads each cloud-only file mid-copy — which can take hours and stall partway through a large library — or, with some tools, you copy placeholders and end up with a "backup" that contains no data. Either way, you rarely get a clear record of what actually made it across.

So a real iCloud backup is a two-step job: first make sure every file's bytes are actually on the Mac, then copy them to the external drive — and verify the copy. That is the pipeline MacManager was built around.

How MacManager does it: see the state, download, copy, verify

MacManager is a native file explorer and control centre for macOS (14 or later), and its iCloud Manager treats cloud state as a first-class fact rather than a decoration:

  • See the truth first. The iCloud Manager shows true per-file cloud state — cloud-only, queued, downloading, stale, conflicted, current — across your iCloud Drive, plus a live activity map of your iCloud services. Before you back anything up, you can see exactly which files exist only in the cloud.
  • Bring the bytes down in bulk. Bulk Download Now pulls cloud-only files onto the Mac, so you are not clicking through folders one placeholder at a time.
  • Copy to the SSD, verified. The backup pipeline copies your iCloud content to the external SSD with SHA-256 checksums on the copied files, so "it copied" means "the bytes on the SSD match." If you unplug the drive or stop halfway, it resumes cleanly instead of starting over.
  • Audit it afterwards. Every bulk operation writes to a durable local journal, so you can check later what was copied and when — useful when the backup is the thing you will one day rely on.

The same engine backs the app's Migration Assistant, which accepts iCloud Drive as a source alongside another Mac, a PC folder or a Time Machine folder — that is the cloud-to-SSD route, with collision handling, symlink preservation and idempotent resume. And like everything in MacManager, it all runs on-device: no account, no server, no file telemetry.

Practical rhythm: plug in the SSD, run the backup, unplug it. Repeat monthly, or after any big import (a photo dump, a finished project). An offline drive cannot be reached by ransomware or an account compromise — that is the point of it.

The alternatives, honestly

You do not strictly need an app for this, so here is a fair comparison:

  • Manual Finder copy. Free and built in. Right-click your iCloud Drive folders, choose Download Now, wait for every cloud icon to disappear, then drag the folders to the SSD. It works for small libraries. The weaknesses: Finder does not show you a per-file inventory of what is still cloud-only, large copies can fail partway with no record, nothing verifies that the copied bytes match, and you will do all of it again by hand next month.
  • rsync in Terminal. Free, scriptable and genuinely good at incremental copies — subsequent runs only copy what changed. But rsync knows nothing about iCloud: it cannot trigger downloads of evicted files, so anything cloud-only is silently skipped or copied as a stub. You must force a full download first and keep it downloaded, and you are on your own for verification flags, exclusions and reading the output.
  • Time Machine. Excellent as a whole-Mac backup, and you should probably run it too — but it only captures iCloud files whose bytes are local, so with Optimize Mac Storage on, evicted files are backed up as placeholders.

MacManager's case is the combination: the visibility (which files are actually local), the bulk download, the checksum-verified copy and the resume, in one pass you can rerun without ceremony. If your library is a few gigabytes and fully downloaded, Finder is honestly fine. If it is hundreds of gigabytes, partly cloud-only, and the backup matters, verification and resumability stop being niceties.

Frequently asked questions

Isn't iCloud Drive already a backup?

No. iCloud Drive is a sync service: it keeps every device showing the same state. Delete or corrupt a file on one device and that change propagates everywhere. A backup is an independent copy that does not change when the original does — which is exactly what a copy on an external SSD gives you.

Why can't I just drag my iCloud Drive folder onto the SSD in Finder?

You can, but with "Optimize Mac Storage" on, many files are cloud-only placeholders. Finder must download them mid-copy, and a large copy can stall or fail partway with no record of what made it across. MacManager shows the true per-file cloud state first, downloads what is missing, and verifies every copied file with SHA-256 checksums, resuming cleanly if interrupted.

Does Time Machine back up iCloud Drive?

Only the files whose bytes are actually on your Mac. Cloud-only files evicted by Optimize Mac Storage are placeholders on disk, and placeholders are what get backed up. To capture everything, the files must be downloaded first — which is the step MacManager's iCloud Manager makes visible and does in bulk.

How big an external SSD do I need?

At least as large as the iCloud storage you actually use, with headroom. Check your usage in System Settings, then round up — a 1TB SSD comfortably covers a 200GB iCloud plan and leaves room for future runs. The drive should be formatted APFS or Mac OS Extended.

Get the app

MacManager is a native Swift 6 app for macOS 14+, distributed directly on this site as a fully activated download supported by a donation — no account, no subscription, nothing locked. Donate and download MacManager, or read the full product page first.

Related reading