My biggest worry with Immich is how to future-proof the albums. With photos sorted into folders, it should be no problem to access them in a couple of decades. With Immich, I have to rely on the software still working or finding some kind of tool to dump the database.

I work on an image search engine[0], main idea has been to preserve all the original meta-data and directory structure while allowing semantic and meta-data search from a single interface. All meta-data is stored in a single json file, with original Path and filenames, in case ever to create backups. Instead of uploading photos to a server, you could host it on a cheap VPS with enough space, and instead Index there. (by default it a local app). It is an engine though and don't provide any Auth or specific features like sharing albums!

[0] https://github.com/eagledot/hachi

I use Single File PHP Gallery. Put the file in root dir of your photos and set it executable in web server. That's it. The settings are also inside the file, if you need any tweaking.

https://sye.dk/sfpg/

Don't storage templates handle this out of the box? I haven't actually checked my instance but that was my impression from reading the docs!

Although Immich does backup from your phone, I don't see it as a viable backup solution. Git-annex, Unison, and Syncthing are much better at keeping files synchronized across devices. Immich will create its own copies of photos and transcode videos for playback on the web. That may be fine if you have enough storage space, but for me it makes the phone backup useless. I suppose you could use a git-annex special remote directory as an Immich external library.

This was why I was driven to use Photoprism. I use syncthing-fork to upload from phones, and a custom made thing to copy them to folders (this also works with Cameras that aren't phones).

https://www.photoprism.app/

The database is Postgres, and the schema is quite sensible. You can (and I have) write normal SQL queries in psql to modify the data.

It might not be as easy as rsync to transfer data out, but I would trust it way more than some of the folder based systems I've had with local apps that somehow get corrupted/modified between their database and the local filesystem. And I don't think ext4 is somehow magically more futureproof than Postgres. And if no-one else writes an export tool, and you feel unable to, your local friendly LLM will happily read the schema and write the SQL for you.

I use photosync to upload to a folder that is an external library for immich. Immich then periodically scans that folder to load new assests. I usually use digikam to manipulate that folder. Immich is there just for easy remote browsing of those files.

I have the same concerns and that’s why I only use software which accept my directory structure as input and isn’t messing with it. I, for example, added my top directories of my image directory structure hand by hand each bit itself as a shared directory (read-only) to immich.

The main reason: I don’t trust software NOT deleting my photos. (Yes, I have an off-site) backup, but the restore would take time.

I remember that Immich has a mode to not use cryptic hashes but folders for storage. When I used it it was somehow deprecated due to some problems, but supported. I actually stopped using Immich because newer versions run the keep alive via socket.io with a Prostgres notify, which does constant empty WAL flushes, triggering empty page writes on idle.

Thank you, well put. thats why I am using next cloud and manual curation. Folders is the ultimate future proof structure. But I do see the value of a nice UI. But immich hides the files from me too much for my taste.

Although I am sure I can back them up to my PC somehow. But having them just on the server is not my favourite solution.

I share this worry.

You can configure the storage template for the photos and include an "album" part, so if a photo is in some album it'll get sorted into that folder. Then the file tree on disk is as you wish.

I haven't tested what it does when a photo is in multiple albums, but it does handle the no album case fine as well.

In the same boat. It seems there is API to export photos, so was thinking about some script that will export photos into separate folder and use hard links in order not to take more space.

This is what I like about Ente. I can pay them to give me an e2e encrypted cloud service, and then the desktop app has a continuous export feature that will dump everything into a plain folder structure on my home NAS automatically.

Ente could go out of business tomorrow and I’d still have all my photos, neatly organized into folders.

And I don’t have to bother with self-hosting overhead. Or I could self host, too, if I wanted. But I still need an off-site backup so I might as well pay for the cloud service.

At this point you could just point Claude code at the database and the image folder and ask it to write a migration script

This is why I still use Piwigo as I don't need to mess with file names and structure as far as I have seen.

As long as it is running on an open source database engine, I don't understand the difficulty.

You'll have plenty of time to write your exportation script before postgres ever disappear completely of all the bytes stored on our planet.

Also, are you saying you don't do backups?