This release is a pre-release and may not be stable for production use.
Immich Memories
Watch your memories again, in films you can make your own.
Immich Memories turns the photos and videos in your Immich library into finished MP4 memory films. Pick a month, a year, a trip, an album or a person. It reads Immich's dates, favourites, people and places, groups pictures into moments and proposes a cut in time order, with the reason each shot is there. You review it, swap what you don't like, then render with titles and music. A quiet month makes a short film rather than 3 minutes of filler.
It runs on a plain NAS with no GPU and no model. A GPU or a model makes it better.
▶ Play the demo with music · Watch a finished trip film · CC0 stock pictures, credited here · Documentation
The first link is a screen recording of the app, the second a finished trip film. Both use CC0 stock pictures, never anyone's family.
What you can do
- Photos and videos in one film. Stills get animated, videos give their best few seconds, Live Photos keep their motion. Favourites and named people win close calls, and you can see everything that was left in the pool.
- Change the cut before rendering. Remove a shot, trim a video, swap a picture or pull one in from the pool, then render that revision. "Never use" is a lasting decision, separate from dropping a shot from one film.
- Titles and music out of the box. Bundled tracks and template titles work on day one. Maps and generated music are optional extras with their own setup.
- Automate it later. A daily timer picks one memory worth making (a trip, a birthday, last month) and can upload it to Immich or keep it on disk. Make a few films by hand first.
- Ask in your own words. "our cat through the years" can become a film. Highly experimental: tuned on one real library, so preview before you trust it.
- Add a GPU or a model when you want. Basic makes complete films on a CPU. A GPU adds captions and extra picture checks, Full adds a text reader on top. A hardware encoder only speeds up rendering.
How it chooses explains the selection rules. Improve a film covers length, missing people and shot changes. What doesn't work yet is in the issue tracker.
Make your first film
The default is one prebuilt Docker container next to your existing Immich. No GPU, no hosted model account, no caption server. You need Docker Compose v2, two CPU cores, 4 GiB RAM for this app on top of Immich, and 25 GB for app data, images and finished films. Immich v2 and v3 both work; the deployment matrix says which versions and setups were actually tested.
The first run downloads the image and model files, then prepares the pictures you pick. A full month can take hours on a NAS, so start with 20–50 photos/videos and a 30-second film. A short film alone doesn't shrink the preparation: pick a short period too. Progress and recovery shows each phase and where to look when it stops.
Follow the quick start, then Your first film. Use the docs that match your release: a development preview says so when its downloads don't exist yet. Upload stays off on the first run, and you end with a local file you can play.
Access and privacy
The app talks to Immich with a scoped API key and never modifies your originals. Uploading a film is opt-in. Model downloads, optional model servers, maps, notifications and workers each have their own data flow, and a local URL alone doesn't prove nothing leaves. Privacy lists every recipient and how to check the Basic tier is offline.
Turn on authentication before you open it to your LAN. Authentication is disabled by default. Native installs and the shipped Compose file listen on localhost only; change the port mapping and anyone who can reach it can read your library through it. Operate and configure covers login, NAS/Kubernetes setup, backups and storage. Keep one UI replica. Report vulnerabilities as SECURITY.md describes.
This is an independent companion to Immich, not made or endorsed by the Immich team.
People and calendars
Families, relationships and calendars differ a lot, and this doesn't cover them all. If yours is missing, say so. Calendar limits and contributing household examples show where help is useful.
Development
Claude and Codex write most of the code; I set the direction and test films on a real library.
make dev installs the development tools and make ci runs the checks.
CONTRIBUTING.md describes the process;
DISCLAIMER.md describes its limits.
License
MIT, see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for immich-memories 1.0.0rc5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| immich_memories-1.0.0rc5.tar.gz | 45.0 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| immich_memories-1.0.0rc5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.6 MB
Release files / immich_memories-1.0.0rc5.tar.gz
| Download URL | immich_memories-1.0.0rc5.tar.gz |
|---|---|
| Size | 45.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31b352a81f1d262d76b00a9858b4d8e669fe73c49583ddcb526d3368430f7fbd
|
|
BLAKE2b-256 checksum How to use checksums |
142190dc0c95580f5a9d17989c47ec5be1bb94123dcdace58cd20a4b38b78160
|
| 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 Oct 7, 2026.
Transparency logRelease files / immich_memories-1.0.0rc5-py3-none-any.whl
| Download URL | immich_memories-1.0.0rc5-py3-none-any.whl |
|---|---|
| Size | 10.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b17cfd93ac7f57d6328c3d712fc538ca556617d1a36e181ea8312b96dcfcd8ff
|
|
BLAKE2b-256 checksum How to use checksums |
3a846e2222d9ba25f4860bfce7354dce924afb83dd31b7eda926c9e700fa2c2c
|
| 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 Oct 7, 2026.
Transparency logSecurity for immich-memories 1.0.0rc5
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for immich_memories-1.0.0rc5.tar.gz
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 Oct 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
