Immich vs PhotoPrism

Last reviewed Aug 22, 2026 · 536 words

The fastest way to choose: Immich is a phone backup service that grew a photo manager; PhotoPrism is a photo manager that can ingest phone uploads. That origin story predicts almost every difference you will meet in daily use, and it means the right answer depends on which problem you woke up with — phones full of unsynced photos, or disks full of unorganised ones.

Where each one is clearly better

Immich's mobile apps are the best in self-hosting, full stop: reliable background upload on iOS and Android, a timeline that feels like the Google Photos app, and partner/album sharing your family will actually use without coaching. Development pace is ferocious — features land weekly, and its 112,000 GitHub stars against PhotoPrism's 40,000 reflect where the momentum is. Multi-user is first-class, with per-user libraries and face recognition.

PhotoPrism wins on respect for an existing collection. It indexes your folders where they sit, treats the filesystem as canonical, and writes nothing you didn't ask for — photographers with a decade of carefully named directories find this non-negotiable. Its RAW handling is stronger, its metadata tooling deeper, and the whole thing ships as one Go binary plus MariaDB, which makes it noticeably lighter to operate than Immich's four-service stack. Mobile, however, is a PWA plus third-party apps rather than a first-party client, and it shows.

Operational cost: pinning vs stability

Both list ~2 GB minimum RAM and both burn CPU during initial AI indexing, so hardware is a wash. The real operational difference is release culture. Immich still ships breaking changes; the project is disciplined about flagging them, but you must pin IMMICH_VERSION, read release notes, and upgrade deliberately — set-and-forget with latest will eventually strand you. PhotoPrism moves slower and calmer; updates are rarely eventful. If you want a photo server you touch twice a year, that temperament difference matters more than any feature.

Licensing is a footnote worth knowing: both are AGPL-3.0, but PhotoPrism gates a few conveniences behind a paid membership, while Immich's features are all free (the project sells an optional supporter licence).

Migration and exit paths

Coming from Google Photos, Immich is the shorter road: Takeout importers are well-trodden, and the full migration walkthrough covers the sidecar-JSON mess. Leaving either is acceptable — Immich's storage template writes originals into date-based folders and PhotoPrism never moved your files to begin with — so neither locks you in the way the cloud did.

Decision table

What I'd do

For the common case — de-Googling a household — run Immich, pin the version, and put its storage template on date-based folders so your files stay legible. Keep PhotoPrism in mind for the second server that indexes the old family archive drive; more than a few people happily run both, because the two tools genuinely solve different problems.