Immich vs Google Photos: Self-Hosting Your Photo Library
Google Photos and Immich solve the same problem — automatic backup, search, and sharing for your phone’s photo library — from opposite ends, the same split as Nextcloud vs Google Workspace for office files. One is a managed subscription with unlimited convenience; the other is software you run yourself, in exchange for owning your data and paying nothing per-seat.
Search intent
Someone searching “Immich vs Google Photos” is considering moving personal or office photo storage off a cloud subscription and wants to know if a self-hosted alternative is actually good enough to replace it, not just conceptually similar.
Quick take
- Want zero setup and the most polished mobile experience, and don’t mind an ongoing subscription plus your photos living on Google’s infrastructure: Google Photos
- Already run a NAS or homelab server, want full control of your photo library, and don’t mind some admin overhead: Immich (self-hosted)
- Want Immich’s model without running your own hardware: a managed Immich host — a smaller, less mature market than managed Nextcloud, so vet any provider carefully before committing
Google Photos
Google Photos gives every Google account 15GB free, shared across Gmail, Drive, and Photos via the unified Google One storage pool. Paid Google One tiers currently start at $1.99/month for 100GB, with higher tiers bundling storage and Google’s AI features together following Google’s 2026 restructuring of its plans (the old “Premium” 2TB tier was folded into new AI-branded tiers) — reverify current pricing and tier names at signup, since Google has changed this plan structure more than once recently.
What you get: automatic backup from any phone with zero configuration, best-in-class ML-powered search (“photos of dogs at the beach”), face grouping, and shared albums that work seamlessly with anyone else on Google Photos. The tradeoff is the familiar one — an ongoing per-account storage fee that only grows as your library does, and your photos, including anything sensitive, living on Google’s servers under Google’s terms.
Immich (self-hosted)
Immich is an open-source, self-hosted photo and video backup solution explicitly built to be a Google Photos replacement — automatic mobile backup (iOS and Android apps with background upload), facial recognition, ML-based semantic search (CLIP-powered “photos of dogs at the beach”-style queries), map view from photo geolocation, and shared albums, all running on hardware you control. The project reached a stable 2.0 release in October 2025 and now follows semantic versioning with limited breaking changes outside major releases — a meaningful maturity signal for something you’re trusting with irreplaceable photos.
Hardware requirements: Immich runs as a set of Docker containers (Postgres, the main server, and a machine-learning container for face/object recognition), and it’s not lightweight — plan for at least 6GB RAM and 2 CPU cores minimum, with 8GB RAM and 4 cores recommended if you want ML features to run smoothly during large imports. A 4GB box can run Immich without ML features, but leaves little headroom. The photo library itself needs to sit on a filesystem that supports Unix permissions (EXT4, ZFS, BTRFS, XFS) — NTFS/exFAT mounts will fail outright.
What you’re signing up for: no per-account fee, ever, and full control over where your photos physically live — relevant if you’re storing anything sensitive or simply don’t want a third party mining photo metadata. The cost is the admin side: you’re responsible for the server, backups of the photo library itself (self-hosting your photos doesn’t back them up — see our 3-2-1 backup strategy guide, since losing a self-hosted photo server with no backup is strictly worse than a cloud subscription), security updates, and troubleshooting when something breaks.
What Immich doesn’t match yet
Being direct about gaps matters more here than in most comparisons, since these are irreplaceable personal photos:
- Search quality: Immich’s ML search has improved a lot and is genuinely usable, but reviewers consistently note it hasn’t fully closed the gap with Google’s search quality, which benefits from a much larger training scale.
- Sharing outside your household: sharing an album with someone who doesn’t run Immich themselves is more friction than a Google Photos share link that anyone can open instantly.
- Zero-maintenance guarantee: Google Photos never goes down because you forgot to renew a certificate or the Docker host ran out of disk space. A self-hosted Immich instance can, and will, occasionally need your attention.
Head-to-head at a glance
| Google Photos | Immich (self-hosted) | |
|---|---|---|
| Cost model | Free 15GB, then per-account subscription | Free software; you pay for hardware/storage |
| Admin overhead | None — fully managed | You (or a hired admin) patch, back up, monitor |
| Data location | Google’s infrastructure | Your own hardware |
| Search/ML quality | Best-in-class | Good and improving, not fully at parity |
| Sharing outside your circle | Effortless (any Google account) | More friction unless the recipient also runs Immich |
| Best for | Anyone who wants zero setup and doesn’t mind the subscription | Homelab/NAS owners who want full control and no per-seat fee |
Who actually fits where
Good fit for Google Photos: no home server or NAS already running, want the best possible search and sharing experience, comfortable with photos living on Google’s infrastructure.
Good fit for Immich: already running a NAS or homelab server with someone maintaining it, want to get off a recurring cloud subscription, comfortable accepting slightly rougher edges on search/sharing in exchange for full control — and willing to build a real backup plan for the photo library itself, not just move the single-point-of-failure from Google to your own server.
Bottom line
This isn’t “which is better” so much as “who’s maintaining this and what happens if it breaks.” Google Photos wins on zero-effort reliability and search quality; Immich wins on cost-at-scale and data control once you’re already running a server. If you self-host, budget the same seriousness for backing up the photo library as you would for any other business-critical NAS data — a self-hosted photo server with no offsite backup is a worse position than the cloud subscription it replaced.