Where does a photo actually go when you back it up to the cloud?

When you back up a photo, your phone sends an encrypted copy over the internet to your provider's data centre. There it is usually split into pieces, written redundantly to many disks and often to several buildings, and encrypted again where it rests. A database keeps track of where every piece is. Sync then makes each of your signed-in devices match that library, deletions included. How each step works varies by provider.

What happens as it leaves your phone?

The photo starts as a file on your phone, image data plus details such as when it was taken. When backup kicks in, your phone opens an encrypted connection to the service and starts sending. Apple's security overview, for example, says iCloud data is encrypted in transit and stored encrypted at rest.

Big files often don't travel as one lump. Dropbox's engineering blog describes a system where every file is cut into 4 megabyte blocks, and each block gets a SHA-256 hash, a short fingerprint calculated from its contents. The app first sends the list of fingerprints. The server checks which blocks it already has and replies with the ones it needs, and only those get uploaded. The payoff is that a block the server already holds doesn't have to be sent or stored twice. That trick is called deduplication.

Think of it as shipping a flat-pack wardrobe. You send the packing list first, the warehouse ticks off the parts it already has in stock, and you only post the rest.

Not every service works exactly like this. Block-level fingerprinting is one well-documented design, not a universal rule.

Does the photo get shrunk on the way?

Sometimes, and on some services you choose. Apple says iCloud Photos stores your photos and videos in their original formats at full resolution. Google Photos offers two backup options. Original quality keeps the file as you took it. Storage saver stores photos at slightly reduced quality, compresses them, and reduces anything over 16 megapixels to 16 megapixels. It may also convert them to a different format such as JPEG.

So "the cloud compresses your photos" is true for some settings on some services and false for others. If the full original matters to you, check the setting rather than assuming.

Where does it actually end up?

Not on one computer. Large storage systems are built on the assumption that disks will fail.

One approach is plain replication, keeping several full copies. Another is erasure coding, which gets similar protection from much less extra storage. Backblaze's description of its system is a clear example. Each file is broken into 17 equal pieces, three extra parity pieces are calculated from them, and the 20 pieces are spread across different storage machines. Any 17 of the 20 are enough to rebuild the original, so three can be lost at once. Do the arithmetic and that protection costs about 18 percent extra storage, against 100 percent for keeping one full second copy.

Copies or pieces are often spread across buildings too. Amazon's S3 documentation says its standard storage classes keep objects on multiple devices across at least three Availability Zones in a region. Each zone is one or more separate data centres, many kilometres from the others but within 100 kilometres. The system checks stored data with checksums and repairs lost redundancy when a device fails. Amazon says it is designed for 99.999999999 percent durability of objects over a year, often called eleven nines.

Google describes something similar. Its documentation says data is broken into chunks, which can be up to several gigabytes, and each chunk is distributed across its storage systems and replicated in encrypted form.

What you often can't find out is which of these systems your particular photo app sits on, or how many copies it keeps. That varies between providers, and it isn't always published.

Play the sequence, take site A offline, then replay it. This shows replication with illustrative chunks and sites, not erasure coding or a particular photo service.

Who can read it?

Encryption at rest means the data sitting on the disks is scrambled, so a drive pulled out of a rack doesn't reveal your photos by itself. Google's documentation describes a pattern called envelope encryption. Each chunk is encrypted with its own data key, using AES-256 by default, and those keys are in turn encrypted with a key-encryption key. When a chunk changes, it gets a new key.

The question that matters more for privacy is who holds the keys. Apple's overview lays out the two cases for iCloud. With standard data protection, your photos are encrypted, but the keys are kept in Apple's data centres so Apple can help you recover your data. With Advanced Data Protection switched on, iCloud Photos becomes end-to-end encrypted, meaning only your trusted devices hold the keys and Apple can't decrypt them. Even then, Apple notes, some metadata stays under standard protection, and Shared Albums are not end-to-end encrypted.

Other services make other choices. "Encrypted" on its own tells you that data is scrambled. It doesn't tell you who can unscramble it.

What does sync actually do?

Backup copies your photos up. Sync keeps a library identical everywhere you are signed in. Apple's iCloud Photos guide says changes you make on one device appear on your others, and that deleting a photo on one device removes it everywhere. Deleted items wait in Recently Deleted for 30 days, then they are gone.

Sync also lets your phone hold less. With Apple's Optimize Storage setting, the phone keeps smaller, space-saving versions of your photos while the full-resolution originals live in iCloud.

Sync is not a backup

Sync is very good at one thing, making every device agree. If you delete a photo by mistake, sync faithfully deletes it everywhere. That is why services add safety nets like a recently deleted folder, and why some storage systems offer versioning. Amazon's documentation describes S3 versioning as a way to recover from unintended user actions and application failures, which tells you that eleven nines of durability alone doesn't protect against those.

The impressive durability figures are about disks failing. They are not a promise about your account, your password or your own thumb. If a set of photos really matters, keep a second copy somewhere that doesn't sync with the first.

Pieces, keys and buildings

If the 17-of-20 trick caught your eye, the next question is how erasure coding rebuilds a file from the pieces that survive. If the keys did, ask how end-to-end encryption stops a company from reading your files. Learnfold writes each of those as a new page hanging off the lesson you were on, and data packing continues in how QR codes work. The lessons come from an AI, so check technical details like these against the provider's own documentation, and see following a curiosity rabbit hole for how one question becomes an evening.