Immich

Self-hosted photo and video management, honestly reviewed. What you get when you stop renting your photo library from Google.

TL;DR

• What it is: Open-source (AGPL-3.0) self-hosted photo and video management platform — think Google Photos, but running on your own server, with no storage limits tied to a subscription [4].
• Who it’s for: Anyone paying for Google One, iCloud+, or Amazon Photos who has a spare server or NAS and wants their photo library fully under their own control. Also families who want a shared private gallery without a corporate middleman.
• Cost savings: Google One runs $3/mo for 100 GB and $10/mo for 2 TB. iCloud+ goes up to $9.99/mo for 2 TB. Immich self-hosted is free — your only cost is the hardware or VPS it runs on.
• Key strength: The closest open-source equivalent to Google Photos that exists. Facial recognition, smart search, automatic mobile backup, memories, shared albums, and a genuinely polished mobile app — most of the reasons people pay for Google Photos are here [2][4].
• Key weakness: AGPL-3.0 license requires careful reading if you plan commercial use. The sharing experience for external guests is limited. Updates ship frequently, and keeping a self-hosted instance current takes real ongoing effort [3]. Object search accuracy degrades at the edges [2].

---

What is Immich

Immich is a self-hosted photo and video management platform that covers the same ground as Google Photos: automatic backup from your phone, facial recognition, object and scene search, albums, shared galleries, a map view, and the “Memories” feature that resurfaces photos from years past. It runs in Docker, ships native iOS and Android apps, and has accumulated 94,994 GitHub stars — making it one of the most-starred self-hosted projects on the platform.

The project is backed by FUTO, a software organization explicitly focused on giving users control over their technology. The core team is small but professional — as of late 2025 it includes eight full-time people, with additional contributors from the community [4]. The README leads with a direct warning: always follow the 3-2-1 backup strategy for your precious photos and videos. That’s an honest signal about the project’s maturity level — it’s production-quality software run by a team that understands the stakes, but they’re not going to let you confuse “backed up to Immich” with “backed up.”

What makes Immich more than just a photo viewer is that it ships the AI features most people actually use in Google Photos — and does it locally. Facial recognition runs on your hardware. Search by objects, scenes, and faces uses a CLIP-based model (semantic image search) that doesn’t send your photos to any external API [2]. If you have the compute, those models run without an internet connection.

---

Why people choose it

The people using Immich in 2025 break into roughly two camps: de-Googlers and NAS owners who want better photo management.

The de-Googler case. Michael Stapelberg [1] ran Google Photos for years and switched to Immich after Google’s gphotos-sync OAuth scope restrictions in early 2025 effectively broke the only reliable way to get a local copy of his library. His framing is straightforward: for every cloud service he uses, he wants a local backup that doesn’t depend on the vendor’s API policy. The migration required immich-go (a third-party CLI) rather than the official immich-cli, specifically because the official tool didn’t handle Google Takeout’s separate JSON metadata files and would time out when background processing jobs slowed the upload. That’s a real friction point — the first-party migration tooling for Google Photos import isn’t fully polished — but the destination works well once you’re there [1].

The Google Photos features comparison. XDA Developers [2] ran a feature-by-feature comparison. Auto backup from Android and iOS works and, once configured, runs in the background without requiring manual intervention. Facial recognition is accurate enough to correctly identify faces with and without sunglasses [2]. The shortfall: Immich doesn’t support individual pet recognition the way Google Photos does (where you can name a pet and it groups all their photos). Object search works well for common terms but accuracy drops when you scroll past the high-confidence results, and it doesn’t handle absence gracefully — searching “dog” returned cat photos rather than a clean “no results” when cat photos dominated the library [2].

The NAS owner’s perspective. The 3dcandy.social reviewer [3] installed Immich on a TrueNAS NAS with 12 TB of ZFS storage. Performance on low-powered NAS hardware is acceptable for browsing but slow for initial indexing. There have been occasional CPU hangs that required a container restart. The reviewer’s conclusion — 7.8/10, best photo management tool they’ve self-hosted — is representative of the mid-tier hardware experience: good enough for daily use, with rough edges.

The consistent thread across all three: Immich is the option you choose when the principle of owning your photo library matters enough to trade some convenience for it. People who switch aren’t primarily looking for a cheaper version of Google Photos. They’re looking for a version that can’t be deprecated, repriced, or data-mined.

---

Features

From the README feature table and the 2025 year-in-review [4]:

Core photo and video management:

• Upload and view photos and videos (mobile and web) [README]
• Auto-backup from iOS and Android when the app is opened, or in the background [2][README]
• Duplicate detection to prevent re-uploading [README]
• Selective folder backup — choose which device folders sync [README]
• Download to local device from any client [README]
• RAW format support [README]
• LivePhoto and MotionPhoto backup and playback [README]
• 360-degree image display (web only) [README]

Organization and discovery:

• Albums and shared albums with password-protected sharing links [3][README]
• Global map view based on EXIF GPS data [README]
• Folder view (mobile and web) [README]
• Memories (“x years ago”) that persist across sessions [4][README]
• Archive and Favorites [README]
• Tags (web only) [README]
• Stacked photos [README]
• “View similar photos” discovery [4]

Search and AI:

• Semantic CLIP-based search (describe a scene in natural language) [2][README]
• Search by metadata, objects, faces [README]
• Facial recognition and clustering — works across photos and video frames [2][README]
• Manual face tagging for corrections [4]
• Object and scene recognition (accuracy varies by library size and hardware) [2]

Sharing and access:

• Partner sharing (full library access for a trusted person) [README]
• Public sharing with QR codes for shared links [4]
• Custom URLs for shared links [4]
• Read-only gallery mode [README]
• Private/locked photos with PIN code protection [4]

Platform and infrastructure:

• Multi-user support with multiple admin accounts [4][README]
• OAuth support (both mobile and web) [README]
• API keys with granular permissions [4][README]
• Mobile app home screen widgets [4]
• Google Cast support [4]
• Offline support (mobile only) [README]
• User-defined storage structure [README]

2025 stability milestone: In October 2025 the team shipped what they described as “Stable” — the result of three parallel overhauls: database query rewrite, a new streaming sync architecture replacing the old bulk-request model, and a full mobile app rewrite that moves all sync to the background [4]. The year also shipped 85 new features, 200 enhancements, and 290 bug fixes [4]. That’s a significant delta — if you formed an opinion of Immich from a 2023 or early 2024 experience, the current version is materially different.

---

Pricing: SaaS vs self-hosted math

Google Photos / Google One:

• Free: 15 GB shared across Gmail, Drive, and Photos
• 100 GB: $2.99/mo
• 200 GB: $4.99/mo (shared plan)
• 2 TB: $9.99/mo
• Most family photo libraries hit 2 TB within a few years of shooting 4K video on modern smartphones

iCloud+:

• 50 GB: $0.99/mo
• 200 GB: $2.99/mo
• 2 TB: $9.99/mo
• 6 TB (family): $29.99/mo

Amazon Photos:

• Free unlimited photo storage for Prime members ($139/year) — no video beyond 5 GB without paid storage
• Not a realistic full Google Photos replacement for video-heavy libraries

Immich self-hosted:

• Software: $0 (AGPL-3.0)
• VPS option: $5–12/mo on Hetzner, Contabo, or similar — though Immich recommends 4 CPU cores and adequate RAM for the ML models, so the cheapest $5 plan may be undersized for libraries above 20K photos
• Home server/NAS: electricity cost only (typically $3–15/mo depending on hardware)
• Your time to set up and maintain

Concrete savings math:

A family with a 2 TB photo library pays $9.99/mo on Google One ($120/year) or $9.99/mo on iCloud+ ($120/year). On a $8/mo Hetzner VPS with 4 cores and 8 GB RAM, Immich costs $8/mo ($96/year) with no storage tiering — you add a volume if you need space. If you already run a home server or NAS, the marginal cost approaches zero. Over three years: Google/iCloud ≈ $360. Self-hosted Hetzner ≈ $288 with better hardware. Home NAS ≈ electricity.

The math isn’t as dramatic as the Zapier comparison because cloud photo storage is already cheap. The real argument isn’t cost — it’s control and data sovereignty.

---

Deployment reality check

What you actually need:

• A Linux server with at least 4 CPU cores and 4 GB RAM for comfortable operation — the machine learning models (facial recognition, CLIP search) are the main resource consumers [1]
• Docker and docker-compose
• Storage: enough disk for your full library plus thumbnails (roughly 1.2–1.5× your raw photo storage)
• A domain name + reverse proxy (Caddy or nginx) for HTTPS access from outside your network
• Optional: Tailscale for private access without exposing a public port, which Michael Stapelberg [1] uses and recommends

Realistic installation path:

The official docker-compose setup is well-documented and not especially difficult. Michael Stapelberg [1] deployed it declaratively on NixOS with a three-line services block — a single VM with 4 cores and 4 GB RAM. The 3dcandy.social reviewer [3] ran it on a low-powered TrueNAS NAS, which works but shows the CPU ceiling during indexing.

What can go sideways:

• Initial Google Photos migration is not turnkey. The official immich-cli upload tool timed out on larger libraries during initial import because background ML jobs (thumbnail generation, face detection, metadata extraction) compete with the upload [1]. The recommended fix is immich-go, a third-party CLI that pauses background jobs before uploading and handles Google Takeout’s metadata JSON files correctly [1]. This is a solvable problem, but it adds a step that isn’t obvious from the official docs.
• Updates are frequent and require manual action. The 3dcandy.social reviewer [3] flags this explicitly — new versions ship often, each one displays a reminder in the UI that you’re running an outdated version, and updating a self-hosted Docker deployment takes real time. This is the ongoing maintenance cost that SaaS users don’t pay.
• CPU spikes during indexing. On low-powered hardware, the ML jobs can pin the CPU at 100% during initial library import or after bulk uploads [3]. The fix is a container restart, but it’s worth knowing this is normal behavior rather than a bug.
• External sharing is basic. The 3dcandy.social reviewer [3] notes that shared albums don’t protect the underlying media in any meaningful way — if you share a link, the recipient can download everything. This is a deliberate design choice (it’s a personal photo manager, not a commercial gallery), but it rules Immich out for any commercial photography workflow.
• Object search accuracy has a ceiling. XDA [2] found that search results become less reliable as you scroll past the high-confidence matches, and the UI doesn’t handle zero-result searches gracefully. For the core use cases (find photos of a specific person, find photos from a trip) the search works. For precise scene queries, results are imperfect.

Realistic time estimate: 1–2 hours to a working Immich instance on a VPS for someone comfortable with Docker. 3–6 hours including Google Photos migration via immich-go. For a non-technical user following a guide without prior Linux/Docker experience, plan a full day.

---

Pros and cons

Pros

• Closest open-source equivalent to Google Photos. The feature surface — facial recognition, CLIP search, memories, shared albums, partner sharing, map view, mobile auto-backup — covers the main reasons people pay for Google Photos [2][4].
• Mobile apps that actually work. Auto-background backup on iOS and Android functions reliably once configured. The 2025 mobile app rewrite moved all sync to background threads, so the app doesn’t freeze during uploads [2][4].
• The ML features are local. Facial recognition and image search run on your server, not on a vendor API. Your photos don’t leave your network [2].
• 94,994 GitHub stars. This is not a hobby project. The community is massive, documentation is maintained, and the 2025 year-in-review [4] shows a professional team with full-time engineering resources.
• Stable release shipped in 2025. The October 2025 stable milestone represents database, sync infrastructure, and mobile app rewrites — the technical foundation is significantly more solid than it was in 2023 [4].
• FUTO backing. The project is funded by an organization explicitly opposed to subscription lock-in. The incentive structure is aligned with users, not venture capital timelines [4].
• Free, genuinely. AGPL-3.0 for personal use is no-cost with no feature gating. There’s no freemium model or commercial tier that hides important functionality [README].

Cons

• AGPL-3.0 is not MIT. AGPL requires that any networked service built on Immich must also open-source its modifications. For personal use this is irrelevant. For commercial use — embedding it in a SaaS product, white-labeling it — this is a hard constraint that requires a legal read.
• Updates demand ongoing time. Immich ships new versions frequently, and the in-app reminder about running an old version is a consistent pressure to update [3]. Self-hosting means you own the maintenance cycle indefinitely.
• Initial migration is not turnkey. Google Photos migration requires a third-party CLI (immich-go) rather than the official tool, and the process requires understanding why background jobs affect upload reliability [1].
• Pet recognition is absent. Google Photos lets you name and group pets by face. Immich doesn’t support this. You can still find pet photos by breed or color description, but accuracy degrades [2].
• Object search has edges. Results are good for high-confidence queries and less reliable when scrolling through lower-confidence matches. Zero-result searches aren’t handled cleanly [2].
• External sharing is minimal. Shared album links have no download protection. If you need watermarking, per-user access control, or commercial gallery features, look elsewhere [3].
• CPU-intensive during initial indexing. Large library imports with ML processing enabled will saturate a low-powered server [3]. Plan for this during the migration window.
• Hardware requirements are real. A $5 VPS is undersized. The ML workload for a large library needs a proper instance — budget $8–15/mo on a VPS, or make sure your NAS has enough headroom [1][3].

---

Who should use this / who shouldn’t

Use Immich if:

• You’re paying for Google One or iCloud+ primarily for photo/video storage and you want that cost to go away or that data under your control.
• You have a home server, NAS, or VPS with 4+ cores and 4+ GB RAM already running, or you’re willing to provision one.
• You want facial recognition and semantic image search without sending your photos to Google or Apple.
• You’re comfortable with Docker and periodic manual updates, or you’ll pay someone once to set it up.
• You’re migrating a family library and want multi-user support with a shared gallery.

Skip it if:

• You need commercial photo gallery features: download protection, watermarking, client proofing. Immich is a personal library manager, not a photography business tool.
• You have no Linux/Docker experience and no one to help with initial setup. The learning curve is real.
• You’re not prepared to maintain it. Every update is your responsibility, and updates are frequent.
• You need guaranteed uptime and can’t tolerate the occasional container hang. Self-hosted means you’re the ops team.
• You’re on a vendor plan that costs less than $3/mo and have a small library. The financial case for self-hosting isn’t strong below that threshold.

Stay on Google Photos if:

• You value zero-maintenance photo management over data sovereignty.
• Google’s AI photo organization features (including pet recognition, precise scene search, Lens integration) are features you actively use and depend on.
• Your library is under 15 GB and fits in the free tier.

---

Alternatives worth considering

• Google Photos — the incumbent. Better AI features, pet recognition, Lens integration, and tight Android integration. Requires trusting Google with your library and paying for storage above 15 GB. Closed source.
• iCloud Photos — Apple’s equivalent. Best for all-Apple households. Same structural issues: vendor lock-in, per-tier pricing, proprietary.
• PhotoPrism — older self-hosted alternative, also Docker-based, AGPL. Fewer active contributors and less feature momentum than Immich. Worth considering if Immich’s resource requirements are too high.
• Piwigo — long-established self-hosted gallery. Better for public sharing and commercial photography workflows. Weaker on the AI and mobile backup side.
• Nextcloud Photos — if you’re already on Nextcloud, this integrates cleanly. Less capable than Immich for dedicated photo management; better for unified file+photo+collaboration.
• Ente Photos — managed cloud option with end-to-end encryption and open-source clients. A reasonable middle ground if you want managed hosting without trusting Google/Apple with unencrypted data.

For a non-technical founder leaving Google Photos, the realistic shortlist is Immich vs Ente Photos. Pick Immich if you want zero ongoing cloud costs and have a server. Pick Ente Photos if you want managed hosting with strong encryption and no infrastructure to maintain.

---

Bottom line

Immich is the most complete open-source answer to Google Photos that currently exists. The 2025 stable release represents a project that’s moved past “impressive for open source” into “actually reliable for daily use.” Facial recognition works, mobile auto-backup works, memories work, and the web and mobile interfaces are clean enough that a non-technical family member can use them without a tutorial.

The trade-offs are honest ones: AGPL license, frequent updates that require manual action, an initial migration that needs a third-party tool to do well, and object search that isn’t Google-quality at the edges. None of those are dealbreakers for the target audience — someone who actively wants their photo library on their own hardware and is willing to do the work to get it there.

The cost math is secondary to the control argument. If you’re paying $10/mo for 2 TB on Google One because you have no alternative, Immich gives you that alternative. If you’re comfortable with Docker, the setup is an afternoon. If you’re not, that’s the one-time cost worth hiring someone to handle.

If the setup is the blocker, that’s exactly what unsubbed.co’s parent studio upready.dev deploys for clients. One-time fee, done, you own the infrastructure.

---

Sources

1. Michael Stapelberg — “Self-hosting my photos with Immich (2025)” (Nov 29, 2025). https://michael.stapelberg.ch/posts/2025-11-29-self-hosting-photos-with-immich/
2. Megan Ellis, XDA Developers — “I tried to see if Immich could replace my favorite Google Photos features and here’s how it went” (Jun 3, 2025). https://www.xda-developers.com/immich-google-photos-features/
3. 3dcandy.social — “Immich Review” (Sep 19, 2025). https://www.3dcandy.social/2025/09/immich-review/
4. Immich Team — “2025 - A year in review”, Immich Blog (Dec 22, 2025). https://immich.app/blog/2025-year-in-review
5. DPReview Forums — “photo backup.. - self hosted : is immich the best out there”. https://www.dpreview.com/forums/threads/photo-backup-self-hosted-is-immich-the-best-out-there.4811025/

Primary sources:

• GitHub repository: https://github.com/immich-app/immich (94,994 stars, AGPL-3.0)
• Official website: https://immich.app
• Documentation: https://docs.immich.app