How Gallery and Immich relate

Noodle Gallery is a friendly fork of Immich, the open-source self-hosted photo management platform built by Alex Tran and a growing community of contributors. Gallery rebases onto every upstream Immich release, so every bug fix, performance improvement, and new feature from the Immich team lands in Gallery automatically.

The relationship is intentionally simple: Immich is the foundation. Gallery sits on top of it and adds a small number of features for use cases that wouldn't fit upstream's scope. Same database, same containers, same migration path back. If you change your mind, swapping back to upstream is a three-line change.

This page exists because people coming from Immich legitimately ask "what's different?", and the answer is worth being clear about — not because we think upstream is worse.

Where Immich runs out of room — and how Gallery fills the gaps

Gallery's exclusive features each started the same way: someone hit a wall in Immich and went looking for a door. The categories below group those walls by theme — each shortcoming followed by the Gallery features that fix it.

People and identity

The shortcoming. Immich's face recognition is account-scoped. The same real person lives as a separate entry in your library, in your partner's library, and in every shared album you both touch. Search for them and you find a third of their photos. Name them in one account and nothing carries to the rest. The People page reflects which container someone shows up in, not who actually shows up in your life.

How Gallery solves it.

Sharing and collaboration

The shortcoming. Immich's two sharing primitives — Partner Sharing and Albums — both run out of room with more than two people. Partner Sharing is all-or-nothing. Albums belong to whoever made them. There's no combined family timeline, no activity log, no “what's new since I last looked”, and no way to bulk-share tens of thousands of photos without selecting them by hand.

How Gallery solves it.

The faces recognition won't commit to

The shortcoming. Face recognition is deliberately conservative, and for a good reason: the errors are asymmetric. A face it never assigned is a small, quiet loss. A face assigned to the wrong person spreads — into search, into memories, into the album everyone can see — and pulling it back out means finding every place it went. So the model holds a tight threshold and leaves anything short of it alone. The cost is a long tail of near-misses in every library: the profile shot, the one in bad light, the one from four years ago, all sitting unassigned while the person they belong to is named and obvious. Immich gives you no way to work through that tail, and no way to untangle the clusters that did fuse two people together. The threshold is something you live with in both directions.

How Gallery solves it.

The two run on one shared verdict layer, which is what makes a decision in either stick everywhere — through merges, renames, and every future scan. Together they turn a conservative threshold from a permanent tax into something you can actually correct.

Search and discovery

The shortcoming. Each page in Immich has its own search bar — there's no global keyboard-first entry point. Smart search results come back in default relevance order with no way to sort by date or tune the similarity threshold, so combined text + filter searches return noise. Filters operate in isolation: select a country and you still see cameras and tags from elsewhere. The map view has no filter panel of its own.

How Gallery solves it.

AI and automation

The shortcoming. Immich's AI surface is focused on faces and basic CLIP search. Pets aren't detected, even though most people's libraries are full of them. Memories show only “On This Day” — no recent trip recaps, no birthday compilations. There's no automated way to suppress clutter (screenshots, memes, receipts) from your timeline. Duplicate detection works on photos but doesn't catch videos that have been re-encoded, resized, or format-converted.

How Gallery solves it.

Media management and migration

The shortcoming. Trimming a video in Immich means exporting to an external tool and re-importing. Moving from Google Photos requires CLI tools and manual scripts. Storage is local disk and external libraries — no native S3-compatible backend. Linking an existing 30,000-photo library into a shared collection isn't possible without manual selection.

How Gallery solves it.

Mobile

The shortcoming. Filtering the timeline in the Immich mobile app means switching to a separate Search tab and losing your scroll position. Advanced surfaces — the map view, scoped search, Shared Spaces — sit deeper in the app or aren't there at all.

How Gallery solves it.

The shortcomings, side-by-side

A condensed view of the same gaps and their fixes — useful if you want the whole picture in one table.

Where Immich runs out of roomHow Gallery solves it
A shared album list is flat — nothing to group twenty-five albums byNestable album folders inside every Shared Space, with covers, counts and a breadcrumb, on web and mobile
No pet detection at all, so no way to find your own dogPet Detection finds the cats and dogs; Pet Recognition turns them into named individuals on the People page, on re-ID models we trained and published ourselves
Filtering on mobile means leaving the Photos tab and losing your scroll positionIn-place filter sheet on the Photos tab — people, places, tags, dates, rating, media type
Automation stops at the edge of a shared library — nothing can file an arriving photo into a space for youWorkflows for Shared Spaces — add to space and add to space album actions, chained to any trigger or filter, creating the album if it is missing
Memories only ever ask “what happened on this date?”, so most days come up empty and every card looks the sameGenerated Memories — nine more rules for months, seasons, places, favourites, people together, videos, trip anniversaries, themes and person throwbacks, staggered across the month
Partner sharing is all-or-nothing; albums belong to whoever made them; face recognition stops at your accountShared Spaces — multi-owner timelines with Owner/Editor/Viewer roles, cross-contributor face recognition, last-visit tracking, and a per-space activity log
Albums belong to whoever made them and live outside any shared timelineSpace Albums — link or create albums inside a Shared Space, with cross-owner contributions and per-album timeline control, on web and mobile
The same person can appear as separate entries across personal and shared librariesGlobal People — identity-aware people rows, filters, and search results across accessible timeline Spaces
Recognition is deliberately cautious, so it skips the close calls — and nothing brings those near-miss faces back to youFace Suggestions — near-misses surface on the named person they probably belong to, reviewed one at a time, with every answer durable
When clustering fuses two people together, untangling it means reassigning faces by hand with no toolingFace Cleanup — a scan finds contaminated clusters and splits them into approve-in-one-pass and needs-review lanes, with six explicit destinations per face
The info panel shows the camera, place, date and tags, but none of it is actionable — filtering means leaving for a search pageContextual Filters — click any metadata value to filter the surface you are already on, with the filter in the URL
Pets aren't detectedPet Detection — RF-DETR finds the cats and dogs; Pet Recognition names them individually
Memories show only “On This Day”Smarter Memories — recent trip recaps and birthday memories with curated, server-defined titles
Generated memories disappear after their daily carousel window, with no archive or retention controlMemories Archive — browse retained generated memories and configure how long unsaved memory records are kept
Each page has its own search bar; no keyboard-first global entry pointSearch Palette — Cmd/Ctrl+K from anywhere across photos, people, places, tags, and every settings page, with prefix shortcuts and context-aware verbs
Advanced filters require leaving the keyboard flow for the filter panelInline Search Filters — type structured filters into the search bar with live suggestions and shareable URL state
Navigating a large library means scrolling through every day bucket — no way to jump to a year or month at a glanceTimeline Grouping — Years / Months / All switcher on every timeline; zoom in and out by tapping a year or month card to find a photo fast in a decades-deep library
Smart search returns default relevance order — no date sort, no similarity tuningSort by date, date-grouped infinite scroll, tunable similarity threshold
Filters work in isolation — selecting a country still shows cameras and tags from elsewhereInterdependent filtering — every filter narrows every other filter in real time
The map view has no filter panel of its ownFull filter panel on the map itself, with markers updating in real time
Storage is local disk or external libraries — no native S3-compatible backendAWS S3, MinIO, Cloudflare R2, Backblaze B2, Wasabi, or any S3-compatible store
Importing from Google Photos requires CLI tools and manual scriptsAn in-browser guided wizard for Google Takeout archives
Trimming a video means exporting and re-encodingLossless stream-copy trimming, near-instant

Worth flagging: every fix above is additive. Gallery doesn't replace anything Immich does — every shortcoming gets a new feature stacked on top of upstream. Core photo features, the full REST API, third-party integrations, Frame, home automation — all of it carries over to a Gallery server unchanged.

Reversible Immich migration

Try Gallery on your existing Immich library.

Swap three config lines, keep the same database and uploads, and use the switch-back script if Gallery is not for you. Your photos and videos stay exactly where they are.

Install in 5 minutes

Should you stick with upstream Immich?

There are real, substantive reasons to run upstream Immich instead of the fork. These aren't token bullet points — these are genuine cases where upstream is the right call.

Community size and track record

Immich has been in active development since 2022, has tens of thousands of GitHub stars, hundreds of contributors, and a large active Discord. Gallery has a small team and a much shorter track record. If you value the comfort of a large community where any question has been answered already, upstream is the right place to be.

Broader platform testing

Upstream Immich has been deployed on every conceivable hardware combination — Raspberry Pis, Synology NAS units, Unraid, TrueNAS, Docker on Windows via WSL2, bare-metal Kubernetes, you name it. Gallery has tested fewer combinations. If you're running an unusual setup, upstream's broader test surface helps.

You don't need any of the additions

The honest reason most people should stick with upstream: if you don't need Shared Spaces, Pet Detection, S3 storage, the Google Takeout wizard, or advanced filtering, then upstream Immich already does everything you want. Gallery exists to add features for specific use cases — and if those use cases aren't yours, upstream is leaner, simpler, and has more eyes on it.

Migrating from Immich is a three-line change

If you're already running Immich and you want to try Gallery, the migration is trivial. Swap two image names in your docker-compose.yml and bumpIMMICH_VERSION in your .env. The current version is v5.

2 files changed+3−3
docker-compose.yml
-image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
+image: ghcr.io/open-noodle/gallery-server:${IMMICH_VERSION:-release}
-image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
+image: ghcr.io/open-noodle/gallery-ml:${IMMICH_VERSION:-release}
.env
-IMMICH_VERSION=release
+IMMICH_VERSION=v5

Then pull the new images and restart:

docker compose pull && docker compose up -d

No data migration. No database conversion. No file copying. Your library lives in exactly the same place — Gallery reads and writes the same files Immich was using, against the same Postgres database, on the same volume.

Back up your database first and it's completely risk-free — one command and you're covered: docker exec -t your-db-container pg_dumpall -U postgres > backup.sql

Full step-by-step guide on the install page. See the migration walkthrough →

Changed your mind? Swap back in one script.

Gallery ships a cleanup SQL that drops every Gallery-specific table, column, and migration record — shared spaces, pet detection, classifications, duplicate data — leaving a plain upstream Immich database. Your photos and videos are never touched. Flip the two image names back and you're on upstream.

Read the switch-back guide
Gallery's job is to make a small set of additional features available without making you choose between them and the Immich roadmap.

Frequently asked questions

Is my data safe if I move from Immich to Noodle Gallery?

Yes. Gallery uses the same database schema, the same upload directory layout, and the same file formats as upstream Immich. The migration is two image-name changes in your docker-compose.yml. Your library is never copied, transformed, or rewritten — Gallery just reads and writes the same files Immich was using.

Can I switch back to upstream Immich later?

Yes. Gallery ships a one-command cleanup script that drops every Gallery-specific table, column, and migration record from the database — your photos and videos are never touched. Run the script, swap the two image names back to ghcr.io/immich-app/immich-server and ghcr.io/immich-app/immich-machine-learning, run docker compose pull, and you're back on upstream. Gallery is designed so the door always swings both ways.

Will Gallery diverge from Immich over time?

No, that's the opposite of the goal. Gallery rebases onto every upstream Immich release, so every bug fix, performance improvement, and new feature from the Immich team lands in Gallery automatically. Gallery's exclusive features are additive — they sit on top of upstream, not in place of it.

How quickly does Gallery rebase after a new Immich release?

Usually within a few days. The rebase process is automated where possible and manual where needed; the goal is to stay close enough that running Gallery feels like running a slightly enhanced Immich, not a separate project.

Does Gallery have a mobile app?

Yes. Noodle Gallery is live on both the App Store (iPhone) and Google Play (Android) with background camera backup, on-device CLIP search, the map view, and Shared Spaces.

Will third-party Immich apps still work with Noodle Gallery?

Yes, fully. Gallery exposes the same REST API as upstream Immich — same endpoints, same paths, same payloads. Tools built against the Immich API work with Gallery without modification: third-party mobile clients, Immich Frame, home automation integrations, CLI tools, scripts — all of it. Just point the app at your Gallery server URL instead of your old Immich URL. Noodle Gallery also has its own iOS and Android app.

Why fork at all instead of upstreaming features?

Several Gallery-exclusive features (Shared Spaces, Pet Detection, contextual filters) were either declined upstream, considered out of scope, or required architectural changes that wouldn't have fit Immich's roadmap. Forking lets us experiment without slowing down the upstream team — and rebasing means we never lose touch with their progress.

A note on the upstream Immich team

Noodle Gallery exists because Immich exists. We owe everything to the upstream team — the architecture, the database design, the mobile apps, the CLIP integration, the relentless pace of releases. If you find Gallery useful, please also star, sponsor, or contribute to immich-app/immich. Without their work, none of this would be possible.