This list exists separately from the photo-app list for one reason: replacing Google Photos is 20% a photo app decision and 80% a backup decision.
Updated 2026-10-03 · 6 options compared
The short answer
Immich, on the strength of its mobile app. Background upload from Android and iOS works, the timeline is fast, and it is the closest self-hosted equivalent to the thing you are replacing. Everything else on this list is infrastructure around that decision.
This list exists separately from the photo-app list for one reason: replacing Google Photos is 20% a photo app decision and 80% a backup decision. The app is where you browse; the backup is what has to work every day without being thought about. Most abandoned self-hosted photo setups were abandoned at the backup step, not the browsing step, so that is what this page optimises for.
| # | Tool | License | Setup | Best for |
|---|---|---|---|---|
| 1 | Immich | AGPL-3.0 | Intermediate | Replacing Google Photos or iCloud Photos as the phone's backup target. |
| 2 | Syncthing | MPL-2.0 | Beginner | Reliably moving camera files from a phone to a server, unmanaged. |
| 3 | Nextcloud | AGPL-3.0 | Intermediate | Adding phone photo upload to an existing Nextcloud setup. |
| 4 | Duplicati | LGPL-2.1 | Beginner | Encrypted off-site backup of the photo directory with minimal setup. |
| 5 | Restic | BSD-2-Clause | Intermediate | Scripted, storage-agnostic backup of a large photo library. |
| 6 | Kopia | Apache-2.0 | Intermediate | Policy-driven deduplicated backup with a graphical interface. |
The workflow to aim for is: phone uploads automatically to your server, the server keeps the originals in a plain directory, and something else backs that directory up off-site. Immich handles the first two reliably. The third leg is the one people skip, and it is the one that matters — a self-hosted photo server with no off-site backup is more dangerous than a cloud subscription, because at least the cloud had redundancy you did not have to think about. Pair whatever you choose with something from the backup tools list, and test a restore.
Best for: Replacing Google Photos or iCloud Photos as the phone's backup target.
The only self-hosted photo project built mobile-first rather than adapted to mobile. Background upload, a fast chronological timeline, duplicate detection, album sharing outside your network, and rapid development that visibly closes gaps. For replacing Google Photos as the destination your phone backs up to, this is the current answer.
Replaces: Google Photos, iCloud Photos, Amazon Photos
Best for: Reliably moving camera files from a phone to a server, unmanaged.
The most reliable way to get raw files off a phone with no cloud in between: device-to-device, encrypted, no account, no server required. It is not a photo manager — there is no timeline, no search, no albums — but it solves the transport problem with the fewest dependencies, which is precisely why it appears in so many robust phone-to-server setups.
Replaces: Dropbox, Resilio Sync, Google Drive
Best for: Adding phone photo upload to an existing Nextcloud setup.
If you already run Nextcloud, its mobile app can auto-upload photos to a folder, and that folder can be indexed by a photo tool. Fewer moving parts, weaker photo experience. A perfectly reasonable answer for people whose priority is one server rather than the best possible gallery.
Replaces: Google Drive, Dropbox, OneDrive
Best for: Encrypted off-site backup of the photo directory with minimal setup.
The off-site leg, and the easiest way to close the gap between "my photos are on my server" and "my photos are safe". Scheduled, encrypted, deduplicated backups to nearly any destination, configured through a web interface. Photos are large and rarely change, which is exactly the workload deduplicated backup handles best.
Replaces: Backblaze, Carbonite, Acronis
Best for: Scripted, storage-agnostic backup of a large photo library.
The same job with a more portable repository format and no daemon — a script and a cron entry. If your photo library is a terabyte of originals, restic's deduplication and its ability to target almost any storage backend make it the option that will still be workable when the library doubles.
Replaces: Backblaze, Duplicati, Arq Backup
Best for: Policy-driven deduplicated backup with a graphical interface.
Deduplicated repository backup with policies, scheduling and a GUI, so retention rules for photos can be expressed in configuration rather than remembered. A comfortable middle ground if you want restic-style portability with a policy engine managing it.
Replaces: Backblaze, Arq Backup, Duplicati