Photos are one of the most common reasons people get into self-hosting: it's the data you'd be most upset to lose, and it's also the thing quietly costing you a recurring subscription once your library outgrows the free tier. Immich is currently the most popular self-hosted alternative to Google Photos, built specifically to replicate its core experience — automatic phone backup, face recognition, a searchable timeline, and shared albums — on hardware you own.
What Immich actually replicates
- Automatic backup from your phone — the Immich mobile app runs in the background and uploads new photos/videos to your home server over Wi-Fi (and, with remote access set up, over mobile data too).
- A searchable timeline — browse by date the same way you would in Google Photos.
- Face recognition and grouping — Immich runs its own machine-learning models locally to detect and group faces, entirely on your own hardware, with no image data sent anywhere.
- Search by content — text search like "dog on beach" works using local AI models, similar to Google Photos' smart search.
- Shared albums and libraries — invite other people on your Immich instance to shared albums, similar to Google Photos sharing.
- Original-quality storage — every photo and video is stored at full, untouched resolution; there's no compression tier decision to make.
What you give up
Being honest about the tradeoffs matters here — this isn't a strictly-better replacement, it's a different set of tradeoffs:
- You are responsible for backups. Google's infrastructure has redundancy built in that you don't get automatically with a single home server. If your server's drive fails and you don't have a separate backup, your photos are gone. This is non-negotiable: do not migrate off Google Photos without a real backup plan for your photo drive (see the callout below).
- Remote access takes setup. To back up photos while you're out and about (not just on home Wi-Fi), you need to configure secure remote access to your server — it's not automatic the way Google's cloud is.
- You maintain it. Occasional software updates, monitoring disk space, and troubleshooting the rare hiccup falls on you.
- No built-in offsite copy. Google Photos data physically lives in geographically distributed data centers. A home server does not, unless you deliberately set up a second, offsite backup destination.
Hardware requirements
Immich runs comfortably on the kind of mini PC covered in our hardware guide — 8GB+ of RAM is recommended since the face-recognition and search features run local machine-learning models, which are more resource-intensive than simple file storage. The real constraint is disk space: budget for roughly double whatever your current Google Photos storage usage is, since you'll want both your active library and a backup copy. If your photo library is large or growing quickly, a dedicated NAS rather than a single-drive mini PC is worth considering — see our NAS buying guide for sizing it, and our NAS hard drive comparison for which drives to actually put in it.
How migration actually works
- Set up Immich on your home server (it installs via Docker Compose — a configuration file that starts all of Immich's required services with one command).
- Export your existing library from Google Photos using Google Takeout, which packages your full photo/video library into downloadable archives.
- Bulk import the exported files into Immich using its built-in external library or bulk-upload tools, which preserve original timestamps and metadata.
- Install the Immich mobile app on your phone and enable background backup, so new photos start flowing to your server going forward.
- Verify everything imported correctly — check photo counts and spot-check dates/faces — before you delete anything from Google Photos.
- Only after you've confirmed your backup plan is working, consider downgrading or canceling your Google One subscription.
Immich vs Google Photos at a glance
| Immich (self-hosted) | Google Photos | |
|---|---|---|
| Cost | Free software + your own hardware/electricity | Free up to a limit, then a monthly subscription |
| Storage limit | Limited only by your own drives | Tied to your paid plan tier |
| Redundancy | Your responsibility to set up | Built-in, handled by Google |
| Face recognition/search | Yes, runs locally | Yes, runs on Google's servers |
| Data privacy | Never leaves your network (unless you back up offsite yourself) | Processed and stored on Google's infrastructure |
| Setup effort | A few hours, one-time | None — works out of the box |
Who should try this, and who shouldn't yet
Good fit: you already have or are willing to set up a home server, you're paying for Google One storage mainly for photos, and you're willing to commit to maintaining a real backup routine. Not a good fit yet: if you're not ready to think seriously about backups, or you need photos reliably accessible to non-technical family members with zero setup — in that case, keep using Google Photos, or run Immich alongside it for a while rather than migrating fully on day one.