RecommendationUpdated September 2026· ~19 min
read
Why people are actually leaving Google Photos
Most guides to this topic open with a vague warning about "big tech"
and move on. The real reasons people leave are more specific, and
worth naming, because they change which alternative actually fits
you. Google ended unlimited free storage for photo backups back in
2021, so most active users are already paying for a Google One plan
whether they meant to or not. Photos, Gmail attachments, and Drive
files all draw from the same storage pool, so a phone that backs up
in the background can quietly fill that pool without anyone noticing
until the "storage full" email shows up. And Google's photo indexing
the face grouping, the "on this day" memories, the searchable
"beach" or "receipt" queries runs on your images whether or not you
use Google's other products, which is the part that bothers
privacy-conscious users most.
None of that makes Google Photos a bad product. It's genuinely good
at what it does: reliable background upload, solid search, and an
interface most people never have to think about. The tools below
aren't trying to be a straight clone of it. Some trade a bit of that
polish for you owning the storage outright. Others keep the "just
works" feel but encrypt everything so the provider can't read your
library even if they wanted to. Which one is right for you depends
less on features and more on how much responsibility you're willing
to take on.
Transparency: Some links below are affiliate
links. We may earn a commission at no extra cost to you. Sponsored
placements never change editorial order.
Read our sponsorship FAQ.
Tools without an affiliate program link straight to the vendor or
our directory.
What to actually evaluate
Who can technically access your photos — a
self-hosted tool means only you; an encrypted cloud service means
the provider stores ciphertext it can't read; a regular cloud
service (including Google) can technically access files unless you
add your own encryption layer.
Automatic mobile backup — the single feature that
makes or breaks whether you'll actually stick with a new tool. If
backup isn't automatic, most people quietly stop using it within a
month.
Face recognition and search — useful, but it's
also the most compute-heavy feature, so it's the first thing that
suffers on underpowered self-hosted hardware.
Where the bytes physically live — your own NAS, a
rented VPS, or a company's data center. This is the real trade-off
axis, more than any feature list.
Exit plan — can you get your photos and metadata
back out in a standard format if you switch again later, or are
you locked into one app's database?
Machine-learning face clustering and semantic search without
sending anything off your hardware
The seven alternatives
1
Immich
The default answer, for good reason
Immich is what most people mean when they say "self-hosted
Google Photos." It's the tool that made self-hosted photo backup
feel realistic instead of theoretical the mobile app backs up in
the background exactly like Google's does, and once photos land
on your server, Immich builds a timeline, groups faces, and lets
you search by content ("dog," "birthday cake") using on-device
machine learning models it runs itself. You'll notice the
project is still moving fast: releases ship often, and the
changelog reads like a team that actually uses their own
software.
Pros
Mobile background backup that behaves like Google Photos,
not an afterthought
Face recognition and content search, computed locally on
your server
Active development with a large, responsive community
No cloud dependency once it's running your data doesn't
leave your network unless you choose to expose it
Cons
You need a server: a NAS, a mini PC, or a VPS, plus Docker
Compose comfort
Face recognition and thumbnail generation are
CPU/GPU-hungry on large libraries a Raspberry Pi will
struggle
Still under 1.0 as a project; breaking changes between
versions happen and upgrades need reading the release
notes
You're responsible for your own backups of the backup
losing the server without an off-site copy means losing
everything
Migration notes: Immich has an official import
tool for a Google Takeout export that maps albums and creation
dates from the accompanying JSON files, so you don't lose that
metadata the way you would with a plain drag-and-drop.
Ideal for: Anyone with a home server (or
willing to rent a small VPS) who wants the closest feature match
to Google Photos, and doesn't mind occasional maintenance.
Immich's engine, rebuilt for sharing with other people
Noodle Gallery is a community fork of Immich, and it's worth
understanding what that actually means before dismissing it as
"just Immich with extras." It rebases onto every upstream Immich
release, so you get Immich's fixes and improvements
automatically, while adding features built specifically around
the one thing Immich itself is weakest at: multiple people
contributing to the same photo library. Its "Shared Spaces" give
each contributor a role (owner, editor, viewer), link photos by
reference instead of duplicating storage, and merge face
recognition across everyone's contributions without letting
anyone see photos outside their permission. If you're the person
a family keeps asking "can you just make one shared album for
the trip," this is built for exactly that problem.
Pros
Genuine multi-owner albums with per-person roles, not just
a read-only share link
Global People search works across your library and every
shared space you can access
Native S3-compatible storage support (AWS S3, MinIO, R2,
Backblaze B2) with a migration tool if you outgrow local
disk
Guided Google Takeout import wizard no command line
required
Database-compatible with Immich, so switching to or
reverting from upstream Immich is a small config change,
not a migration
Cons
Smaller community than upstream Immich, since it's a fork
maintained by fewer people
Being newer, it has had less real-world battle-testing at
very large scale
Inherits all of Immich's hardware requirements, plus a bit
more for the sharing layer
Worth knowing: the project is openly built with
heavy AI-assisted development alongside human-led design and
testing the maintainers are upfront about this rather than
hiding it, which we'd rather see disclosed than discover later.
Ideal for: Households or friend groups who've
outgrown "everyone dumps photos in one shared Google album" and
want real collaborative albums without a subscription.
For people who want privacy without running a server
Not everyone wants to own a piece of hardware just to store
photos, and that's a legitimate position self-hosting has real
ongoing costs in time, not just money. Ente is what to pick
instead. It's a hosted cloud service like Google Photos, but
built on zero-knowledge, end-to-end encryption: your photos are
encrypted on your device before they ever reach Ente's servers,
and Ente's published architecture means the company itself
cannot decrypt your library, even under legal compulsion. The
apps look and feel close enough to Google Photos that
non-technical family members won't need a tutorial.
Pros
Zero setup sign up and the mobile app backs up
automatically, same as Google Photos
End-to-end encryption means Ente can't view your photos
even if it wanted to
Open-source apps, so the encryption claims are
independently verifiable rather than just marketing copy
Family plan lets you share storage without sharing a
single account
Cons
You're trusting a company with your storage bill, not
yourself it's not free at meaningful capacity
End-to-end encryption means Ente can't do server-side
"magic" search on unencrypted content the way Google can;
ML search runs on-device and is a lighter feature set
Smaller company than Google, which cuts both ways: better
incentives, but less certainty about long-term survival
Ideal for: Anyone who wants real privacy
guarantees but has no interest in owning a server or doing any
maintenance.
Pricing: Free tier with limited storage; paid
plans scale by storage, with a family option.
Platforms: iOS, Android, web, desktop
(Windows/macOS/Linux).
Stingle covers similar ground to Ente open-source, end-to-end
encrypted backup with cross-device sync but positions itself
differently: a genuinely usable free tier (1GB, pay only if you
need more), no ads, and registration that asks for nothing but
an email and password. It's built on Libsodium with XChaCha20
and ECC, which is a reasonable, well-understood cryptographic
foundation rather than something custom and unaudited. It's also
on F-Droid, which matters if you specifically avoid Google Play
on your phone.
Pros
1GB free tier with no forced upgrade nagging
End-to-end encryption covers photos, videos, and their
metadata, not just the file bytes
Can capture photos/videos directly into the encrypted
vault without unlocking the app first
Available on F-Droid as well as Google Play and the App
Store
Cons
Interface and feature depth (search, albums, editing) is
noticeably more basic than Google Photos or Ente
Smaller team and community than Ente or Immich, so support
and update cadence are less predictable
No meaningful AI search this is a vault-first tool, not a
"browse by content" tool
Ideal for: Someone who mainly wants a secure,
private backup vault for sensitive photos rather than a full
Google-Photos-style browsing experience.
Pricing: 1GB free; paid tiers for more storage.
Platforms: iOS, Android (Google Play and
F-Droid).
If you're already running Nextcloud for file sync, this isn't
really a new tool to evaluate it's the Memories app, which turns
your existing Nextcloud instance into a Google-Photos-style
timeline with face recognition, map view, and "on this day"
memories, all sitting on storage you've already set up and
already back up. Starting from scratch purely for photos, we'd
point you to Immich first, since Immich's photo-specific tooling
is more polished. But if Nextcloud is already your file layer,
adding Memories is close to free no new server, no new backup
routine, no new account to manage.
Pros
Zero additional infrastructure if Nextcloud is already
your file storage
Optional end-to-end encryption at the Nextcloud storage
layer
One login, one backup routine, one place your family
already knows how to use
Fully open-source and auditable codebase
Cons
Not worth setting up Nextcloud from scratch just for this
it's a much bigger, more general system than a photo tool
Face recognition and indexing performance depend heavily
on your existing Nextcloud server's resources
Photo-specific UX is noticeably less refined than Immich's
purpose-built interface
Ideal for: Existing Nextcloud users who want
photo timeline and face search without adding a second
self-hosted app to maintain.
Pricing: Free, self-hosted (part of the
Nextcloud ecosystem). Platforms: Docker/server
install, iOS, Android, web.
LibrePhotos predates Immich and takes a slightly different
angle: rather than chasing mobile-backup polish, it leans into
search face clustering, object and scene detection, and semantic
search that lets you type something like "sunset over water" and
get plausible results, all computed locally on your server via
Django and machine learning models it runs itself. If your main
frustration with leaving Google Photos is "but I actually use
the search," this is worth a look specifically for that reason.
The mobile experience is a React Native Android app rather than
fully native iOS/Android apps, which is the clearest gap versus
Immich.
Pros
Strong self-hosted face clustering and object/scene
detection
Semantic search that goes beyond simple filename or tag
matching
Handles RAW files and video, not just standard image
formats
Immich, Noodle Gallery, and LibrePhotos all lean on
machine-learning indexing, which needs real CPU (or a GPU) to
stay fast as your library grows. PiGallery2 takes the opposite
approach on purpose: it's directory-first and read-only, meaning
it displays whatever folder structure you already have instead
of re-importing and re-organizing everything into its own
database. That design is exactly why it runs comfortably on
something as small as a Raspberry Pi there's far less happening
under the hood. The trade-off is that you don't get face
recognition or Google-Photos-style automatic organization; you
get a fast, honest viewer for photos you've already organized
yourself.
Pros
Genuinely lightweight — runs well on a Raspberry Pi or
other low-power hardware
Read-only by design, so it can never reorganize or damage
your existing folder structure
Fast setup: point it at a folder and it works
Configurable user access control for shared households
Cons
No face recognition, no AI search, no automatic albums
No native mobile backup app you still need another way to
get phone photos onto the server first
Best suited to people who already keep their photo folders
organized, not as a replacement for Google Photos'
automatic sorting
Ideal for: Raspberry Pi or low-power NAS owners
who want a fast photo viewer without the overhead of ML
indexing, and who already manage their own folder structure.
Pricing: Free, self-hosted, MIT licensed.
Platforms: Docker (recommended), native
Node.js.
Getting your photos out of Google in the first place
Whichever tool you pick, the move starts the same way: Google
Takeout. Request an export of just Google Photos (skip the rest of
your account data unless you need it too it slows the export down
and bloats the download). Google splits large libraries into
multiple zip files, and each photo ships with a matching
.json sidecar file containing the original timestamp,
GPS location, and album membership. That JSON file is the part
people throw away by accident, and it's the part that lets a good
import tool rebuild your timeline and albums correctly instead of
dumping everything into one folder dated "today."
Immich and Noodle Gallery both have import tooling built
specifically to read those Takeout JSON sidecars, which is a real
time-saver over a plain file copy. If you're moving to Ente or
Stingle instead, expect a manual upload through their desktop apps,
since neither is built around bulk Takeout imports the same way.
Either way, don't delete anything from Google until you've verified
the new library on a second device Takeout exports have been known
to silently drop a handful of files on very large libraries, and you
want to catch that before, not after, deleting the source.
Honest drawbacks worth knowing before you switch
Self-hosting means you are the backup admin.
Immich, Noodle Gallery, LibrePhotos, and PiGallery2 protect your
privacy, not your data from hardware failure. If your server dies
without an off-site copy, the photos are gone. Set up a second
backup target before you trust any self-hosted tool with
irreplaceable photos.
Face recognition needs to relearn your faces.
None of these tools can import Google's face-tagging data, since
Google doesn't export it in a usable form. Expect to re-tag faces
once after migrating.
Encrypted cloud tools trade some search power for
privacy.
Ente and Stingle can't run the same server-side content analysis
Google does on unencrypted photos, since they never have access to
unencrypted photos. Their on-device search is good, but it's not a
one-to-one replacement for "search any word and Google finds it."
Mobile-only tools without a desktop app are inconvenient for
large libraries.
If you're moving tens of thousands of photos at once, doing it
from a phone app is slow. Prefer a tool with a desktop client or a
bulk-import path for the initial migration.
Comparison at a glance
Qualitative ratings reflect editorial judgment on each tool's core
strength, not a benchmark score.
●●● = strong;
● = weaker or
not the focus.
Tool
Setup required
Mobile auto-backup
Face/AI search
Sharing
Cost
Immich
●
●●●
●●●
●●
●●●
Noodle Gallery
●
●●●
●●●
●●●
●●●
Ente Photos
●●●
●●●
●●
●●
●●
Stingle Photos
●●●
●●
●
●●
●●●
Nextcloud Memories
●
●●
●●
●●
●●●
LibrePhotos
●
●
●●●
●●
●●●
PiGallery2
●●
●
●
●●
●●●
"Setup required" is rated inversely — more dots means less setup
work.
FAQ
Can I keep Google Photos and just back up elsewhere too?
Yes, and it's a reasonable middle step. Several tools here
support automatic mobile backup the same way Google Photos
does, so you can run both in parallel until you trust the new
setup, then turn off Google's upload.
Will I lose my face-tagging and search when I switch?
Google Takeout does not export face-tag data in a form other
tools can read, so you'll lose that layer and need to let the
new tool re-scan your library. Album structure, captions, and
timestamps do carry over if you use the JSON sidecar files
correctly.
Is self-hosting actually harder than it sounds?
It requires a server you control (a home NAS, a mini PC, or a
rented VPS) and comfort with Docker Compose. It is not harder
than setting up a home router, but it is more upfront work
than downloading an app, and you are responsible for backups.
