Most people believe their photos are backed up. What they actually have is a synced library, and the difference only becomes visible on the day something goes wrong.
It is a genuinely easy mistake to make. Apple and Google both use reassuring language: your photos are "in iCloud," and Google's feature was for years called "Back up and sync." Your photos sit on another company's servers, reachable from any device. That feels like a backup. It behaves like something else entirely.
This article explains the difference precisely, shows the failure modes sync does not cover, and lays out what a real backup of your phone actually looks like.
Is iCloud Photos a backup?
No. iCloud Photos is a sync service, not a backup service.
Its job is to keep your photo library identical everywhere you are signed in. Take a photo on your iPhone and it appears on your iPad and Mac. That is the feature working correctly. But the same mechanism runs in the other direction: delete a photo on your iPhone and it is removed from iCloud and from every other device on that Apple Account.
A backup does not behave that way. A backup is a copy taken at a point in time that stays as it was, regardless of what happens to the original afterwards. That independence is the entire point.
What is the difference between a backup and a sync?
Sync keeps two or more locations identical, so every change propagates, including deletions, edits, and corruption. A backup is an independent copy captured at a point in time, so it survives changes made to the original afterwards. Sync protects you from losing a device. A backup protects you from losing the data.
| Sync (iCloud Photos, Google Photos) | Backup (a copy you keep) | |
|---|---|---|
| Purpose | Keep devices matching | Preserve a copy that survives change |
| On deletion | Deletion propagates everywhere | Copy is unaffected |
| On accidental edit | Edit propagates everywhere | Earlier version is retained |
| History | Current state only | Point-in-time copy |
| If the account is lost | Library goes with it | Copy is still yours |
| Protects against | Losing or breaking a device | Losing the data itself |
Both are useful. They are answers to different questions. Sync answers "how do I reach my photos from anywhere?" A backup answers "what happens if these photos disappear?"
The trouble is that sync answers its question so well that people stop asking the second one.
What happens when you delete a photo from iCloud Photos?
It is removed from every device signed into that Apple Account, and it moves to Recently Deleted.
On iPhone and iPad, deleted photos sit in Recently Deleted for 30 days before they are removed permanently. In Google Photos, deleted items stay in the trash for 60 days.
That window is a real safety net, and it catches the most common mistake: deleting something and realising within the month. But it is a grace period, not an archive. It does not help with the deletion you did not notice, the one that happened eighteen months ago, or the one made by someone else with access to the account. And it runs on a clock you do not control.
The practical test: if the only copy of a photo is one that a single tap can remove from every device you own, you do not have a backup of it.
Isn't iCloud Backup a real backup?
This is the most important confusion to clear up, because the names are so close.
iCloud Backup and iCloud Photos are two different features. iCloud Backup captures your device — app data, settings, messages, and so on — so a phone can be restored. That genuinely is a backup of those things.
But here is the catch: if iCloud Photos is turned on, your photo library is not included in the iCloud Backup. Apple does not duplicate it, on the reasoning that the library already lives in iCloud. So the device backup you assume contains your photos very likely contains none of them.
The result is a gap that feels like coverage. iCloud Photos is not a backup, because deletions propagate. iCloud Backup would be a backup, but it excludes the photos. Both features are switched on, and the photo library still has exactly one live copy.
Worth checking too: if Optimize iPhone Storage is enabled, the full-resolution originals live in iCloud while your phone keeps smaller versions. In that configuration the device is not holding a complete copy either.
Does Google Photos work the same way?
Yes, for the same reason.
Google Photos syncs your library rather than preserving an independent copy, so deletions propagate from your phone to the service. The feature's long-standing name, "Back up and sync," describes uploading from the phone to Google, not archiving against loss. Deleted items go to the trash for 60 days and are then removed.
The account dependency is the same as well. Google's free tier is 15 GB shared across Gmail, Drive, and Photos, and losing access to the Google account means losing the library with it.
None of this makes these services bad. They are excellent at what they do. They are just not the thing standing between you and permanent loss.
What sync doesn't protect you from
Four failure modes, none of them exotic:
Accidental deletion. The most common cause of photo loss is not hardware failure. It is someone deleting something — often while trying to free up space, sometimes a child holding the phone, sometimes a bulk selection that grabbed more than intended. Sync faithfully copies that mistake everywhere within seconds.
Losing the account. A forgotten password, a lost second factor, a suspension, a compromised account, or a lapsed payment. When your only copy lives behind an account, access to the account is access to the photos. Apple and Google both give you a grace period after a storage plan ends, then begin removing what exceeds the free tier — 5 GB on iCloud, 15 GB shared on Google.
Corruption propagating. If a file is damaged on the device, sync replicates the damaged version. There is no earlier good copy to fall back on, because sync only keeps the current state.
Someone else's decision. Terms change, pricing changes, regions get restricted, features are retired. These are ordinary business decisions, and they are made without reference to your photo library.
A backup is what makes all four survivable. Not because clouds are untrustworthy, but because a second independent copy turns a disaster into an inconvenience.
What counts as a real backup?
The standard answer is the 3-2-1 rule: keep 3 copies of anything you care about, on 2 different kinds of storage, with 1 copy kept somewhere else.
You do not need to follow it religiously. The principle underneath it is what matters: the copies should fail independently. A phone and a cloud library that mirrors that phone are not two independent copies, because one deletion removes both. A phone and a drive in a drawer are two independent copies, because nothing that happens to one automatically happens to the other.
For most people's photos, a realistic version looks like:
- The phone — the working copy you use every day.
- A cloud service — for access anywhere and for device loss. iCloud Photos or Google Photos is fine here; this is the job they are good at.
- A copy you physically hold — a USB drive or external SSD that is not tied to an account and does not sync.
The third one is the one almost nobody has. It is also the only one that survives all four failure modes above.
How to actually back up your phone photos
Whatever tool you use, a real backup of a phone library needs four properties:
It copies originals, not compressed versions. Check that full-resolution files and formats like Live Photos, RAW, and HEIC arrive intact rather than being flattened or re-encoded.
It preserves dates and metadata. A backup where every file is stamped with today's date is much harder to use later. Capture dates, albums, and location data are part of the photo.
It is independent of any account. If restoring requires logging into a service, the backup shares a failure mode with the thing it is supposed to protect against.
It can be verified. You should be able to plug the drive into a computer and see your actual files, in folders, without special software. A backup you cannot inspect is a backup you are trusting on faith.
An external drive covers all four, which is the approach VaultDrive takes: it copies photos, videos, albums, and documents from an iPhone or Android phone straight to a connected USB drive over the cable, at full quality, with no account and no internet involved. The files land as ordinary files you can open anywhere. The VaultDrive FAQ covers supported drives and formats, how Live Photos and metadata are handled, and what the iCloud Optimize Storage setting means for a backup.
Other approaches work too — a computer with enough disk space, a NAS, or a second cloud provider genuinely separate from your first. The tool matters far less than the property: a copy that does not disappear when the original does.
Quick check: do you have a backup?
Answer these about your photos from the last five years:
- If you deleted a photo on your phone right now, is there a copy somewhere that would still have it in a month's time?
- If you permanently lost access to your Apple or Google account tomorrow, what would you still have?
- When did you last look at a copy of your photos that was not on your phone and not in your main cloud account?
- Could you hand someone a drive with your photos on it right now, without downloading anything first?
If the honest answers to the first two are "no" and "nothing," you have sync. That is worth knowing, because it is a fixable problem, and it takes one drive and an afternoon to fix.
Frequently Asked Questions
Is iCloud Photos a backup?
No. iCloud Photos is a sync service. It mirrors your library across your devices, which means a deletion is also mirrored. If you delete a photo on your iPhone, it is removed from iCloud and from every other device signed into the same Apple Account. A backup is a separate copy that does not change when the original changes.
What is the difference between a backup and a sync?
Sync keeps two or more locations identical, so every change propagates, including deletions, edits, and corruption. A backup is an independent copy captured at a point in time, so it survives changes made to the original afterwards. Sync protects you from losing a device. A backup protects you from losing the data.
Does iCloud Backup include my photos?
Usually not. If iCloud Photos is turned on, your photo library is not duplicated inside the device's iCloud Backup, because Apple treats the library as already stored in iCloud. That means the device backup you are relying on may contain no photos at all. If iCloud Photos is turned off, photos are included in the device backup instead.
How long do I have to recover a deleted photo?
On iPhone and iPad, deleted photos sit in Recently Deleted for 30 days before they are removed permanently. In Google Photos, deleted items stay in the trash for 60 days. After that window the photo is gone from the service. This recovery window is a safety net for recent mistakes, not a backup.
Is Google Photos a backup?
No, for the same reason iCloud Photos is not. Google Photos syncs your library rather than preserving an independent copy, so deletions propagate from your phone to the service. The name "Back up and sync" describes uploading, not archiving. Losing access to the Google account means losing the library with it.
What is the 3-2-1 backup rule?
Keep 3 copies of anything you care about, on 2 different kinds of storage, with 1 copy kept somewhere else. The point is that the copies should fail independently. A phone and a cloud library that mirrors that phone are not two independent copies, because one deletion removes both.
The short version
Sync and backup solve different problems. Sync keeps your library reachable and identical across your devices, and it is very good at that. A backup keeps a copy that survives whatever happens to the original — deletion, account loss, corruption, or a decision made by a company you do not control.
iCloud Photos and Google Photos are sync. They are worth using. They are just not the answer to "what happens if these photos disappear?"
That question needs a copy you hold.