Guide · Updated July 2026 · 11 min read
How to back up your Google Photos, properly
Somewhere in a Google data center there is one account record that decides whether you still have your baby photos. One password, one lockout, one slip of the thumb. This guide is about fixing that this weekend, whatever your budget and however deep your paranoia runs. You don't have to leave Google Photos to do it.
The uncomfortable part
The risk isn't Google losing your photos
Google's data centers are probably the safest place your photos have ever lived. Hardware failure is not the threat. Access is. People get locked out of Google accounts every day: a flagged payment, an automated moderation misfire, a hacked account, a recovery phone number that no longer exists. When it happens there is no support line to call, and everything attached to the account goes at once. Gmail, Drive, and every photo since 2009.
Even with your account intact, Google Photos is a sync service. Delete a photo on your phone, or let a storage cleanup app do it for you, and the cloud copy disappears too. Sync keeps your devices agreeing with each other; it won't save you from your own mistakes, or from Google.
Pick your level
The ladder, from peace of mind to bulletproof
You don't need to become a data hoarder overnight. Pick the level that matches how much you'd grieve, and climb later if the paranoia grows.
Level 0 · One copy, one account
Where most people are. Everything rides on a single Google login. Free, effortless, and the entire reason this guide exists.
Level 1 · Peace of mind, in ten minutes
Turn on camera-roll backup in a second app you may already have. OneDrive gives you 100 GB for $1.99 a month. Amazon Photos is free and unlimited for photos if you have Prime (videos cap at 5 GB). From then on every new photo lands in two clouds automatically, and you never think about it again.
The gap: it only catches new photos from your phone. Your existing library, the years already in Google, stays unprotected. (There's one more trap here; how this actually works below.)
Level 2 · The real backup: your whole library, somewhere you own
Export everything with Google Takeout and put it in storage that answers to you, not to an ecosystem. Cheap object storage is built for exactly this: Backblaze B2 runs about $6.95 per TB per month, iDrive e2 about $40 per TB per year. A typical 500 GB library costs a couple of dollars a month to keep safe. This covers everything Level 1 misses, including the old stuff.
The catch: getting a clean export out of Google is genuinely annoying. More on that below, it deserves its own section.
Level 3 · Full 3-2-1, for the irreplaceable
The archivist's standard: 3 copies, on 2 kinds of storage, with 1 off-site. In practice: Google stays your working copy, the cloud archive from Level 2 is your off-site copy, and you add a local one, an external drive (a 2 TB drive is roughly $70, once) or a NAS. Keep the drive unplugged between updates and ransomware can never touch it.
Test a restore once a year; the worst time to discover a broken backup is the day you need it.
How the second-cloud backup actually works
Level 1 sounds almost too easy, so here is exactly what happens. You install a second app (OneDrive, Amazon Photos, Proton Drive), sign in, and flip one switch: OneDrive calls it “Camera backup,” Amazon calls it “Auto-Save.” From then on the app watches your camera roll and uploads new photos in the background, over Wi-Fi by default. Same mechanism Google Photos uses, pointed at a second home.
The fine print is about what it uploads: the photos physically on your phone. That has two consequences. First, it can't reach back into Google's cloud for the old photos that are no longer on the device; that history is what Level 2 is for. Second, and this trips up a lot of people: if you use Google Photos' “Free up space” button, it deletes the local originals, and your second app suddenly has nothing to upload. If you rely on that button, let the second app finish its initial sync first, and go easy on it afterwards.
Platform quirks, briefly. Phones are stingy with background time, so give the app an occasional open to let it catch up, and glance at its “last backed up” line when you think of it. Amazon Photos in particular wants to stay open during the initial sync, which can take hours for a big camera roll. After that, it's hands-off.
Which second cloud? If you have Prime, Amazon Photos is free and unlimited for photos (videos cap at 5 GB). If you live in Windows or Office, OneDrive is $1.99 a month for 100 GB and includes ransomware detection with 30-day file recovery, a real backup feature hiding inside a sync app. If privacy is the point, Proton Drive does end-to-end encrypted camera backup at $3.99 a month for 200 GB. Skip Dropbox for this: the free tier is 2 GB, which fills up in a weekend.
What it actually costs
| Option | What it protects | ~500 GB library | Notes |
|---|---|---|---|
| Amazon Photos (Prime) | New + old photos (not videos) | Included with Prime | Videos cap at 5 GB; keep the app open for the first sync |
| OneDrive 100 GB | New phone photos | $1.99/mo (100 GB only) | Level 1; 1 TB is $99.99/yr with Office thrown in |
| iDrive e2 | Everything you put in it | ~$1.70/mo | Cheapest archive; no download fees |
| Backblaze B2 | Everything you put in it | ~$3.50/mo | The well-loved standard; free egress up to 3× stored |
| External 2 TB drive | Everything, locally | ~$70 once | Add for Level 3; keep it unplugged |
The deep freeze: Glacier and friends
If you scroll cloud pricing pages long enough you'll find tiers that look absurdly cheap. Amazon's S3 Glacier Deep Archive stores a terabyte for about a dollar a month; Azure's Archive tier is the same. A 2 TB library, safe in a data center, for roughly $24 a year. The catch is that these tiers are priced for data you write once and hope to never read. A Deep Archive restore takes 12 to 48 hours, retrieval is metered, storage has a 180-day minimum, and pulling 2 TB back out of AWS costs about $180 in bandwidth alone. Cold storage is a fire safe, not a filing cabinet.
| Tier | $ / TB / month | Getting it back | Sharp edges |
|---|---|---|---|
| S3 Glacier Deep Archive | ~$1.01 | 12–48 h wait, plus fees | 180-day minimum; ~$90/TB egress |
| S3 Glacier Instant | ~$4.10 | Instant, ~$30/TB retrieval | 90-day minimum |
| Azure Archive | ~$0.99 | Hours, ~$20/TB retrieval | 180-day minimum |
| Cloudflare R2 Infrequent | ~$10.24 | Instant, ~$10/TB processing | 30-day minimum; egress free |
| Backblaze B2 (for comparison) | $6.95 | Instant, free up to 3× stored | None to speak of |
Our take: the deep-freeze tiers are worth it for large libraries if you're comfortable in the AWS console (a neat trick is uploading to plain S3 and letting a lifecycle rule sink files into Glacier automatically). Everyone else gets ninety percent of the benefit with none of the sharp edges from B2 or iDrive e2, at prices that are already a rounding error.
The total cost of your paranoia
Putting the ladder in money terms, per year, for a typical and a large library:
| Level | What you're running | 500 GB library | 2 TB library |
|---|---|---|---|
| Level 1 · peace of mind | Second cloud on your phone | $0 (Prime) – $24/yr | $60 – $120/yr |
| Level 2 · adds the archive | + B2 or iDrive e2 | + $20 – $42/yr | + $80 – $167/yr |
| Level 3 · adds local + offline | + external drive (5-yr amortized) | + ~$15/yr | + ~$25/yr |
| The frugal extreme | Level 3, archive on Deep Archive | ~$45/yr all-in | ~$75/yr all-in |
How often, and can you automate it?
Think of it as two clocks. New photos should back up continuously, and Level 1 already solves that: once a second app watches your camera roll, there is nothing to remember. The archive runs on a slower clock and needs refreshing. The rule of thumb: refresh as often as the number of photos you can bear to lose. A lost quarter would sting but not devastate most people, so quarterly is a sane default. Wedding year? Back up next week.
So can the archive clock be automated? Partly, and it's worth being honest about which part. Here's what runs by itself:
- Scheduled Takeout. When you request an export, tick “every 2 months for 1 year” and Google produces six snapshots on schedule, delivered to your Drive. Two caveats: each one is a complete copy, never an increment, and after a year the schedule silently stops. Calendar reminder, twelve months out.
- PC backup services. If your library also lives on a computer, Backblaze Personal ($99/yr, unlimited, one machine, famously refuses NAS drives) or iDrive Personal (5 TB for $79.50/yr, unlimited devices, NAS included) will back that machine up continuously without your involvement.
- Scheduled sync tools. For the technical: rclone or Arq on a schedule, pushing a local photo folder to B2 or e2 with client-side encryption. Set it once, forget it.
And the part that can't be automated: nothing can watch your Google Photos cloud and mirror it out continuously. Google closed the Photos API to third-party apps in 2025, so there is no background door. Takeout is the only exit, and someone has to carry the boxes: download the parts, unpack them, fix the metadata, upload them to the archive. That someone can be you with an afternoon and a script, or a tool built for it. Either way, the realistic ceiling is semi-automatic: Google drops a snapshot every two months, and each drop needs about ten minutes of attention to land in your archive.
The export problem
Where Google makes it harder than it should be
Here's what actually happens when you export. Takeout hands you your library as a stack of zip files, 2 GB apiece by default, so a few hundred gigabytes arrives as dozens of parts. Inside, every photo has been separated from its own metadata: the capture date, the location, the description all sit in a little .json file next to the image, and the photo's file date is reset to the day you exported. Unpack it naively into a new home and twenty years of photos sort themselves under today's date.
It doesn't stop there. Emailed download links expire after about a week (send exports to Drive instead). Every export is a full snapshot, so refreshing your backup means re-handling the entire library each time. And since Google shut off API access to Photos for third-party apps in 2025, no backup tool can simply sync your library out in the background. The export door is Takeout, and only Takeout.
None of this is impossible to deal with by hand. It's just tedious in a way that makes most people give up halfway, which is exactly the wrong place to stop.
Full disclosure: PhotoBridge is our product. Everything else in this guide works without it.
So which level are you?
If losing your photos would make you shrug, do Level 1 today and move on with your life: it's free with Prime, $2 a month without. If it would make you cry, add the Level 2 archive: two to four dollars a month covers your whole history. If your photos are irreplaceable, or they're also your work, go the full 3-2-1 and test your restores. Even that tops out around $5 or $6 a month for a big library, less than the Google One tier you're probably already paying for.
Whichever you pick, do the ten-minute version now. Every level above zero survives the bad day that Level 0 doesn't.
Quick answers
Isn't Google Photos itself a backup?
No. It syncs. If a photo is deleted on your phone, or your account is locked or hacked, the cloud copy goes with it. A backup is an independent second copy that survives whatever happens to the first one.
What does it cost to back up a 500 GB library?
About $1.70 a month on iDrive e2, about $3.50 on Backblaze B2, or roughly $70 once for an external drive. If you have Amazon Prime, unlimited photo (not video) backup is already included.
How often should I refresh a full backup?
Continuous for new photos (a second cloud app handles that automatically) and two to six full refreshes a year for the archive. Google Takeout can schedule an export every two months for one year, then it silently stops, so set a reminder to re-enable it.
Why do my exported photos all show the wrong date?
Google Takeout strips the real capture date and location out of each photo and puts them in a separate .json file, and the photo's own file date gets reset to the export date. You have to merge that metadata back, either by hand with a script or with a tool like PhotoBridge that does it automatically.
I turned on a second cloud's backup, so why are my older photos missing from it?
Camera-roll backup only uploads what's physically on your phone. Photos already offloaded to Google's cloud, especially after using the 'Free up space' button, aren't on the device to upload. Your history needs the archive route: a Takeout export into storage you own.
Is Amazon Glacier worth it for a photo backup?
It's the cheapest storage on earth, about a dollar per terabyte per month on Deep Archive, but restores take 12 to 48 hours and getting a full library back out of AWS costs real money (roughly $90 per TB in bandwidth plus retrieval fees). Good as a last-resort copy of a huge library if you're comfortable with AWS. For most people, Backblaze B2 or iDrive e2 are nearly as cheap and have no sharp edges.
Ready for more than a backup?
If the real itch is getting your photos out of Google entirely, we wrote a separate guide on the exits: Ente, Immich, and what daily life looks like after you switch.