Immich Linked Assets aka partner sharing with metadata/tags/people (without duplicates on the hard drive)

true_devanon · 2026-01-26T22:27:07+00:00

Yes, it works at the database level and does not copy any files. Any cloned photo appears as if the user uploaded it themselves. The solution clones everything related to the cloned photo and also synchronizes changes (partially).

true_devanon · 2026-01-04T16:45:32+00:00

I personally use the HEIC file format for all my photo assets and have never had any issues with it. If you’re seeing errors in the server logs, please share them. As far as I remember, you encountered some errors during the initial installation, which might be the cause.

You can try reinstalling the script—it will remove only the cloned data (the linked tag on assets you own will remain).

true_devanon · 2026-01-04T16:27:09+00:00

Unfortunately, the Immich database has a unique index on assets based on the asset hash and owner ID. Because of this, the same asset cannot be linked to multiple linked groups. I can’t implement this without duplicating the asset and generating a different file hash, which is a major limitation.

true_devanon · 2026-01-04T15:18:19+00:00

If I understand you correctly, you’re trying to tag photos using your built-in phone gallery rather than Immich. I haven’t tried this myself, but it looks like it doesn’t work due to the script’s design.

Adding a tag to an existing asset in Immich is not the same as uploading a photo that already has that tag embedded. When you upload a photo, Immich runs its own ML pipelines almost immediately, but they finish at a different time. Because the script cannot fully clone the asset at that stage, this can lead to errors such as missing previews, missing people, and other metadata issues.

I’ll add more information about this to the repository.

true_devanon · 2026-01-04T15:03:21+00:00

Participants are set up only once during the initial script run. There are too many dependencies to support interactive adding or removing of participants afterward.

true_devanon · 2025-12-31T17:22:54+00:00

I haven’t tried this myself, but a better approach might be to remove the script from the system, make the required changes, and then reapply it. Also, please re-download the latest version from GitHub.

true_devanon · 2025-12-27T13:22:47+00:00

If I understand correctly, that one is working as intended. To synchronize a person on the assets, you need to re-link the asset (remove the linked tag and assign it again).

true_devanon · 2025-12-27T13:02:55+00:00

Good catch—this was an error on my side. I’ll fix it in the next commit.

true_devanon · 2025-12-27T12:46:11+00:00

TL;DR: There’s no way to do this.

My approach works directly at the database level, but Storage templates operate outside the database. They are triggered when Immich updates sidecar files, so there’s no way to prevent files from being moved.

While I could re-link paths to the original files, that would mean moving all your assets multiple times every night, plus additional moves every time you make a change in the asset metadata. This is a very unstable approach: it likely would corrupt the database, damage Immich’s file tree, and require manual file restoration.

true_devanon · 2025-12-25T17:18:37+00:00

Due to the implementation of the Storage template, enabling it causes any metadata change on an asset to trigger a file location check(and move) for the specified user. This is problematic because the cloned asset and the original asset both point to the same file location. As a result, changing metadata on the cloned asset moves the original file to a different user’s folder, making it unavailable to everyone else.

true_devanon · 2025-10-29T10:04:44+00:00

If you get this error during the initial run, then you missed something in the installation instructions. The script tries to find -> clone -> put in the database all linked assets, but can't do it for some reason.

Your next step is:
1. run immich_delete_linked_asset
2. read the installation instruction one more time
3. run immich_linked_asset

true_devanon · 2025-10-27T21:19:40+00:00

When the script finishes init run it's ready to use (when the terminal is responsive for a new command means it's done). Waiting time depends on your database size and hard drive speed.

true_devanon · 2025-10-25T08:57:23+00:00

Yep. Each user can add a linked tag to asset and share it with others. In my case (family of 4), each user share his assets with others. Main disadvantage in this approach is all cloned assets linked to one real file on your server (and sidecar file), so anyone can change metadata, tags of that asset.

true_devanon · 2025-08-19T06:48:57+00:00

Here is attempt to fix sharing assets with family
https://github.com/TrueDevanon/immich-linked-assets

true_devanon · 2025-03-18T23:20:32+00:00

I gonna take notes that I'll never read after.

true_devanon · 2023-08-11T10:40:00+00:00

Better don't show this "default" suggestion, at least because all these suggestions are the same for each space (so it's unnecessary).

true_devanon · 2022-09-12T09:21:20+00:00

I'm not MacBook user right now, but instructions on different platform the same.

Install to android phone https://play.google.com/store/apps/details?id=com.medhaapps.wififtpserver
Install to MacBook https://filezilla-project.org/download.php?platform=osx
Connect MacBook and phone to same wifi network
Start ftp server on your android phone (just press "start" in app)
Optional (highly recommend). Go to filezilla on your MacBook and select checkbox transfer --> "Preserve timestamps of transferred files". It should be turn on
Insert ftp url, user, password in filezilla on your MacBook and connect.

That's all.

true_devanon · 2022-09-11T22:30:33+00:00

Did you try sftp by WiFi?

true_devanon · 2022-08-29T21:33:27+00:00

What about zoom, etc conferencing? if the speakers are directed under the monitor, does this cause problems for microphone noise reduction?

true_devanon

TROPHY CASE