Immich Memories
Beta, under heavy rework, not stable. The selection engine has just been replaced by a story-driven editor, and
mainand thelatestDocker tag move with the work that follows. Expect runs that fail, photos that go missing, and options that move between releases. Try it on one small album first, not your whole library, and file what breaks.
Cuts your Immich library into edited memory videos: it reads the period as a story and argues for every picture it keeps.
It connects to your self-hosted Immich server and runs a real editor over your library: a small vision model captions every picture once, a text model reads the period as a story and weighs its stories in words, and every picture in the cut carries the one line that says why it is there: a year in review, a trip with its map, one person across the years. Always chronological, favourites as indicators rather than gates, and when it can't name a day honestly it refuses rather than faking it. How it decides is documented in The Curator.
Full documentation: sam-dumont.github.io/immich-video-memory-generator
▶ Watch the 60-second demo · Make your first memory
Why: you left Google Photos for Immich and lost the year-in-review / trip / "your kid's year" videos. This brings them back: on your hardware, with pictures you can veto and music that isn't canned. AI music and LLM titles are optional extras; the render runs on CPU, and the models the editor reads with can run on the same box.
What it takes to run
This is heavy machinery. The editor reads with two models you host yourself: a reader (vision and text, ~17 GB resident at 4-bit) that groups the period into stories and looks at the candidates whose facts the edit demands, a few dozen per memory, and a caption server (500M, 1-2 GB) that describes each picture once. On the app's disk, an 88 MB encoder and ~400 MB of CPU detectors. The app itself is cheap: 2-4 GB and a CPU render. It will not cut anything without the models.
The two configurations that work:
- One Apple Silicon Mac, 32 GB or more. App, both models, render, all on it. This is the one that has actually been graded.
- The app anywhere (NAS, mini-PC, Kubernetes) plus one box that can hold the models. Two machines. There is no version of this with one small machine.
A NAS on its own, with no second machine, is not a supported setup. The whole stand-up, in order, is the self-hosting guide.
Docker (recommended for self-hosters)
curl -O https://raw.githubusercontent.com/sam-dumont/immich-video-memory-generator/main/docker-compose.yml
export IMMICH_URL="http://your-immich-server:2283"
export IMMICH_API_KEY="your-api-key"
docker compose up -d # then open http://localhost:8080
The compose file publishes port 8080 on localhost only. Authentication is disabled by default, and the app holds an Immich API key to your whole library: anyone who can reach the port can use it. To get to the UI from another machine, enable authentication first, then change the mapping to
"8080:8080". The UI is single-user, single-replica; run one instance.
Resource Requirements
Time depends mostly on where the caption server and the reader run, and on whether the period has been prepared before. Facts and readings are cached, so the first cut over a period is the slow one.
| Phase | RAM | CPU | Apple Silicon / GPU | CPU-only (4-core NAS class) |
|---|---|---|---|---|
| Idle (UI) | small | minimal | n/a | n/a |
| Preparing pictures (first cut) | 2-4GB | 2+ cores | one caption request and one encoder pass per picture; not yet measured on this route | same, slower on the encoder |
| Assembling 1080p | 4GB | 4 cores | not measured | ~10-16 min for a 14-clip monthly (measured) |
| Assembling 4K | 6-8GB | 4+ cores | not measured | not recommended |
Those are the app's numbers. The two model services are the big line item and they are not in that table because they are not in that process:
| Service | Resident while it's up | Where |
|---|---|---|
| Reader (vision + text) | ~17GB at 4-bit (30B parameters, arithmetic not measurement) | this box if it has 32GB+, otherwise another one |
| Caption server | 1-2GB | same |
A 4-core, 8GB NAS runs the app and the render perfectly well. It does not run the reader, and no media accelerator changes that. See the self-hosting guide.
Most of that assembly time is the title screens, not the encode: measured at 2 CPUs, title rendering took ~263 s of a ~339 s assembly, so read CPU-Only Mode before you buy a GPU for the encoder.
Measured once for calibration (2026-08-18): a 14-clip monthly at 1080p, cold cache, in the Docker
image with --cpus=4 --memory=4g and no GPU took 10 min with preset: fast and 15.7 min with
the default profile (4 M5 Max cores). Nobody has run the same measurement on a Celeron, so this README will not guess a multiplier. preset: fast swaps in
1080p H.264, a fast encoder and static titles; explicit settings still win over it. The
NAS-only guide
has the measurement in full. Field reports from Synology, Unraid, Proxmox and Raspberry Pi are
welcome: open an issue.
Without Docker
uvx immich-memories --help # no clone needed
mkdir -p ~/.immich-memories
cat > ~/.immich-memories/config.yaml << EOF
immich:
url: "https://photos.example.com"
api_key: "your-api-key-here"
EOF
immich-memories ui # web UI on http://localhost:8080
immich-memories generate --year 2024 --person "John" --output ~/Videos/john_2024.mp4
Supported Immich Versions
Immich Memories supports Immich v2 and v3, detected at runtime:
immich:
api_version: auto # auto | v2 | v3
Leave this on auto. The app detects the server major version and uses the matching API contract;
you do not choose a version for each run. The explicit v2 and v3 values are manual
troubleshooting overrides: escape hatches for proxies or unusual deployments that hide or rewrite
the version endpoint. They force that contract, so don't use them as upgrade flags.
immich-memories config test reports the detected contract and checks your credentials without
generating or uploading anything.
Editorial model setup
The editor reads; it does not score. Before its first cut it needs three things, all of which can run on your own hardware:
- a caption server for a public 500M vision model, on any OpenAI-compatible endpoint: it describes every picture once, and the description is kept;
- the pinned DINOv2-small encoder and two CPU detectors:
pip install "immich-memories[editorial]"plus the pinned weights; - a reader on any OpenAI-compatible chat endpoint: it reads the period, weighs its stories
and picks the moments, and it is sent an 800 px tile of the candidates whose facts the edit
demands (a few dozen per memory), so it needs vision and a 32k context. Graded on
Qwen3-VL-30B-A3B-Instruct-4biton oMLX (Apple Silicon); other vision models should work, text-only ones cannot.
A cut with one of them missing stops and says which. The whole setup, in order, is the self-hosting guide; the pinned versions, digests and the caption server contract are on Editorial annotation setup.
# In ~/.immich-memories/config.yaml
advanced:
llm:
provider: "openai-compatible"
base_url: "http://your-llm-server:8000/v1"
model: "mlx-community/Qwen3-VL-30B-A3B-Instruct-4bit"
editorial:
preparation:
caption_base_url: "http://localhost:8092/v1"
What it does
- Reads the period as a story: every eligible picture gets a caption and facts once, the text model weighs the period's stories in words (dominant, major, minor, glimpse), and each story is granted the pictures its weight earns, capped by the moments it actually holds. No clip scores, no ranking against a bar; when the moments run out the film is shorter, and it says so.
- 10 memory types: year in review, monthly, person spotlight, multi-person, season, on this day,
album, trip (GPS-detected, with an animated satellite map fly-over), holiday, and surprise me
(a day the library itself flagged, found by
discover-daysrather than asked for). The web UI offers the same ten plus a custom date range. - Photos share one pool with videos: Ken Burns, face-aware pan, blurred fill behind anything that doesn't fill the frame. A Live Photo plays its motion when the editor thinks it earns it, and is held as a still otherwise.
- Title screens with satellite map fly-overs, month dividers and particles, GPU-rendered through Taichi (static PIL titles without it). This is what makes the output look edited, not concatenated.
- Music: bring your own file, use the 28 bundled tracks (the
musicextra, already in the Docker image), or generate with ACE-Step or MusicGen. Ducking drops the music under the clip's own audio. - Runs as a four-step web UI (Memory, where the brief, the cut and the story live; Clip Review; Options; Export; behind basic auth, OIDC/SSO, or a trusted header proxy) or a headless CLI, in Docker, Kubernetes or a plain venv. Every cut is kept under the cache directory with the plan and the reason for every picture. Privacy mode blurs every frame and scrambles the speech for demos.
Daily automation
Schedule one daily immich-memories auto run. It retries the oldest pending Immich upload if a
finished video still needs delivering, otherwise it generates a single eligible memory: never
several in one invocation. It ends skipped, dry_run, completed or failed, only failed
exits non-zero, and --quiet gives a scheduler stable JSON to read. In Docker skip cron entirely:
IMMICH_MEMORIES_AUTOMATION__ENABLED=true (plus …__DAILY_AT=09:00) and the UI process runs that
same decision once a day. The variety rules that stop it repeating itself are in the
auto CLI docs.
Documentation
The full documentation covers installation (Docker, uv/pip, Kubernetes, Terraform), the web UI walkthrough, the CLI reference, every config key, hardware acceleration, audio and music and per-setup recipes.
How the maintainer runs it
graph LR
IM["Immich Memories<br/>Python + FFmpeg, Apple Silicon Mac"]
LLM["omlx / mlx-vlm<br/>local text model + caption server, same Mac"]
ACE["ACE-Step 1.5<br/>in-process, or a GPU box / K8s"]
MG["MusicGen API<br/>fallback"]
Immich["Immich v2 or v3<br/>Synology NAS"]
IM -->|"download clips"| Immich
IM -->|"reads the period"| LLM
IM -->|"background music"| ACE
ACE -.->|"fallback"| MG
IM -->|"upload back (optional)"| Immich
One example, not a requirement. The music generator is optional: without it you get your own music, or silence. The text model and the caption server are not (the editor reads with them), but they speak any OpenAI-compatible endpoint, local (oMLX) or not.
Development
make dev installs everything, make ci runs the full pipeline, make help lists the rest.
Guidelines in CONTRIBUTING.md.
Built with AI
This entire codebase was written with AI (Claude) as an experiment in building complex software cleanly with AI assistance. 7,461 tests (623 of them integration/E2E), 20 static analysis gates in CI (15 quality, 5 security), 454 source modules. See DISCLAIMER.md for the full story.
License
MIT License, see LICENSE for details.
1 maintainer
Release files for immich-memories 0.77.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| immich_memories-0.77.1.tar.gz | 7.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| immich_memories-0.77.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.5 MB
Release files / immich_memories-0.77.1.tar.gz
| Download URL | immich_memories-0.77.1.tar.gz |
|---|---|
| Size | 7.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
15200a6dba81e35036c7af0658a7f350fc33de3ddfd202dee854076035ede8f2
|
|
BLAKE2b-256 checksum How to use checksums |
74142549842cea232f20b1c0e3f56148190066246111ae4d1e61ce387092bb80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logRelease files / immich_memories-0.77.1-py3-none-any.whl
| Download URL | immich_memories-0.77.1-py3-none-any.whl |
|---|---|
| Size | 6.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
daf6ae45a656029aa1d8c385338e405f53c153bf89c6ce653379245979671872
|
|
BLAKE2b-256 checksum How to use checksums |
0d342d099cb87e39749d31d6f476641db911bdfc79c921e78a3b952557db18cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency log
