Getting photos out of social media and cloud libraries

Everybody assumes the hard part is getting the photos out. It is not. Every large service has an export button somewhere, and given enough patience you will end up with a folder of files.

The hard part is that the folder is worth less than what you started with.

The value was in the comments

Think about what is actually attached to a family photo posted in 2013. The image, yes. But also: eleven replies, four of which name somebody. An aunt correcting the year. Somebody saying “this was the day before we moved”. A person tagged who nobody in the family can identify now but who was clearly there.

None of that is a photo. All of it is the memory.

Most exports give you the files and a machine-readable dump of everything else, if you are lucky. The relationship between the two, this comment belongs to that photo and this person said it, survives in the archive but not in any form a human will ever read again. Nobody opens a JSON file in five years and recovers their grandmother’s correction from it.

So before you export anything, decide that the comments are part of what you are rescuing. Otherwise you will do the work twice.

What each route actually gives you

A large social platform. The full-archive download is the only version worth having; the “download your photos” shortcut usually gives you compressed copies at a fraction of the original resolution. Expect the archive to take a day or more to prepare. Expect comments to be in a separate file from the images.

A phone-maker’s cloud library. Generally the best-preserved originals, and generally the worst at giving you anything else. Dates and locations usually survive. Album structure often does not. Anything anyone typed, a caption or a shared-album comment, is frequently absent entirely.

A general cloud photo service. Use the dedicated data-export tool rather than dragging folders out of the web view, which quietly re-encodes. Watch for the archive being split into several parts; people routinely download the first and assume they are done.

A messaging thread. Almost always the worst quality and almost always the best context, because people talk while they send. If a photo only exists in a thread, screenshot the conversation around it as well. It is not elegant. It is the only copy of what was said.

A method that does not lose the context

1. Export the archive, not the pretty version. Whatever the service calls its complete download, that is the one.
2. Before you touch the files, read the comments. Open the old thread, the old album, the old post. Read what people wrote underneath.
3. Write down what you learn, in your own words, while you are there. Not later. Names, the year somebody corrected, the thing your uncle said. Ten minutes now beats an afternoon of forensics in a year.
4. Bring the photos and what you wrote in together. In Cirluma that means the file and the note arrive as one thing, credited to you, rather than the file arriving alone and the knowledge staying in your head.
5. Then ask the people who were there. You will have got half of it wrong, and that is the point of doing this with other people rather than alone.

The one that catches everybody

Check the resolution of what came out. A photo that looked fine on a phone in 2013 may have been stored at 960 pixels on its longest edge, and no amount of later work recovers detail that was never saved. If the original is still on an old device, on a memory card, or on a drive in a cupboard, that copy is worth more than the cloud one.

The export is a rescue, not an archive. What makes it an archive is the part you write down while you still can ask.