iCloud is not a backup.

The mirror problem

Here is a quick test. Open Finder. Delete a file from your Desktop. Empty the trash. Now open iCloud.com on your phone. Is the file there?

It is not. Or if it is, it will be gone within seconds. That is because iCloud Drive is a mirror. What happens on your Mac happens in iCloud. What happens in iCloud happens on your other devices. The mirror is the whole point: you start something on your Mac and pick it up on your iPad. That is what sync does and iCloud does it well.

The problem is a mirror cannot protect you from yourself. Delete a file and the mirror deletes it everywhere. An app corrupts a document and the corrupt version overwrites the good one in iCloud and on every other device. Ransomware rewrites your files with encrypted garbage and iCloud faithfully copies the garbage to the cloud and out to every signed-in device.

By the time you notice what happened, the good version is gone. Not archived somewhere. Gone.

What about version history?

iCloud and Dropbox both offer version history. For individual files, you can often go back 30 days and recover an earlier version. That sounds like a safety net.

It is a limited one. A few things version history does not do:

• → Restore a whole Mac. Version history is per file. Recovering your apps, preferences, and system state from sync version history is not how it works.
• → Cover everything. Files outside your synced folders are not in version history at all. Your Downloads folder, your Desktop (if you did not opt into that sync option), your apps, your system preferences: not covered.
• → Scale to a ransomware event. If ransomware rewrites thousands of files, going through version history file by file is not a realistic recovery path. You need a point in time snapshot of the whole disk, from before the attack.
• → Survive cancellation. If you stop paying for iCloud storage, the version history goes with it. A real backup on your own hardware is still yours when the subscription ends.

Version history is a convenience feature. It will save you from "I overwrote a file and need yesterday's version." It will not save you from "my Mac needs to be restored from scratch."

"But I pay for 2TB of iCloud storage"

Storage capacity and backup coverage are different things. You can fill 2TB of iCloud with synced files and still have no backup. The files are there. But there is no point in time snapshot, no system state, no independent copy that exists outside of what iCloud decides is the current version.

There is also a naming thing that trips people up. Apple has a service called iCloud Backup. It backs up your iPhone and iPad over WiFi, automatically. It is genuinely good at that job.

Your Mac is not covered by iCloud Backup. Your Mac has iCloud Drive, which syncs files. These are different products with similar names. I have met people who believed their Mac was backed up to iCloud because their iPhone was. It is not a crazy assumption. It is just wrong.

What a real backup looks like

A real backup takes a snapshot of your entire Mac at a point in time. Every file, every preference, every piece of state that makes your Mac yours. It keeps that snapshot intact, independent of what happens afterward.

Here is the technical thing that makes this work: a good backup app writes each snapshot as a full browsable copy of your Mac, but uses hardlinks for files that have not changed between snapshots. Two snapshots that share 90% of the same files do not store that 90% twice. The hardlinked files point to the same data on disk. Only the changed files consume new space.

What this gives you is a library of independent, fully readable snapshots. You can open the snapshot from last Tuesday like a folder. Navigate to any file. Drag it out. No restore wizard. No decryption process you have to remember how to do. Your files, organized the way they were last Tuesday, available to you today.

That is what makes backup useful in an emergency. Not a file browser you have to use per-file, but a full copy of yesterday you can walk into and retrieve whatever you need.

What I actually do

I use iCloud Drive. I use it for the reason it exists: working across devices. A note I start on my Mac is on my iPhone by the time I leave my desk. A file I put in a shared iCloud folder is available to the people I share it with. That is useful and I am not going to stop using it.

But I also run Back That Data Up, the app I built precisely because iCloud is not a backup. The feature I am most proud of: you can lock the backup with a FIDO hardware key such as a Yubikey. The backup stays sealed against anyone who does not have the physical token. No other major Mac backup app does this. BTDU also does anomaly aware backups: it watches the FSEvents stream for the patterns of rapid, uniform file rewrites that mass corruption events produce, and pauses before damaged files can overwrite clean snapshots. And because I care about what happens if the drive is stolen along with my Mac, Cloud Vault sends encrypted copies of my most important files to Dropbox, in a format that only my Mac can open.

iCloud handles sync. BTDU handles backup. They are not competing. They run side by side.

Who is most at risk from this confusion

The honest answer is: almost everyone. The iCloud-as-backup misconception is extremely common, including among people who consider themselves technically sophisticated. But the consequences vary.

The people who are most exposed:

• → Freelancers and small business owners whose files are their business. Client work, contracts, invoices, years of correspondence. If that disappears, the business has a problem.
• → Photographers and video editors with large libraries. A decade of RAW files is not going to fit in version history recovery. You need a snapshot.
• → Anyone working on files that are hard to reconstruct: original writing, design work, code built over years, personal records. Once they are gone, they are gone.
• → People who have been trusting iCloud as backup for years and have never had a reason to test whether it actually protects them.

The frustrating thing about this category of problem is that you only find out if you are in it when something goes wrong. The backup question feels abstract until the moment it is urgent.

What to do today

If you are leaving this post with the understanding that iCloud does not back up your Mac, here is the practical next step.

Get a backup drive. The simplest backup is Time Machine pointed at a nearby external drive. Time Machine is free, it comes with your Mac, and a working backup at any fidelity is better than no backup. Get a drive and turn it on today.

After that, think about whether you need more. If you want hardware key encryption, anomaly aware backups, an off-site encrypted copy in the cloud you already pay for, or simply more control than Time Machine offers, that is where BTDU fits. But start with any real backup today.

Sync is not a backup. Today is the day to stop treating it like one.