惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
O
OpenAI News
Y
Y Combinator Blog
MyScale Blog
MyScale Blog
C
Check Point Blog
Vercel News
Vercel News
小众软件
小众软件
The Register - Security
The Register - Security
N
News and Events Feed by Topic
腾讯CDC
S
SegmentFault 最新的问题
H
Heimdal Security Blog
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
S
Secure Thoughts
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Schneier on Security
Schneier on Security
G
GRAHAM CLULEY
云风的 BLOG
云风的 BLOG
S
Schneier on Security
J
Java Code Geeks
L
LINUX DO - 最新话题
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
P
Privacy & Cybersecurity Law Blog
Forbes - Security
Forbes - Security
Cisco Talos Blog
Cisco Talos Blog
L
LINUX DO - 热门话题
Scott Helme
Scott Helme
爱范儿
爱范儿
GbyAI
GbyAI
Simon Willison's Weblog
Simon Willison's Weblog
L
Lohrmann on Cybersecurity
Cloudbric
Cloudbric
W
WeLiveSecurity
The Hacker News
The Hacker News
V
V2EX
Last Week in AI
Last Week in AI
Hacker News: Ask HN
Hacker News: Ask HN
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Blog — PlanetScale
Blog — PlanetScale
Cyberwarzone
Cyberwarzone
Google Online Security Blog
Google Online Security Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
S
Security @ Cisco Blogs
P
Proofpoint News Feed
Google DeepMind News
Google DeepMind News
C
Cyber Attacks, Cyber Crime and Cyber Security
U
Unit 42
Webroot Blog
Webroot Blog
Martin Fowler
Martin Fowler
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Backup Photos from Google Photos: A 2026 Guide
Paul Koeck · 2026-05-17 · via DEV Community

Google Photos is convenient until you need a copy that lives outside Google. Maybe you are cleaning up an old account, preparing to leave Google Photos, protecting family photos from account trouble, or just trying to make sure one mistaken delete does not wipe out years of memories.

This guide walks through the workflow end to end: Google Takeout for the export, a local staging drive for the download, and a real backup target for long-term protection.

Why Is Google Photos Backup Not a Real Backup?

Google Photos "Backup" feature uploads photos and videos into Google's cloud, but it does not create an independent, restorable copy outside Google. In a 2022 Backblaze survey of 2,068 U.S. adults, 54% reported data loss and only 10% backed up daily (Backblaze, "The 2022 Backup Survey," retrieved May 16, 2026). A real backup follows the 3-2-1 idea: separate copies, separate storage, and recoverable history in case the account, sync state, or original files change.

In Google Photos, "Backup" means your phone uploads photos to Google's cloud. That is useful sync. It does not give you an independent copy outside Google, and it does not protect you if your Google Account gets banned, you accidentally delete photos, or you want to leave Google Photos later.

Accidental deletion is the single biggest cause of data loss in a 2025 Handy Recovery survey of 1,000 U.S. adults (Handy Recovery, "The Data Loss Survey," retrieved May 16, 2026).

If you want the deeper distinction, read Sync vs Backup.

Google Photos can also remove local device copies after they are backed up. Google's Free up space on your device help page says the feature deletes photos from your device, while photos and videos that are fewer than 30 days old may be retained there. That saves phone storage, but once the device copy is gone, the practical copy you depend on may live only in Google's cloud.

A real backup is separate from the original system and should follow the 3-2-1 backup rule. Drive failure is not theoretical: Backblaze's 2025 drive report analyzed 344,196 hard drives and found a 1.36% annualized failure rate across the year (Backblaze, "Drive Stats for 2025," retrieved May 16, 2026). For Google Photos, that means exporting your photos out of Google, storing them somewhere else, and keeping historical copies you can restore later.

What Do You Need Before You Back Up Google Photos?

Before you back up Google Photos, prepare four things: a computer that can stay awake, a stable internet connection, staging storage with roughly 2x your reported library size, and backup software that can store encrypted snapshots.

Google Takeout exports can be much bigger than the storage number shown in Google Photos because Takeout may include additional copies and files that do not count against your Google storage quota. Plan for more free space than Google says you use.

Standard smartphone photos run 2–5 MB each, and a single minute of 4K video takes 400–600 MB (SamMobile, "How much storage do photos and videos actually use?," retrieved May 16, 2026). A library that Google reports as 200 GB can easily need 400+ GB of staging space once you account for both the zip files and the extracted folders.

How Do You Create a Google Takeout Export?

Create the export in Google Takeout from the Google account that owns the Photos library. Select only Google Photos, keep the default media formats, choose zip files, and use the largest archive size available so a large library turns into fewer downloads.

Select Google Photos

In the Select data to include section, click Deselect all in the top right. Most Google products are selected by default, and you do not want a huge export full of unrelated account data.

Google Takeout screen with the Deselect all button highlighted

Scroll to Google Photos and select the checkbox to the right of Google Photos.

Google Takeout screen with Google Photos selected

Leave Multiple formats at the default settings. That menu controls photo, video, and metadata formats, and the defaults are the safest choice for a faithful export.

Google Photos Multiple formats settings in Google Takeout

The All photo albums included button opens the album selector. It includes regular albums and generated entries such as Photos from 2024, Photos from 2025, and other year folders. For backup purposes, exporting everything is safer than selecting only the auto-created "Photos from year" entries. Google Photos can store files in albums, shared albums, and other generated folders. You want the full Takeout output, then let your backup software deduplicate repeated files later.

Google Photos album selector in Google Takeout

Scroll to the bottom and click Next step.

Google Takeout Next step button

Configure the export

The next Takeout screen is Choose file type, frequency & destination. This is where you choose how Google delivers the export and how large each archive file can be.

The Transfer to dropdown includes options such as Send download link via email, Add to Drive, Add to Dropbox, and Add to Box. For a backup, the email download link is usually the cleanest option because you can download the archives straight to your staging drive instead of first copying them into another cloud account.

Google Takeout Transfer to dropdown set to send download link via email

For Frequency, choose Export once if you are making a one-time archive or testing the workflow for the first time. Choose Export every 2 months for 1 year if you want Google to generate six exports on a schedule. Recurring exports still require manual downloads, so do not treat that option as automatic backup.

Google Takeout Frequency dropdown with export options

For File type, choose .zip unless you specifically prefer .tgz and know your restore tools handle it well. Zip files are easier for most people to open on macOS, Windows, and Linux.

Google Takeout File type dropdown set to zip

For File size, choose the largest archive size available to you.

Google Takeout File size dropdown with archive size options

After you choose the settings, click Create export.

Google Takeout Create export button

What Google Takeout Archive Size Should You Choose?

Choose the largest Google Takeout archive size available to you, usually 50 GB. Smaller archive sizes create more files, which means more clicks, more download time, and more chances to miss one archive. In our test export, the largest archive size made the final download audit easier.

The File size dropdown may offer 1 GB, 2 GB, 4 GB, 10 GB, and 50 GB. The size you pick decides how many archive files a large Google Photos library turns into:

Archive size 200 GB library 500 GB library
2 GB (default) ~100 files ~250 files
4 GB ~50 files ~125 files
10 GB ~20 files ~50 files
50 GB (recommended) ~4 files ~10 files

Google specifically recommends the 50 GB size limit to decrease the chance that archives are split (Google Account Help, "How to download your Google data," retrieved May 16, 2026).

How Long Does Google Takeout Take for Google Photos?

Google Takeout can take minutes, hours, or several days to prepare a Google Photos export. Small libraries may finish quickly, medium libraries often take several hours, and large libraries commonly take one to three days. Wait for Google's completion email before scheduling the download.

Google Takeout export created message explaining that the export can take hours or days

The timing depends on the size of your photo library, Google's server load, and the export settings you selected. As a rough guide:

Library size Typical Takeout processing time
Small (< 10 GB) Minutes to ~2 hours
Medium (10-100 GB) Several hours
Large (100 GB-1 TB) 1-3 days
Very large (> 1 TB) 3+ days

Wait for the completion email before you plan the download session. That email contains the link back to your Takeout export.

Google Takeout email notifying that the export is ready to download

How Do You Download All Google Takeout Archives?

Download every Takeout archive into one staging folder on a drive with enough free space for the complete export. If Google creates seven zip files, all seven must finish downloading before extraction. Missing one archive can leave gaps in years, albums, videos, or metadata sidecar files.

  1. Open the link from the email in your browser.
  2. Press the first Download button.
  3. In the save file dialog, navigate to the folder where you want to store the archives. Make sure that drive has enough free space.
  4. Repeat steps 2 and 3 for every archive file.
  5. Keep the computer awake until all downloads finish.

Google Takeout export page showing a completed Google Photos export ready to download

Do not start extracting until every zip file is downloaded. After the download completes, count the files and compare them with Google's export page. If Takeout says there are seven archives, make sure all seven are present before moving on.

Do not wait too long to download the files. Google says Takeout archives expire in about 7 days and each archive can be downloaded only 5 times before you need to request another export (Google Account Help, "How to download your Google data," retrieved May 16, 2026).

How Do You Extract Google Takeout Files?

Extract all Takeout archives into one merged destination folder, then keep both the media files and the .json sidecar files. Google Photos can place dates, location edits, descriptions, and other details in those JSON files, so deleting them reduces what a future restore or migration can recover.

How to unzip Google Takeout on Windows

  1. Put all the Google Takeout .zip files in one folder.
  2. Create a destination folder called Google Takeout Extracted, for example C:\Users\Simon\Downloads\Google Takeout Extracted.
  3. Right-click the first archive and choose Extract All....
  4. Click Browse... and select the same destination folder.
  5. Repeat for each remaining .zip file, always choosing that same destination folder.
  6. When Windows asks about duplicate files, choose Skip.

How to unzip Google Takeout on macOS

  1. Create a folder called Google Takeout Extracted.
  2. Move all Takeout .zip archives into it.
  3. Select all archives.
  4. Right-click and choose Open With -> Archive Utility.
  5. When extraction is done, delete the .zip files, leaving the combined extracted folder contents behind.

How to unzip Google Takeout on Linux

Create a merged destination folder called google-takeout-extracted, then unzip each Takeout archive into it:

mkdir -p ~/Downloads/google-takeout-extracted

for z in ~/Downloads/takeout-*.zip; do
  unzip -n "$z" -d ~/Downloads/google-takeout-extracted
done

Enter fullscreen mode Exit fullscreen mode

Keep the JSON metadata files

Google Takeout separates some Google Photos metadata into .json sidecar files, so your backup should preserve both the media files and their matching JSON files. Do not delete the JSON files just because they are not photos; our test export had enough of them that they looked like clutter at first.

This messiness is normal. Google Photos stores dates, location edits, descriptions, and other details outside the original file in some cases. For a backup, you usually do not need to repair EXIF metadata immediately. Keep the files as exported. If you ever migrate into another photo app, you can decide then whether to use a metadata repair tool.

How Do You Back Up the Extracted Google Photos Folder?

Back up the extracted Takeout folder with software that creates encrypted, versioned snapshots you can restore later. The important distinction is that the folder now lives outside Google Photos; backing it up separately gives you an independent copy with history instead of another sync-only copy.

A Mixbook survey reported by TechRadar in 2023 found that only 35% of respondents regularly backed up camera-roll photos, while the average phone held 3,139 pictures and videos (TechRadar, "Are you backing up your photos? This survey says most of us aren't," retrieved May 16, 2026).

Use a backup app that encrypts files before upload, keeps versioned snapshots, and deduplicates repeated Takeout files so copied photos do not waste storage. If you want to compare options first, use the backup software finder to find the right tool for your setup.

Back Up the Folder with BlinkDisk

To follow these steps, download BlinkDisk, open the desktop app, and sign up for an account.

After signing in, create a vault. A vault is the encrypted backup space where your snapshots are stored.

You can choose a storage destination for the vault. The default option, CloudBlink, works without additional setup, or you can choose another supported storage provider if you prefer.

Enter an encryption password. This password encrypts your files before they are backed up, so store it somewhere safe.

BlinkDisk create vault screen with CloudBlink selected as the storage destination

After the vault is created, press Add folder and select the extracted Takeout folder you created in the previous step.

BlinkDisk add folder dialog with a Google Photos Takeout folder selected

When the folder is added, press Backup folder to create the first encrypted backup.

BlinkDisk backup list showing the Google Photos Takeout folder ready to back up

Your Google Photos export now has an encrypted backup snapshot outside Google.