Most people never think about their photos until a phone falls in a lake. Then the question gets urgent: where are the pictures of the kids, the wedding, the trip you will never take again?
The easy answer is to let a big company hold everything. That works, and for many people it is fine. But it also means a company you do not know keeps a full record of your life. This guide covers the safest way to back up photos while keeping that record private. It takes an afternoon to set up, and then it mostly runs itself.
You do not need to be technical. You need to understand two ideas, then pick one of two paths.
Before you start
You will need your photos in one place, a little patience, and a password manager. A password manager is an app that creates and remembers a different strong password for every account you have. You will want one, because both paths below depend on a secret you cannot afford to lose.
If you only take a few photos a year and none of them matter much, you can skip all of this. Your phone’s built-in backup is enough. This guide is for people who would be heartbroken to lose their pictures, or who do not like the idea of strangers holding them.
What “safe” means for photos
Safe means two different things, and people mix them up.
The first is safe from loss. Phones break. Laptops get stolen. Hard drives die without warning. A photo that lives in only one place is one accident away from gone.
The second is safe from prying eyes. A backup that sits on someone else’s computer can be read by that company, by anyone who breaks into it, or by anyone who gets a legal demand approved.
A good backup handles both. Most advice only covers the first.
Start with the rule that fixes loss
The backup world has a simple rule of thumb. Immich, a popular photo app you run yourself, recommends a 3-2-1 backup strategy to protect your data [1]. The name is shorthand. Keep three copies of your photos, on two kinds of storage, with one copy somewhere else, such as another building.
Here is why that works. Say Jake keeps his photos on his phone, on a laptop, and on an external drive in the same desk drawer. A house fire takes all three. If he had left one copy at a relative’s house, he would still have his pictures.
You do not need to follow the rule perfectly. Aim for the spirit of it: more than one copy, and at least one of them far from the others.
Understand encryption in one minute
Encryption means scrambling information so only someone with the right key can read it. The part that matters for photos is who holds the key.
With most cloud backups, the company holds the key. Your photos are scrambled while they travel and sit on their servers, but the company can unscramble them. That is how they offer face search and shared albums.
With end-to-end encryption, only you can read your files, not the company carrying them. The company stores a locked box and has no key. Think of a sealed envelope compared with a postcard.
So the question to ask about any backup is simple: who can open my photos?
Path one: an encrypted cloud service
If you want something that works like the big apps but keeps your photos private, look at services built around end-to-end encryption. Ente is one example. Its documentation says your files are encrypted on your device before being uploaded to its servers [2]. That order matters. The photos are locked before they leave your phone.
Ente also says it stores three copies of your data, across three providers, in three countries [2]. That covers the “lost” side of safety, since one failure at one company does not wipe out your pictures.
Some features usually need the company to see your photos. Face recognition is the common one. Ente says that all of its machine learning, meaning face recognition and magic search, happens entirely on your device [2]. Your phone does the work, so the server does not need to see the pictures.
It also has apps for Android, iOS, Linux, Mac, Windows and the web, and all of them are open source [3]. Open source means the code is public, so anyone can read, check, and improve it. Ente says its open-source apps have been externally audited by Cure53 [2]. An audit by an outside group is not a guarantee. It is still better than “trust us.”
The catch: you hold the key
Here is the trade. If the company cannot open your photos, it cannot help when you lock yourself out.
Ente gives you a recovery key, a 24-word phrase. It is the only way to recover your account if you forget your password and are logged out on all your devices [2]. Ente is plain about the result. If you lose both your password and your recovery key and are logged out everywhere, it cannot recover your account or data [2].
That is the deal with any private service. Nobody can snoop, and nobody can rescue you either.
So do this on day one. Write the 24 words down on paper. Keep the paper somewhere safe, apart from your computer. Save a copy in your password manager too. Do it before you upload anything.
Path two: host your own backup
The other path is self-hosting. That means running a service, like photo backup, on a computer you control instead of a company’s servers. The computer can be a small box in a closet or an old desktop. Immich is one popular tool for this.
Sarah likes this idea because no company holds her photos at all. They live in her home. She pays once for a drive and has no monthly bill.
But the work moves to you, and this is the part that surprises people. Self-hosting is not a backup by itself. It is only a second place your photos live.
Immich is direct about this: it does not handle filesystem backups for you, and you have to arrange these yourself [1]. If the drive in Sarah’s closet dies, the photos on it die too.
Back up the photos and the database
A self-hosted photo app keeps two things. There are the photo files. There is also a database, which is the app’s index of where everything is and who owns what.
Immich stores file paths and user details in the database. It does not scan the library folder, so database backups are essential [1]. Without the index, a pile of photo files is hard to rebuild into an organized library.
The good news is that Immich makes automatic database backups by default. It keeps the last 14 and creates a new one daily at 2:00 AM [1]. Those backups sit on the same machine unless you copy them elsewhere, so they do not replace the “somewhere else” copy from the 3-2-1 rule.
For the photos themselves, Immich recommends backing up the entire upload folder, though only the original photos and videos are critical [1]. If space is tight, protect the originals first.
Who this path is for
Self-hosting suits someone who enjoys tinkering, or who has a friend who does. If setting up a home server sounds like a chore, take path one. Nothing about a hobby project should make you feel behind.
Setting up a server also has risks of its own. If you open it to the internet, you take on the job of keeping it secure. That is beyond what a blog post can cover. If you go this way and feel unsure, ask a person who runs servers for a living.
A simple setup for most people
You do not have to choose only one. Here is a plan that fits most families.
Emily uses an encrypted cloud service as her main backup. Her phone sends photos there automatically. Once a month she copies the originals to an external drive. Every few months, she leaves that drive at her sister’s house and brings back the older one.
That is three copies: the phone, the cloud, and the drive. It is two kinds of storage. One is far away. It is also private, because the cloud copy is locked before it leaves her phone.
Chris, who likes projects, could swap the cloud service for a home server. The rule stays the same. The server counts as one copy, and he still needs another one somewhere else.
Common mistakes
- Keeping every copy in one place. Three copies in one drawer are one copy as far as a fire is concerned. Move one off site.
- Treating sync as backup. If a photo is deleted on your phone and the service mirrors that, it can vanish everywhere. Check that your setup keeps older versions or a separate copy.
- Losing the recovery key. With private services, this one slip can lock you out for good. Write the key down now.
- Never testing a restore. Once a year, pick a few photos and try to get them back. A backup you have never restored is a hope, not a plan.
- Forgetting the database. On a self-hosted setup, protect the index as well as the pictures.
What you can skip
You can skip building a complex setup with many tools. You can skip worrying about whether a hacker will target your vacation photos. The realistic dangers are a dead drive, a lost phone, and a company holding more of your life than you would like. The steps above deal with all three.
Your next step
Pick one path today. If you want the simpler one, sign up for an encrypted photo service, write down your recovery key, and let your phone upload. Then put a reminder in your calendar for next month to copy your photos to a drive.
Back up the photos now, while nothing has gone wrong. Then go back to your life.