Immich: Own Your Photo and Video Library
In this Repos
Immich: Own Your Photo and Video Library
The job
Immich replaces a photo and video cloud subscription with a library you run yourself. It is a self-hosted management platform (the repository) with mobile apps for automatic backup, albums, map, search and shared libraries, served from a machine you control.
What it replaces: the recurring storage tier, and the assumption that your photos must live on someone else's servers. The project's documentation states its requirements plainly: a Linux machine, a Docker Compose deployment, at least 6 GB of RAM, and the database on local storage rather than a network share.
Immich: Own Your Photo and Video Library
For whom / skip if
For you if your library has outgrown a free tier, or you would rather not rent storage for pictures you took. It suits anyone with a small always-on machine: a home server, a NAS that runs Docker, or a modest virtual private server with enough memory.
Skip it if nobody will maintain a server: upgrades, backups and certificates become your job. The requirements are also firm: 6 GB of RAM at minimum (8 GB recommended), a Unix-friendly filesystem, and the database on local SSD storage, never a network share. If that machine is not in your future, stay on a managed service.
Immich: Own Your Photo and Video Library
Before you start
You need a Linux machine (or Windows through WSL2) with Docker Engine and the Docker Compose plugin, at least 6 GB of RAM and two CPU cores, and disk sized for the library plus room to grow: the documentation notes that thumbnails and transcoded video add roughly 10 to 20 percent to the library size. No GPU is required.
Budget twenty minutes for the documented quickstart below, and a little more to point a domain and HTTPS at the server for real use. Everything in this publication comes from the project's own documentation, read on 2026-10-05.
Immich: Own Your Photo and Video Library
First win in 30 minutes
These are the commands from the project's Docker Compose guide, the path its documentation recommends. Nothing here needs an account or a cloud service.
Download the compose file and the environment template into a folder of their own.
Edit the .env file to set where photos and the database live.
Start the containers, then open the web app to register the admin user.
mkdir ./immich-app
cd ./immich-app
wget -O docker-compose.yml https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
wget -O .env https://github.com/immich-app/immich/releases/latest/download/example.env
# edit .env: set UPLOAD_LOCATION and DB_DATA_LOCATION
docker compose up -dThe documentation says the web app then answers at http://<machine-ip>:2283, where the first visit registers the admin user and creates the library. The mobile apps log in with the same address and start backing up the camera roll.
One documentation note worth reading twice: the command is docker compose, the Compose plugin form; the older docker-compose is deprecated and no longer supported by Immich.
Immich: Own Your Photo and Video Library
Links and freshness
Repository: https://github.com/immich-app/immich. Documentation: https://immich.app/docs. Licence: AGPL-3.0, read from the repository on 2026-10-05. Reviewed: sources and documentation read on 2026-10-05. Version or commit: last commit 69f06a29, 2026-10-03; current stable release v3.2.4 (2026-09-28).
The Repos method page, How U365 Selects Open-Source Repos, explains the admission rules and every card signal. The Vaultwarden publication, Vaultwarden: Own Your Password Vault, shows another repository at full length.
Freshness: this entry carries its review date and its maintenance signal. The section monitor re-checks licence drift, archive state and commit movement on a schedule. When a signal moves, the publication is updated or demoted, and a correction found by a reader appears here with its date.
Immich: Own Your Photo and Video Library
What it teaches
The run builds three transferable capabilities. First, storage thinking: sizing a library, separating fast database storage from bulk media, and planning thumbnails and transcodes, the arithmetic behind every media pipeline. Second, service operations: a multi-container stack, its upgrades, and the release notes that warn when an upgrade needs care. Third, data custody: phone backup, retention and the backup habit that makes a library survive.
This publication maps to UID (Digital Design, UX/UI). A photo library is a design artefact at scale: metadata, albums, sharing and the interface that makes it usable, and running it yourself is the ownership habit UID builds.
Immich: Own Your Photo and Video Library
The Repo Card
The card carries the same signals as every INSIDE Repos publication, so one glance answers the questions that matter before you commit a machine to it.
Signal | What the card says |
What it replaces | Photo and video cloud subscriptions: storage tiers and phone-backup plans |
Own-It grade | B. Self-hosted service: a Docker Compose stack you run; the code is AGPL-3.0 and yours to keep |
Friction | 3. A Linux machine with 6 GB of RAM or more, Docker Compose, and the database on local storage |
First win | The documented compose quickstart: download two files, edit one, start the stack, register the admin at port 2283 |
CI-First benefit | CI-First Positive. It moves a library off rented storage and puts retention, sharing and backups under your own policy |
Imposture risk | Low. Hosting photos is infrastructure; the app is the product and the library is yours |
Licence | AGPL-3.0, read from the repository on 2026-10-05 |
Maintained | Last commit 2026-10-03; not archived (GitHub API read on 2026-10-05) |
Reviewed | 2026-10-05: sources and documentation read for this review |
Stars appear only as context, never as a ranking: the repository showed 115,600 stars as of 2026-10-05. Everything on this card is verifiable: the licence, the last commit and the archive state come from the repository, and the review date is when U365 read the sources.
Immich: Own Your Photo and Video Library
The cost of ownership
The software is free (AGPL-3.0); the costs are the machine that runs it and the storage for the library. A small always-on computer or an entry-level virtual server with 6 to 8 GB of RAM is enough to start, and the documentation is explicit that thumbnails and transcodes add roughly 10 to 20 percent on top of your original files. There is no subscription, no per-user fee and no storage rent.
The real bill is attention. The project moves fast: the current stable line shipped its latest patch on 2026-09-28, and major releases publish explicit breaking-change notices with a reminder to back up first (read on 2026-10-05). Plan for occasional upgrades and a backup you trust, the same care any self-hosted service needs.
Immich: Own Your Photo and Video Library
Backup and recovery
The project's own warning is the right starting point: its README tells users to follow a 3-2-1 backup plan for their photos and videos. Concretely, three things must be safe: the uploaded media, the Postgres database, and the compose configuration. The documentation's backup page shows the database dump command (pg_dump through the running container) and the matching restore steps, with the blunt warning that the restore path deletes current data.
A practical routine: keep the upload folder and the database dump inside your normal backups, keep one copy off the machine, and read the upgrade notes before each major release because they say whether the database will be touched. Then do the step almost everyone skips, and walk one restore through somewhere harmless before you ever need it.
Immich: Own Your Photo and Video Library
Common pitfalls
The traps that cost the most time are documented, and each has a known answer.
Database on a network share: the documentation says the Postgres data must live on local SSD storage, never a network share of any kind. This is the single most common way to corrupt a self-hosted library.
The compose command: Immich requires the docker compose plugin form; the older docker-compose is deprecated and no longer supported, and using it fails in confusing ways.
Upgrades need eyes open: major releases carry breaking-change notices and a back-up-first warning. Read the release notes before pulling a new version; this is a feature when you expect it and a trap when you do not.
Immich: Own Your Photo and Video Library
What users say
Signals were read on 2026-10-05 and each carries its source. Where a source shows no data, this publication says so instead of guessing.
Source | Signal (read 2026-10-05) | What it shows |
GitHub issues | 479 open, 8,997 closed | A large project whose maintainers close issues steadily relative to its size |
Contributors | 1,015 listed | A community far too large to depend on any single person |
GitHub releases | v3.2.4 stable on 2026-09-28; breaking-change notices on majors | A project that warns before it breaks, and ships often enough to matter |
Project documentation | A public demo instance, full install and backup guides, per-release upgrade notes | The maintenance burden is documented rather than hidden |
What users ask for, from the tracker read on 2026-10-05: stronger sharing, stacking across views, and metadata editing, requests from people deep enough in the tool to want it better. What users report: HEIC HDR previews that render flat, mobile delete flows that confuse, and a timeline that resets position. None of these are hidden displacement; they are the normal backlog of a platform used daily by very many people.
U365 editorial note: the signal aligns with the CI-First reading. People who run Immich report capability increasing (they operate and curate their own library), and the costs that remain are maintenance, which is exactly the ownership the section teaches.
Immich: Own Your Photo and Video Library
Migration
Leaving a photo cloud is a well-trodden path. The documentation describes importing the rest of your Google Photos library through Google Takeout, with the community tool immich-go doing the heavy lifting, and it covers adding a pre-existing folder as an external library so your current archive keeps its place without being copied twice.
What stays behind: the cloud service's sharing features and its hosted processing. What comes over: every photo and video, with albums and metadata as far as the export carries them. Start the server first, import the archive, then keep the phone backup running for a week before you cancel anything.
Comments