Immich Review 2026: Self-Hosted Photos Without the Cloud Lease

Verdict: Immich is the leading open-source, self-hosted Google Photos–style library for people who want mobile backup, face search, and albums on hardware they control in 2026. Run it free forever with no feature paywalls; optionally buy a lifetime Individual (about $24.99) or Server (about $99.99) license to fund the project. Treat Immich as a serious self-host: backups, disk growth, and Docker ops are your job — not Immich’s marketing page.

Best for: Homelab and privacy-minded families escaping recurring cloud photo plans.
Not for: Anyone who wants zero maintenance and is happy paying Google, Apple, or Amazon for managed storage.

Researched 2026 overview based on immich.app docs, GitHub, and buy.immich.app licensing notes — not a logged multi-year restore drill. Confirm live license prices and hardware requirements before you migrate terabytes.

What it is

Immich is an AGPL-3.0 photo and video management stack, typically deployed with Docker Compose, plus iOS and Android apps and a web UI. Core capabilities include automatic mobile backup, albums and sharing, maps, “memories,” RAW and Live Photo support, facial clustering, CLIP-style search, OCR, administrative user management, and growing workflow and video-transcode features in the v3.x line. The software remains fully usable without paying. Optional lifetime licenses — commonly listed about $24.99 per individual user and about $99.99 per server — support development and explicitly do not unlock paywalled features. Confirm live at buy.immich.app and the docs hub at immich.app.

Who it’s for

Self-hosters with a NAS or mini-PC, comfortable with Docker Compose updates, and serious about a 3-2-1 backup plan for irreplaceable media. Multi-user households benefit from partner sharing and per-user libraries. Casual phone users who never patch containers, never monitor disk, and never test restores will eventually prefer a managed cloud gallery — Immich will not babysit neglect.

Strengths

• Feature trajectory close to big cloud galleries: backup, search, faces, maps, sharing, and mobile polish.
• No ransomware-by-subscription model: pay optionally, keep all product features.
• Active release cadence; recent lines emphasize mobile editing, workflows preview, and more reliable Android background backup.
• True ownership of originals on disks you control, with OAuth and API keys for advanced setups.

Trade-offs

• You operate Postgres, object/file storage, machine-learning jobs, and upgrades — downtime and data loss risk are yours.
• Hardware: public docs commonly suggest about 6GB+ RAM (roughly 8GB RAM / 4 cores is more comfortable); ML features can be disabled on smaller boxes.
• Thumbnails and transcodes often add about 10–20% storage overhead on top of originals.
• Windows filesystem quirks exist for database volumes — prefer Unix-friendly storage layouts as documented.

Buying notes & pricing

Budget hardware, electricity, and offsite backup before the optional license fee. Individual licenses usually suit small households; a Server license tends to win once you have more than a handful of users — confirm current guidance on the purchase page. Merch and donations are alternatives if you skip licenses. Never treat the Immich database volume as disposable scratch space.

How it compares

Versus Google Photos: Google wins zero-ops convenience; Immich wins ownership and long-term cost predictability. Versus Ente or PhotoPrism: Ente leans encrypted managed/self-host hybrids; PhotoPrism is another capable self-host library — Immich currently leads mobile backup polish for many buyers. Versus Synology Photos: Synology wins appliance simplicity if you already live in that NAS UI.

If you cannot restore a random month’s library from backup this weekend, fix backups before inviting the whole family onto Immich.

Verdict

Best for self-hosters who want a real Photos replacement. Not for zero-maintenance cloud refugees. Deploy with Docker and tested backups, size ML to your box, optionally license to support the project, and confirm live docs before you cut over.