Your cloud sync is not a backup — and the difference can cost you everything

Dropbox, Google Drive, and OneDrive are brilliant at keeping your files in sync across every device. That is exactly why none of them is a backup — and why people lose everything believing otherwise.

The most expensive misunderstanding in cloud storage

Ask around and almost everyone will tell you they are "backed up." Their files are in Google Drive, or Dropbox, or OneDrive — synced, in the cloud, safe. Right?

Sync and backup feel like the same thing. They are not, and the gap between them is where data goes to die. Spend an hour reading r/DataHoarder, r/Backup, or r/cloudstorage and the same gut-punch repeats: "LOST MY HDD — storage alternatives pls." "Lost all my data. About 30TB." People who genuinely believed their setup would save them, finding out at the worst possible moment that it would not.

Here is the distinction in one line: sync keeps every copy identical; backup keeps old copies safe. Those goals are opposites — and the second one is the one that saves you.

Why sync can't save you

A sync service has exactly one job: make every location match. Change a file on your laptop and the new version is pushed everywhere in seconds. That is the magic — and the trap.

Because sync is faithful, it faithfully copies your mistakes:

• Delete a file and it disappears from the cloud and every other device. ("I deleted it from the cloud and it vanished off my phone" is one of the most common complaints in cloud-storage forums.)
• Corrupt a file — a bad save, a flaky drive — and the corruption syncs straight over your good copy.
• Get hit by ransomware and it is worse: the malware encrypts your files, your sync client sees "changed files," and dutifully uploads the encrypted versions, overwriting the good ones in the cloud within minutes.

"But Dropbox keeps version history." It does — for a limited window, usually around 30 days, and only if you catch it in time. Version history is a nice undo button, not a backup. And it does nothing about the failure mode that wipes out everything at once: losing the account itself. One r/pcloud user described paying for a lifetime plan and then watching the account get "deleted — no warning, no nothing," taking the files with it. When the live copy and the "backup" live in the same account, one billing dispute, lockout, or provider decision takes both.

What a real backup actually is

Backup people have a rule that has been around for decades — the 3-2-1 rule: at least 3 copies of your data, on 2 different kinds of media, with 1 kept off-site and separate. The whole point is that no single event — a dead drive, a wrong click, a ransomware hit, a closed account — can reach all your copies at once.

A real backup has properties sync does not:

• It is versioned. You can restore the file as it was last Tuesday, not just however it looks right now.
• It is separate. It lives somewhere your everyday machine and sync clients cannot silently overwrite.
• It is immutable, ideally. The strongest backups are written to storage with object-lock — once a backup is written, nothing can alter or delete it for a set period, not even stolen credentials. That is what "ransomware-safe" actually means.
• It is restore-tested. A backup you have never restored is a hope, not a backup. Can I actually get my files back? is the one question most people never check until it is too late.

If you take away one thing: a copy that updates itself to match the original is not protecting you from anything that happens to the original.

How Whimsy does backup

This distinction is exactly why we built real backup into Whimsy — and why it is a separate thing from the everyday cloud-to-cloud moving Whimsy already does.

A few deliberate choices:

• It runs on your machine, not our servers. Whimsy's desktop connector does the backup work locally and sends the data directly from your computer to your storage. Our servers schedule it, watch its health, and orchestrate restores — but they never touch your file contents. The "we never see your files" promise holds for backup too.
• It writes to immutable storage. Backups go to object stores with native object-lock — S3, Cloudflare R2, Backblaze B2, Wasabi, Azure, GCS — so a backup, once written, cannot be silently encrypted or deleted. That is the ransomware-safe part, and it is why we refuse to call a synced Dropbox folder a "backup."
• It is versioned and restore-first. You can browse a point in time and pull back a single file, a folder, or your whole library — and we spend most of the effort on the boring, critical part: proving a backup can actually be restored.
• We orchestrate a proven engine. Backup is a pure trust product, so we wrap a mature, years-hardened open-source backup engine (Kopia) rather than inventing our own snapshot format. A clever format with a restore bug is worse than no backup at all.

We even renamed Whimsy's old "Backup" automation to "Scheduled copy," because that is what it always was — a copy, not a backup. The word "backup" now means the real thing.

What it is — and isn't (honestly)

Today, Whimsy's backup protects the files on your computer and connected NAS, sent to immutable cloud storage you control. Backing up one cloud account to another is still a scheduled copy for now, not a true versioned backup — we would rather tell you that plainly than blur the line we just spent an article drawing.

We are in free early access and building this in the open, with the next stretch aimed at the people who feel backup pain hardest — photographers and video editors sitting on terabytes of irreplaceable footage on a single drive "knowing it is risky."

So, a genuine question: what would make you trust a backup enough to stop worrying? Test restores you can watch run? A clear "you are safe" health dashboard? Cheaper cold storage for old projects? Tell us in the comments — we are building from real answers.

Whimsy is in free early access at whimsy.numeracode.com. Move files between clouds byte-direct, find the duplicates hiding across all of them, and — now — back up what you cannot afford to lose to storage that cannot be silently erased.