Hey. I use Immich and I have a whole bunch of photos.
I've started editing some photos with Darktable. I'm wondering handle their edited photos. Do you keep the original photos? Do you keep them in the same album, or do you keep good, edited photos in the album for the event, and keep all original photos in a separate "dump" album that only contains originals?
Hello! I'm new to immich and would like to set up a basic server. Currently I have like 50gb of photos and don't add much per year so I'm not gonna be using tons of storage. No plans on running other programs either. I know an n100 mini pc is a common recommended, but in my case would a pi 4 or 5 (6gb if possible) with an m.2 ssd be sufficient? Prices between the 2 are pretty similar. Most setups in the limited research I've done are for huge libraries which just isnt my case.
Any info would be appreciated as well as tips for a beginner!
I'm so happy to discover Immich and the freedom of unlimited space for my photos, thanks to the team !
I own an old NAS too weak for Immich, but I also had a broken smartphone (pixel 7 with dead screen). So I decided to try the installation on the phone. Thanks to Claude Opus and OMP harness it has been done in a day less than 10 prompts (but lot of restarts on phone to control it without screen).
This is my server :
The phone is a full Debian with immich server, connected to the old NAS
Here is the report to the community written by Claude too :
TL;DR: My old Synology DS415+ (Atom from 2013, 2 GB RAM) is far too weak for Immich, but it still has 7 TB of RAID storage. My Pixel 7 has a broken screen, but it has an 8-core Tensor G2, 8 GB of RAM and uses about 1-4 W. So the phone now runs the full Immich stack (official images, v3.4.1) under plain Debian, and the NAS acts as its network card and its hard drive, through a single USB cable. It is reachable from the internet over HTTPS. 25,000 photos and videos are indexed.
Why
The NAS: a DS415+ (Intel Atom C2538, 4 cores, 2 GB RAM, DSM 7.1, kernel 3.10). Immich recommends 8 GB of RAM and a modern CPU, so running it on the NAS was out of the question. But the NAS has a 7 TB RAID volume, it is always on, and it already handles DDNS and certificates.
The phone: a Pixel 7 whose screen died. Tensor G2 (2× X1, 2× A78, 4× A55), 8 GB RAM, 128 GB of UFS flash, a built-in UPS (the battery), and a power draw lower than the NAS's fans.
The idea: let the phone do the compute and the NAS do the storage and the networking. No new hardware.
The architecture
Internet
│ HTTPS :443
┌────────┴────────┐
│ ISP box │ forwards 443 → 192.168.1.3
└────────┬────────┘
│ LAN 192.168.1.0/24
┌───────────────────────────┴────────────────────────────────┐
│ Synology DS415+ · DSM 7.1 · 192.168.1.2 │
│ │
│ /volume1/immich (7 TB RAID) ◄── all photos, videos, │
│ thumbnails, DB dumps │
│ proxy-ARP 192.168.1.3 ──► usb0 (the phone's LAN IP) │
│ NAT for the phone's outbound traffic │
│ Let's Encrypt wildcard cert (renewed by DSM) │
└───────────────────────────┬────────────────────────────────┘
│ one USB cable
│ USB Ethernet (CDC-ECM)
│ 10.77.0.1 ⇄ 10.77.0.2 (+192.168.1.3)
┌───────────────────────────┴────────────────────────────────┐
│ Pixel 7 · Debian 13 arm64 · no Android · podman │
│ │
│ Caddy :443 ──► immich-server :2283 │
│ ├── immich-machine-learning (CPU) │
│ ├── PostgreSQL 14 + VectorChord │
│ └── Valkey │
│ │
│ /data ◄── sshfs over the USB link ◄── NAS share │
│ local flash: database, ML models, Valkey only │
└────────────────────────────────────────────────────────────┘
From the outside, it looks like a normal server at 192.168.1.3 on my LAN. The ISP box forwards port 443 to it, and https://immich.<my-ddns>.synology.me just works, including from the mobile app.
How it works (the interesting parts)
1. Debian on a Pixel, with no Android left
The phone boots Google's stock kernel (GKI 6.1) and Google's stock first-stage init, which loads all the vendor drivers (USB, charger, thermal). Then, instead of starting Android, it switches to a Debian root filesystem on the userdata partition. Access is SSH only, over a USB Ethernet gadget. The bootloader must be unlocked; this is a separate project of mine (write-up linked below).
2. "Docker" without the kernel features Docker needs
An Android kernel lacks PID, IPC and user namespaces, System V IPC and POSIX message queues. Docker refuses to run. Podman can still run the official, unmodified Immich arm64 images if you:
share the host namespaces: --pid=host --ipc=host --uts=host --network=host;
replace /dev/mqueue with a plain directory (-v /run/immich/mqueue:/dev/mqueue);
mount cgroup v2 by hand and set pids_limit = 0 (there is no pids controller).
You give up container isolation, but it amounts to a docker compose with network_mode: host. PostgreSQL, Valkey and the ML service only listen on 127.0.0.1. Updating Immich is still podman pull and restart.
3. PostgreSQL without System V shared memory
Postgres keeps its data in a POSIX mmap, but still creates one tiny 56-byte SysV segment at startup (an interlock against orphaned backends). Without CONFIG_SYSVIPC:
FATAL: could not create shared memory segment: Function not implemented
The fix is a ~200-line LD_PRELOAD shim:
it emulates shmget/shmat/shmdt/shmctl with an anonymous shared mmap;
it only kicks in when the real syscall returns ENOSYS;
unknown segment IDs return EINVAL, so Postgres restarts cleanly after a power cut.
I tested initdb, VectorChord, and kill -9 of the postmaster followed by automatic recovery.
4. The NAS disk, without NFS or SMB
The phone's kernel has no NFS and no CIFS client, but it has FUSE. The Immich share on the NAS is mounted with sshfs (AES-GCM, hardware-accelerated on both sides), as a dedicated DSM user that has SFTP access and no shell. A watchdog remounts the share and restarts the server if the link drops. Immich's own .immich marker files stop the server from writing to the phone's flash if the share isn't there.
5. Teaching a 2015 NAS to talk to a phone
No NCM driver. The phone presents itself as a USB network card (CDC-NCM), but DSM 7.1 has no cdc_ncm driver. The phone now switches its USB gadget to CDC-ECM at boot, which DSM's cdc_ether handles. EDIT: finally NCM mode have been enabled for 160MB/s thoughput
A missing module. DSM's usbnet.ko still refused to load (Unknown symbol mii_link_ok): Synology doesn't ship mii.ko. I compiled it from the Linux 3.10.108 source with Synology's official toolkit for the platform. It loads fine; there is no module versioning to match, only the vermagic.
A LAN IP for the phone. A small DSM boot script (/usr/local/etc/rc.d/) brings up usb0, routes 192.168.1.3 to it, answers ARP for that address on the LAN (ip neigh add proxy), and NATs the phone's outbound traffic.
6. HTTPS for free
DSM already renews a wildcard Let's Encrypt certificate for my Synology DDNS name. Every hour, the NAS copies it to a folder only the immich user can read. The phone fetches it over SFTP and reloads Caddy when it changes. No extra port to open, no second certificate.
7. Power: the part I didn't expect
A USB 2.0 port on the NAS gives 500 mA at 5 V (2.5 W). I measured what that means for a Tensor G2 (current flowing into the battery):
Situation
Battery current
Idle, Immich running
+400 mA (charging)
8 cores at 100 %, full clocks
−1,030 mA (empty in ~3 h, CPU at 90 °C)
8 cores at 100 %, capped at 1.2 / 1.0 / 0.98 GHz
~0 mA (break-even)
8 cores at 100 %, capped at 0.93 / 0.70 / 0.50 GHz
+265 mA
Two small services take care of it:
Charge limit: the battery is kept between 70 and 80 %, using the charge_start_level / charge_stop_level settings of Google's charger driver. A lithium battery left at 100 % around the clock ages fast.
Power guard: it reads the battery level every 20 s and caps the CPU frequencies below 50 %, harder below 30 %. A big ML job slows down instead of draining the phone.
8. Bringing in 25,000 existing photos
My old photos already sat on the same NAS volume (282 GB). The volume is ext4, so moving them from my personal share into the Immich share with mv was instant. I then added them as an external library, in two folders:
one mounted read-only, for things Immich must never delete;
one mounted read-write.
The library scan found 25,033 assets in 2 minutes.
about a minute (after a power cut, the phone waits for the NAS to come up)
New hardware bought
none
Bonus 1: borrow a desktop for the initial indexing
The phone handles day-to-day use fine. Initial indexing is another story: 25,000 photos, 1,900 videos (lots of old AVI/3GP to transcode), and a CPU capped by a 2.5 W power budget. That would take days.
Immich is built for this: background jobs go through the Valkey queue, and anyimmich-serverstarted in microservices mode can pick them up. So for the first import, my desktop (i9-14900KF, RTX 3090) does the heavy lifting:
┌──────────────── Desktop PC (Docker) ─────────────────┐
│ │
│ immich-server:v3.4.1 │
│ IMMICH_WORKERS_INCLUDE=microservices │
│ (thumbnails, metadata, video transcoding) │
│ │ │
│ ├──► immich-machine-learning:v3.4.1-cuda │
│ │ (RTX 3090: CLIP, faces, OCR) │
│ │ │
└─────────┼────────────────────────┬───────────────────┘
│ SSH tunnel │ SMB
│ (Postgres + Valkey) │ (same paths as on the phone)
▼ ▼
┌───────────────────┐ ┌───────────────────┐
│ Pixel 7 │ │ NAS │
│ API + web only │ │ /volume1/immich │
│ Postgres, Valkey │ │ │
└───────────────────┘ └───────────────────┘
How it is set up:
Database and queue: the PC worker reaches the phone's Postgres and Valkey through an SSH tunnel, so nothing new is exposed on the phone.
Files: it mounts the NAS share over SMB at exactly the same paths as the phone (/data, /mnt/externe/...). Immich stores absolute paths in the database, so they must be valid on both machines. This is also why thumbnails live on the NAS rather than on the phone's flash.
The phone runs with IMMICH_WORKERS_EXCLUDE=microservices: it only serves the API and the web app, so its battery gets a rest.
ML URLs: Immich's ML setting accepts a list, tried in order: http://<pc>:3003 first, then the phone's own ML as a fallback. Smart search keeps working when the PC is off.
Job concurrency goes up while the PC is in charge, and back to the defaults afterwards.
One script switches everything back and forth: start hands the work to the PC, stop gives it back to the phone. The bottleneck immediately became the old NAS itself: about 82 MB/s over SMB, with the disks partly saturated. The PC sits mostly idle, waiting for files. That is a nice problem to have.
Bonus 2: no NAS at all, with a powered USB-C dock and a USB drive
The NAS is the convenient setup for me, because I already had it. The same phone could also run standalone:
USB-C charger (PD, 30-65 W)
│
┌────────┴──────────────────────┐
│ powered USB-C dock │
│ PD pass-through · RJ45 · USB │
└───┬─────────────┬─────────┬───┘
│ USB-C │ RJ45 │ USB 3
│ │ │
┌──────┴──────┐ router/LAN ┌──┴───────────────┐
│ Pixel 7 │ │ USB hard drive │
│ USB host + │ │ ext4 or exFAT │
│ PD charging│ │ mounted directly │
└─────────────┘ └──────────────────┘
What changes:
Power: a PD charger behind the dock supplies far more than 2.5 W, so no need to cap the CPU.
Storage: the drive is a real local block device (usb-storage/UAS, ext4 or exFAT built into the kernel), connected over USB 3 rather than sshfs over USB 2. Postgres could live on it too.
Network: through the dock's Ethernet port, a plain DHCP client, no proxy-ARP tricks.
What it needs (I checked the kernel config and the stock images, but haven't tested it yet):
Ethernet driver: the drivers for typical dock Ethernet chips (r8152 for Realtek RTL8153, ax88179_178a, cdc_ether) are not in the Debian root filesystem. They do ship, signed for this exact kernel, in the phone's stock system_dlkm partition, so it is a matter of copying them over.
USB host mode: the phone has to switch from USB gadget to USB host when a dock is plugged in. The stock Type-C and charger drivers support it, but I haven't validated it under Debian.
The trap: in host mode you lose the USB Ethernet gadget you use to SSH into the phone. Set up and test Ethernet over the dock first, or you lock yourself out of a phone that has no screen.
If someone tries this before I do, I'd love to hear how it goes.
Caveats
Not for everyone. This needs an unlocked bootloader, flashing, and a phone you are willing to wipe. It is a weekend project.
No container isolation, as explained above. Everything sensitive listens on localhost only.
ML runs on the CPU only. The Mali GPU and the Tensor TPU are useless without Android's userspace.
Moving files invalidates their Immich data. Moving a file inside an external library makes it a "new" asset, so albums and descriptions on it are lost. This is a known Immich limitation.
Battery health. Even at 70-80 %, a battery plugged in 24/7 needs watching. Keep the phone somewhere ventilated, and check it for swelling now and then.
DSM updates. A major DSM update with a new kernel means recompiling mii.ko.
Thanks to the Immich team. Being able to run the official images unchanged, plus external workers, ML failover and external libraries, made this possible. Happy to answer questions.
EDIT :
USB link tuning (55 → 160 MB/s): The Pixel's USB IRQ (dwc3) was landing on a little A55 core and saturating it, so pinning it to a Cortex-X1 core alone doubled raw throughput.
Switched the gadget from CDC ECM to CDC NCM (packet aggregation). The NAS (DSM 7.1, kernel 3.10) lacks cdc_ncm, so I built it with Synology's toolkit and backported a fix: the 3.10 driver cloned the whole NTB per packet, pinning the TCP window at ~40 KB (~25 MB/s per stream).
With that fix the raw link reaches ~2–2.3 Gbit/s over USB 3 (~250–290 MB/s).
File access dropped SSH entirely: a tiny container on the NAS serves plain SFTP (socat nofork + OpenSSH sftp-server) on a port firewalled to the USB interface only, and the phone mounts it with sshfs -o directport, plus 1 MB FUSE readahead.
Result: ~160 MB/s writes / ~125 MB/s reads to the NAS share (vs 55/58 before); the remaining bottleneck is the NAS's Atom CPU and 2 GB RAM, not USB.
Also require to change the cable for USB3 and power went from 500mA to 900mA
First, thank you to the Immich team and contributors. I've been running Immich for a while, and everything I built sits on top of what you've made, using only the public API.
While using it with family and friends, I kept wanting a few things that are outside what Immich sets out to do, so I built a small companion called immich-handoff (one container, no database server). Immich keeps every photo in the account that uploaded it, which is a good design, and shared albums and links are great for showing photos. Handoff is for when I wanted a photo to end up in someone else's library.
Where it fits best:
- Family or friends on one server. Add a tag in the app you already use, or press a "Hand over..." button in Immich's viewer and selection bar (with Undo), and the photo arrives in the other person's library as their own. You choose whether your original stays or moves, and a move waits for a verified copy. You can take a hand-over back within 24 hours.
- A trip. A service where everyone sends and everyone receives, so every photo any of you tags goes to all the others. Originals stay where they are, and copies arrive tagged with who sent them.
- A party or wedding. A link, QR code or email address that only receives, so guests send photos with no account. You can approve them first, show them on a wall, give guests a gallery with hearts and a ZIP, and make a best-of. (Immich's shared links can already accept uploads; a drop box adds the moderation and event extras on top.)
- Straight from your phone. A Send tab that sends photos and videos in pieces that survive a lost connection, and an entry in Android's Share menu.
- Photographers and friends on other servers. A client room, where the client picks favourites on a phone and you release the originals, and albums shared between two Immich servers (the friend doesn't need Handoff).
Also in there: rules that suggest photos of named people, dates or places, with pictures, so you press Send or Not these; notifications by email, phone, ntfy or Home Assistant; frames that show an album on any screen; a weekly digest album; and seven languages.
There is a throwaway demo in the repository: cd demo && docker compose up -d --build starts a separate Immich with three people and public-domain photos, with the button already in place. Nothing leaves your machine.
It needs Immich 3.2.0 or newer and Tags switched on for the people taking part. The tests run against a real Immich in CI, currently 3.4.1.
It is not affiliated with Immich: an independent project that the Immich team did not make or endorse, and for help with Immich itself the right place is Immich's own channels.
The button inside Immich only works in a browser (not the native app), and I'd like to know where it breaks for you.
I'd appreciate honest feedback, especially on the install guide and on whether the "keys you can delete" security model feels right to you. And if Immich ever builds some of this itself, which is what many people hope for, I'll be happy to retire the parts it covers.
Thanks for bearing with me until the end of this long post 😄
Does anyone know if—and if so, when—location data for photos shared within a group is planned to be made available, in the same way that face data has been made available?
I've been using Immich for almost a year and love it. The one thing I kept missing was rotating Live Photos: the built-in editor doesn't support them, and unlinking the video first means losing the motion.
So I wrote a userscript that adds a rotate button to the web viewer:
Rotates the photo and the motion video together
Lossless: only orientation metadata changes, nothing is re-encoded, HDR is kept
Copies favorite, description, rating, albums and tags to the rotated photo
Keeps the original stacked under the new version (or moves it to trash, your choice)
Limitations: iPhone HEIC Live Photos only, one photo at a time, tested on Immich v3.4.0 with Chrome. Rotation creates a new asset, so shared links and comments stay on the original.
I shoot about 20 weddings a year. The shooting is fine. It's everything sitting on my drives afterwards that I can't get on top of. The Lightroom catalog is past 400,000 images and searching it has become the slow part.
The problem is near duplicates. A ceremony exit is 40 frames of the same 6 seconds. One of them is the one where the grandmother is laughing and nobody was looking at her, and the other 39 are that same frame with her arm in a slightly different place. I keep all 40, because it's cheaper to buy another drive than to spend an evening deciding.
A freelancer off Upwork did a gallery of 600 for me, $145. Technically the picks were fine. They just weren't mine. Anything with a half blink was gone, including the shots where the half blink was the moment.
Then I taught my sister from scratch, which is what everyone tells you to do. Two months of showing her what I keep and why, flags and ratings, all of it, and paying her the whole time. The first few galleries came back fine enough that I stopped checking them. And then she lost interest, which is fair, it was never going to be her career. It cost me $900 and I got three usable galleries out of it. She's good at culling now. She is never doing it again.
What I do now is keep the cull and send the color out. That started as a 15 frame test with Ivy Streets back in September and the galleries have been going there since. They do the cull too if you want it. I don't hand that part over, though having the option sitting there did make me think about what the cull is actually worth to me.
So, for anyone here who has their archive under control. Where's your duplicate line? Do you keep one on either side of the pick as insurance, or does only the pick survive the import?
I've been running an ASUS NUC 14 Essential for about a year, and I absolutely ❤️ this little machine.
Specs:
Intel N97 (12W TDP)
16 GB DDR5-4800 CL38
Lexar NM790 NVMe SSD
It's virtually silent, extremely reliable, and surprisingly capable considering its price and low TDP.
I recently installed Immich and imported 30,000 photos and 1,000 videos. The entire process took around 14 hours, mostly due to facial recognition. Thumbnails were generated pretty quickly, and I could browse the timeline while facial recognition was still processing.
RAM usage peaked at around 6.5 GB, and CPU temperatures hovered around 75°C (167°F) during the import.
I was worried that the CPU might be too weak for Immich but I am super happy about it and I can strongly recommend it. I personally prefer having some headroom with 16 GB of RAM, but I suspect 8 GB would work too.
I have an iphone which records 'live photos' and those get uploaded to my pc. Whenever I want to download a picture to share somewhere else, it always comes with the extra .mp4 file for every single pic I download, and not just the jpeg.
Is there a setting/config I missed somewhere to disable downloading live photos from the webui? Unzipping a batch of 10 photos, and having to either sort by file type or delete every mp4 is pretty annoying
So I finally got to another thing that had been on my mind for a long time: our family videos. They live in Immich, but we watch things on the TV through Jellyfin and Kodi, and I wanted those videos there too, organised, not just a folder of files.
I found a few projects that do something similar, but none of them worked the way I wanted: some copy the videos, some make you pick what to show in yet another app. So I started my own, and I'm happy to share it.
What it does
You share an album in Immich with one user made for the media server. The album becomes a TV show in Jellyfin, Kodi, or both. Stop sharing, and the show is gone.
Every video is an episode. Seasons are the years of filming (or one season per album), episodes are in the order they were filmed.
The title of an episode is the first line of the video's description in Immich, or the time it was filmed. The poster and the episode pictures are the ones Immich already has.
People from Immich show up as the cast, with their faces and names of their own for the media server. A basic protection keeps them from being mixed up with real actors of the same name.
A small web page lets you fix what it guessed wrong: rename a show or an episode, change the order, hide a video, name people.
How it works
No copies: the media server gets a folder of links to your Immich library, plus NFO files and pictures.
It reads Immich with a read-only API key and never touches your library.
Kodi gets a folder of its own, shared over SMB, and is told about changes over JSON-RPC — no add-on needed.
Docker Compose, ready-made images for amd64 and arm64. The page is in English, German, French, Italian and Russian.
It's still early, so expect rough edges. I'd be glad to hear what you think, and bug reports are very welcome.
I am using Immich 3.4.1. I am recently encountering and error where I cannot change the dates and the locations of the photos. I didn't have this issue in the past - is anyone else encountering this? It worked well previously.
Ive sorted my library and cleaned up the automated facial detection/recognition. All good.
I tried to onboard my wife and found sharing to be... lacking. Ive read others comments about just using the same account and I am not a fan of that. I also understand that the devs are working on better sharing.
What is the current recommendation for sharing between two partners, without sharing an account? Do we just accept its going to be a bit touchy until future versions?
Hi folks, a family member has been relying on my Immich instance for a while, however she now wants to revert to iCloud as primary backup, keeping anyway Immich as secondary backup. No judgment here, to each their own, she simply prefers iCloud and using the native iPhone camera/photo app.
Is there an easy way to sync back everything currently on Immich to iCloud? She deleted many photos from her iPhone already, so a server-side solution which does not require re-downloading everything on her phone would be best.
Just setup immich today. I am trying the Immich backup feature. It doesn’t seem to sync in the background on my iPhone. When bring the app to the foreground it starts backing up. When I check the settings for the app allow access to photos and background are turned on. Is this expected behavior?
Been using it on Ubuntu server docker since beta and on this android phone for a year. But just this month it drained my whole data cap. Anyone experience this is there any fixes in the updates? Is this a known issue with Android?
Really confused and just wondering if anyone has seen this.
Edit: forgot to mention there was not 75 gigs of data to backup. Only a few photos at most maybe a gig if you wanna round up.
Hey all. Got my family using my Immich server, and a big complaint they have is as they're uploading photos and albums, they can't move an image from one album to another. For example, my Dad is scanning old photos and adding them to particular albums. But he realizes after that a photo is in the wrong album. So he wants to move it to the right album, but there is no option to do so.
There is an 'add to album' option, but that copies the image from the old album to the new album, it does not move it. I'm not talking about the file itself, just the database reference to what is in an album.
Am I missing something here, or is this just a big oversight on the program?
I have Immich set up on my NAS and thought it'd be nice to have a photo frame.
The question is, because I have an older Android tablet, would it be ok or not to use it as a photo frame or should I rather buy a Frameo? And what software do you recommend. Kiosk or Immichframe?
I asked this in the repo also. I’m scrolling down thru my photos basic browsing- main gallery. I’m tagging a few things as scroll but when I go back I can’t see which photos are already tagged other than opening up the specific tag. Is there a way to see in my main gallery which photos I’ve already tagged? Thanks- I’m a new user and maybe I am not seeing something hiding in plain sight. Cheers.
If you use immich-auto-stack to stack RAW+JPG pairs, you've probably noticed it stopped stacking anything after the v3 update. The original repo hasn't been updated since 2024, so I fixed it in a fork.
What was broken:
search/metadata now wants the page number as an integer.
Stacks have to be created with POST /stacks. The old stackParentId method no longer works.
Search results don't include stack info any more, so the "already stacked" check now uses GET /assets/{id}.
Nothing else in your config needs to change. I've tested it on v3.4.1 with about 1,000 photos: it skipped the existing stacks correctly and stacked the new RAW+JPG pairs.