← All open source projects

Immich

immich-app/immich

Immich is an open self-hosted photo and video management solution with mobile apps, a web interface, backup upload, albums, and search.

Forks 5,797
Author immich-app
Language TypeScript
License AGPL-3.0
Synced 2026-06-09

What it is

Immich is a self-hosted photo and video management system. It combines a web interface, mobile apps, media upload, albums, shared albums, search, map views, favorites, archive, and administrative functions.

The project became visible because the need is easy to understand: people like the convenience of cloud photo products, but not everyone wants family archives stored by an external provider. Immich offers a path to self-hosting without becoming just a file browser.

What is inside and how people use it

The project includes a server, web app, mobile apps, machine-learning features, metadata handling, format support, and background upload behavior. Its feature table explicitly separates mobile and web capabilities, such as mobile auto backup and web administration.

Feature shape

This fragment shows that Immich is designed as a mobile plus web product, not just a single server daemon.

Language: Markdown
| Feature | Mobile | Web |
| --- | --- | --- |
| Upload and view videos and photos | Yes | Yes |
| Auto backup when the app is opened | Yes | N/A |
| Multi-user support | Yes | Yes |
| Metadata view (EXIF, map) | Yes | Yes |
| Search by metadata, objects, faces, and CLIP | Yes | Yes |

A typical setup is a home server or private family/team infrastructure. The user connects the mobile app, configures upload, and then browses the library from web or phone. The project also clearly reminds users that Immich should not be the only copy of important photos.

Strengths and limitations

The strength is product focus: not only storing files, but searching, sharing, viewing metadata, working with albums, and recognizing faces. It feels like a full product rather than a directory of images.

The limitation is server responsibility. Updates, disks, backups, external access, and security remain with the deployment owner. For a personal archive, that matters more than a polished gallery.