immich-app/immich

Choose this fork if you want an actively evolving Immich variant with stronger collaboration, discovery, and storage-direction changes. Avoid it if you want maximum upstream compatibility or the smallest maintenance burden.

Choose this fork if you want Immich as a branded, operator-managed product with added feedback and deployment workflows. Avoid it if you want the closest possible upstream experience or the fastest access to Immich mainline fixes.

Choose this fork if you want a customized, mobile-first Immich derivative and can tolerate divergence. Choose upstream if you want the broader, faster-moving feature set and lower maintenance burden.

Choose this fork if you want a more customized Immich experience with mobile-centric enhancements and can tolerate lagging upstream. If you need the safest path for upgrades, compatibility, and the newest upstream fixes, upstream Immich is the better default.

Prefer this fork only if its added selection, search, API, or CI changes are important enough to justify the maintenance burden. For most adopters, upstream looks safer because this fork is heavily diverged and materially behind.

Prefer the upstream project unless you specifically want this older, heavily diverged baseline and are prepared to maintain it yourself. This fork is not a good choice for adopters who want current features, fixes, or low-maintenance self-hosting.

Prefer this fork only if its album-sorting and workflow changes match a specific need and you are prepared to manage divergence. If you want the newest upstream fixes and the lowest maintenance burden, upstream is the safer choice.

Choose this fork only if its specific local behavior changes are valuable enough to justify a large maintenance burden. If you want a stable, broadly supported Immich deployment with current fixes, upstream is the safer default.

Choose this fork if Pascal GPU compatibility is the priority. Choose upstream if you want current Immich behavior, active maintenance, and the least merge risk.