Immich is the better choice if you own a machine that stays powered on and you care where your photos live. It gives you the parts of Google Photos people actually use every day, mobile auto backup, face grouping, map view, albums and shared links, without a storage meter that raises your bill as your library grows. Google Photos still wins on zero maintenance and on search that understands a sentence. If you are willing to spend one evening on setup and roughly an hour a quarter on updates, Immich replaces it.
TL;DR by reader profile:
- Family archivist with 15 years of photos (Marta, two phones, one shared library): move to Immich on a small always on box, because a growing archive is exactly the case where a per gigabyte subscription compounds against you forever.
- Photographer shooting RAW every weekend (Tomas, 40 megapixel bodies): Immich, because RAW files eat cloud tiers fast and you already keep a local working copy that you can point the server at.
- Non technical user with one phone and no home server (Elena, iPhone, no NAS): stay on Google Photos for now, because Immich needs someone to own updates, backups and remote access, and that someone would be you.
- Privacy sensitive professional handling client images (lawyer, therapist, journalist): Immich on hardware you control, because the legal question is not whether the provider is trustworthy but who can be compelled to hand over the data.
- Homelab owner already running Docker (Sam, existing NAS and reverse proxy): Immich, because the marginal cost is one compose stack on infrastructure you maintain anyway.
- Small team or studio sharing a shoot library (five people, one archive): Immich with per user accounts and shared albums, because Google Photos was built for one person and gets awkward the moment several people need write access.
The central tradeoff: Google Photos sells you freedom from maintenance and pays for it with a recurring bill and a library you do not control, while Immich hands you control and a one time hardware cost and charges you in setup time, backup discipline and the responsibility for your own uptime.
Table of contents
What is Immich, and can it really replace Google Photos?
Immich is an open source, self-hosted photo and video backup server. You install it on a machine you own, install the Immich app on your phone, and it uploads new photos in the background the way Google Photos does. It is licensed under AGPL-3.0, developed in the open on GitHub, and released on a fast cadence with frequent tagged versions. It is not a photo viewer bolted onto a file share. It is a full stack with its own database, machine learning container and mobile clients for Android and iOS.
The honest answer on replacement: yes for the daily loop, partially for search.
The daily loop is backup, browse, album, share. Immich covers all four. You get automatic background upload, a timeline grouped by date, albums, shared albums with other users on your server, public share links with optional passwords and expiry, a map view built from EXIF GPS data, face grouping into named people, and duplicate detection. Multi user support is built in, so each family member gets their own library on the same server.
Where it differs is the part Google spent a decade on: semantic search quality and the automatic memories and collages that surface old photos without you asking.
| Capability | Google Photos | Immich |
|---|---|---|
| Automatic phone backup | Yes, first party OS integration | Yes, background service in the app |
| Face grouping and named people | Yes | Yes, runs locally on your server |
| Natural language search | Yes, strong | Yes, CLIP based, weaker on complex phrasing |
| Storage limit | Bound to your Google One tier | Bound to your disk |
| Who holds the data | You | |
| Maintenance owner | You |
Treat Immich as a replacement for the product, not a clone of the company. You give up an army of engineers tuning search ranking. You gain a library that cannot be reindexed, repriced or closed without your consent.
Top comments (0)