immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-07-16 05:34:30 +03:00
Code Issues 783 Packages Projects Releases 22 Wiki Activity

Support user defined storage location/structure #16

New Issue
Closed
opened 2026-02-04 16:32:24 +03:00 by OVERLORD · 27 comments
OVERLORD commented 2026-02-04 16:32:24 +03:00
Owner
Copy Link

Originally created by @wjbeckett on GitHub (Feb 26, 2022).

Originally assigned to: @alextran1502 on GitHub.

I mentioned this on Reddit, but the user should be able to define how images are stored on the file system. This will not only allow for the user to choose how the images are named, but should allow Immich to index existing images.

Let's say I have an existing photos library where the photos are structured like this:
Photos |
|-> 2022
|-> 01
|-> filename.ext

Immich should respect the existing file structure and index the existing images.

While importing new photos, it should ask the user how the photos should be stored allowing the user to define the file structure above so that newly imported photos are placed in the correct place on the existing file system in the users defined folder structure.

Ideally, we should be able to define the filename pattern as well. Mine is currently date_timestamp_number.ext. for example, 2022-02-23-203109-001.jpeg

Originally created by @wjbeckett on GitHub (Feb 26, 2022). Originally assigned to: @alextran1502 on GitHub. I mentioned this on Reddit, but the user should be able to define how images are stored on the file system. This will not only allow for the user to choose how the images are named, but should allow Immich to index existing images. Let's say I have an existing photos library where the photos are structured like this: Photos | |-> 2022 |-> 01 |-> filename.ext Immich should respect the existing file structure and index the existing images. While importing new photos, it should ask the user how the photos should be stored allowing the user to define the file structure above so that newly imported photos are placed in the correct place on the existing file system in the users defined folder structure. Ideally, we should be able to define the filename pattern as well. Mine is currently date_timestamp_number.ext. for example, 2022-02-23-203109-001.jpeg
OVERLORD commented 2026-02-04 16:32:43 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Feb 26, 2022):

Thank you for your suggestion. I will consider this when the mobile app is stable and all the basic features are ironed out

@alextran1502 commented on GitHub (Feb 26, 2022): Thank you for your suggestion. I will consider this when the mobile app is stable and all the basic features are ironed out
OVERLORD commented 2026-02-04 16:32:53 +03:00
Author
Owner
Copy Link

@wjbeckett commented on GitHub (Mar 3, 2022):

So, I am the one who made the request for the external importer but you may be misinterpreting what I have said.
What I mean is this - most people in this sub will already have a bunch of photos on their servers/NAS stored in a way they prefer on the file system, for me, it’s a directory called photos and then sub folders as years (2022, 2021, 2020, etc) and then sub folders within them as months, and then the image files within that.

This is how I want my photos to be arranged and I don’t want another app changing that. What I would like is the app to accept my input as to how I want the images stored on the server/NAS and then move them there for me.

So, what Immich should be doing, is collecting the photos and videos off my device, grab the metadata along with that and pushing them to my server to sit in an “import” directory (or something similar). Then, the server app should scan that directory for any files, tag them based on the metadata, perform facial recognition, etc and then move the photos to their final testing place in my photo library that already exists on my file system and in the naming convention I expect them to be in.

This way Immich won’t just be an uploading too, it will be an image management app as well as a backup tool for my device images and a way to view my images on my server.

This is sort of the way Photoprism and similar app/servers work.

@wjbeckett commented on GitHub (Mar 3, 2022): So, I am the one who made the request for the external importer but you may be misinterpreting what I have said. What I mean is this - most people in this sub will already have a bunch of photos on their servers/NAS stored in a way they prefer on the file system, for me, it’s a directory called photos and then sub folders as years (2022, 2021, 2020, etc) and then sub folders within them as months, and then the image files within that. This is how I want my photos to be arranged and I don’t want another app changing that. What I would like is the app to accept my input as to how I want the images stored on the server/NAS and then move them there for me. So, what Immich should be doing, is collecting the photos and videos off my device, grab the metadata along with that and pushing them to my server to sit in an “import” directory (or something similar). Then, the server app should scan that directory for any files, tag them based on the metadata, perform facial recognition, etc and then move the photos to their final testing place in my photo library that already exists on my file system and in the naming convention I expect them to be in. This way Immich won’t just be an uploading too, it will be an image management app as well as a backup tool for my device images and a way to view my images on my server. This is sort of the way Photoprism and similar app/servers work.
OVERLORD commented 2026-02-04 16:32:59 +03:00
Author
Owner
Copy Link

@ippocratis commented on GitHub (Mar 4, 2022):

I agree with the year/month/day folder structure but I don't want to push the dev
Its his app after all
I see that immich is crazy fast in loading and displaying immages appar to how fast google photos loads cloud images. That crazy fast
So I really want this app to grow so I can use it.
The truth is that if the feature to add to immich server photos already on the server machine is not somehow imlemented it is not going to be any usable

@ippocratis commented on GitHub (Mar 4, 2022): I agree with the year/month/day folder structure but I don't want to push the dev Its his app after all I see that immich is crazy fast in loading and displaying immages appar to how fast google photos loads cloud images. That crazy fast So I really want this app to grow so I can use it. The truth is that if the feature to add to immich server photos already on the server machine is not somehow imlemented it is not going to be any usable
OVERLORD commented 2026-02-04 16:33:03 +03:00
Author
Owner
Copy Link

@nijhawank commented on GitHub (Mar 22, 2022):

+1. I also have my existing photos in year/month/photo.ext structure that I want to be able to access via Immich. It would be a good idea if Immich simply indexes them in-place without requiring them to be imported/duplicated into another location.

@nijhawank commented on GitHub (Mar 22, 2022): +1. I also have my existing photos in year/month/photo.ext structure that I want to be able to access via Immich. It would be a good idea if Immich simply indexes them in-place without requiring them to be imported/duplicated into another location.
OVERLORD commented 2026-02-04 16:33:17 +03:00
Author
Owner
Copy Link

@JamesTeague commented on GitHub (Mar 30, 2022):

Adding to the request, this would be great. It's something that I think a lot of people want, being autonomy over their server file structure. This will allow other things to play nice with the files too, I believe. This is something I'd personally love to see in here and I think many others would to.

@JamesTeague commented on GitHub (Mar 30, 2022): Adding to the request, this would be great. It's something that I think a lot of people want, being autonomy over their server file structure. This will allow other things to play nice with the files too, I believe. This is something I'd personally love to see in here and I think many others would to.
OVERLORD commented 2026-02-04 16:33:20 +03:00
Author
Owner
Copy Link

@Akruidenberg commented on GitHub (Apr 6, 2022):

+1 for me.

@Akruidenberg commented on GitHub (Apr 6, 2022): +1 for me.
OVERLORD commented 2026-02-04 16:33:30 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Apr 6, 2022):

+1. I also have my existing photos in year/month/photo.ext structure that I want to be able to access via Immich. It would be a good idea if Immich simply indexes them in-place without requiring them to be imported/duplicated into another location.

Noted, this is a different scope of the project though. I will let you know when I implement a CLI tool for this.

@alextran1502 commented on GitHub (Apr 6, 2022): > +1. I also have my existing photos in year/month/photo.ext structure that I want to be able to access via Immich. It would be a good idea if Immich simply indexes them in-place without requiring them to be imported/duplicated into another location. Noted, this is a different scope of the project though. I will let you know when I implement a CLI tool for this.
OVERLORD commented 2026-02-04 16:33:36 +03:00
Author
Owner
Copy Link

@mokahless commented on GitHub (Aug 8, 2022):

Ah I was just starting to investigate the best way to expose my smb share to immich in its container and came across this thread. I actually don't care about adding photos through immich and just want it to add photos I've put on my smb share automatically, without duplicating them or renaming them or moving them.

Since it hasn't been mentioned yet, I'll mention that photoprism refers to this as "indexing" for original directories.

@mokahless commented on GitHub (Aug 8, 2022): Ah I was just starting to investigate the best way to expose my smb share to immich in its container and came across this thread. I actually don't care about adding photos through immich and just want it to add photos I've put on my smb share automatically, without duplicating them or renaming them or moving them. Since it hasn't been mentioned yet, I'll mention that photoprism refers to this as "indexing" for original directories.
OVERLORD commented 2026-02-04 16:33:37 +03:00
Author
Owner
Copy Link

@wiseindy commented on GitHub (Aug 10, 2022):

+1 Would love to be able to use my existing photo library with Immich

@wiseindy commented on GitHub (Aug 10, 2022): +1 Would love to be able to use my existing photo library with Immich
OVERLORD commented 2026-02-04 16:33:55 +03:00
Author
Owner
Copy Link

@reejosamuel commented on GitHub (Aug 22, 2022):

+1 to this.

@reejosamuel commented on GitHub (Aug 22, 2022): +1 to this.
OVERLORD commented 2026-02-04 16:34:02 +03:00
Author
Owner
Copy Link

@Ewalda commented on GitHub (Aug 22, 2022):

+1
SynologyPhotos (NAS) use following similar file structure for standard backup mobile devices:

MobileBackup///month
The device name is e.g. iphone name which the user give to his phone e.g. "Toms Iphone". In Immich is currently a cryptic Id a name would be better.

Parallel to that the user can create free defined other folders, which are also included in the photo database. And inside this folders also free defined sub folders are possible. This structure is necessary for sorting a lot of images to several events.

Additional the original date and time of the image and the movies is set to the modified date and time of the file system. Immich uses the upload time in the file system.
Additional it either uses the original name of the mobile device or it can be selected to rename the filename to IMG_yyyyMMdd_HHmmss (If there is already a file with this name it will be renames by adding _1 ...) <= This naming is often used by mobile phones and cameras for photos and videos. Immich uses a random UUID (asset-upload.config.ts fileNameUUID = randomUUID()).

It would be very good if Immich can do it similar. Immich mobile backup is much faster than synology photos. (I believe also other things are faster! Very Good! But I have not yet so much photos in Immich.)

All that things are very essential if the database crashes (what happens to me on the synology database). It is possible to rebuild the database by this file system structure! Also for files (videos) with no Exif Data! Also the sorted directory structure is still there, albums are only stored in the database.

We have above 1 000 000 photos currently sorted by this way.

Additional information to albums:
Only a flat album structure is not enough to sort so many photos at least sub albums should be supported (Synology photos also don't support sub albums, therefore and because of database problems I sort it in the directories. But because of avoiding duplicates, albums would be better! )

@Ewalda commented on GitHub (Aug 22, 2022): +1 SynologyPhotos (NAS) use following similar file structure for standard backup mobile devices: MobileBackup/<deviceName>/<year>/month The device name is e.g. iphone name which the user give to his phone e.g. "Toms Iphone". In Immich is currently a cryptic Id a name would be better. Parallel to that the user can create free defined other folders, which are also included in the photo database. And inside this folders also free defined sub folders are possible. This structure is necessary for sorting a lot of images to several events. Additional the original date and time of the image and the movies is set to the modified date and time of the file system. Immich uses the upload time in the file system. Additional it either uses the original name of the mobile device or it can be selected to rename the filename to IMG_yyyyMMdd_HHmmss (If there is already a file with this name it will be renames by adding _1 ...) <= This naming is often used by mobile phones and cameras for photos and videos. Immich uses a random UUID (asset-upload.config.ts fileNameUUID = randomUUID()). It would be very good if Immich can do it similar. Immich mobile backup is much faster than synology photos. (I believe also other things are faster! Very Good! But I have not yet so much photos in Immich.) All that things are very essential if the database crashes (what happens to me on the synology database). It is possible to rebuild the database by this file system structure! Also for files (videos) with no Exif Data! Also the sorted directory structure is still there, albums are only stored in the database. We have above 1 000 000 photos currently sorted by this way. Additional information to albums: Only a flat album structure is not enough to sort so many photos at least sub albums should be supported (Synology photos also don't support sub albums, therefore and because of database problems I sort it in the directories. But because of avoiding duplicates, albums would be better! )
OVERLORD commented 2026-02-04 16:34:07 +03:00
Author
Owner
Copy Link

@fivestones commented on GitHub (Aug 26, 2022):

I'd like to have this feature too

@fivestones commented on GitHub (Aug 26, 2022): I'd like to have this feature too
OVERLORD commented 2026-02-04 16:34:15 +03:00
Author
Owner
Copy Link

@eckebusch commented on GitHub (Aug 27, 2022):

+1 to this

@eckebusch commented on GitHub (Aug 27, 2022): +1 to this
OVERLORD commented 2026-02-04 16:34:22 +03:00
Author
Owner
Copy Link

@Txxicer commented on GitHub (Aug 28, 2022):

+1

@Txxicer commented on GitHub (Aug 28, 2022): +1
OVERLORD commented 2026-02-04 16:34:26 +03:00
Author
Owner
Copy Link

@zkhan93 commented on GitHub (Sep 11, 2022):

+1 to this feature as it also makes the app more "safe".
love the app thank you so much!

@zkhan93 commented on GitHub (Sep 11, 2022): +1 to this feature as it also makes the app more "safe". love the app thank you so much!
OVERLORD commented 2026-02-04 16:34:30 +03:00
Author
Owner
Copy Link

@ggantn commented on GitHub (Oct 1, 2022):

+1 for me.

@ggantn commented on GitHub (Oct 1, 2022): +1 for me.
OVERLORD commented 2026-02-04 16:34:35 +03:00
Author
Owner
Copy Link

@Spectre5 commented on GitHub (Oct 3, 2022):

I'd also love the ability to just index an existing directory tree. I have my photos already organized in a meticulous way within various subdirectories that are meaningful for me. I'd like to load this share/directory as read-only in Immich to be sure nothing in it changes.

@Spectre5 commented on GitHub (Oct 3, 2022): I'd also love the ability to just index an existing directory tree. I have my photos already organized in a meticulous way within various subdirectories that are meaningful for me. I'd like to load this share/directory as read-only in Immich to be sure nothing in it changes.
OVERLORD commented 2026-02-04 16:34:47 +03:00
Author
Owner
Copy Link

@DawidPietrykowski commented on GitHub (Oct 6, 2022):

I also agree that such feature would be a great addition to the app. For me it's the only thing holding me back from ditching Plex, the loading/viewing speed of Immich could make it a great photo gallery/browser for a NAS.

@DawidPietrykowski commented on GitHub (Oct 6, 2022): I also agree that such feature would be a great addition to the app. For me it's the only thing holding me back from ditching Plex, the loading/viewing speed of Immich could make it a great photo gallery/browser for a NAS.
OVERLORD commented 2026-02-04 16:34:53 +03:00
Author
Owner
Copy Link

@kenzot11 commented on GitHub (Nov 2, 2022):

+1 for me

@kenzot11 commented on GitHub (Nov 2, 2022): +1 for me
OVERLORD commented 2026-02-04 16:34:58 +03:00
Author
Owner
Copy Link

@nijhawank commented on GitHub (Dec 18, 2022):

I assume this only stores photos uploaded via Immich to be stored in the specified folder/file structure. But this does not indexes photos in existing folder (not uploaded via Immich) and makes them available via Immich, is the understanding correct?

@nijhawank commented on GitHub (Dec 18, 2022): I assume this only stores photos uploaded via Immich to be stored in the specified folder/file structure. But this does not indexes photos in existing folder (not uploaded via Immich) and makes them available via Immich, is the understanding correct?
OVERLORD commented 2026-02-04 16:35:03 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Dec 18, 2022):

I assume this only stores photos uploaded via Immich to be stored in the specified folder/file structure. But this does not indexes photos in existing folder (not uploaded via Immich) and makes them available via Immich, is the understanding correct?

@nijhawank that is correct, the scanning feature is not yet implemented. You can find a more detailed discussion here #1006

@alextran1502 commented on GitHub (Dec 18, 2022): > I assume this only stores photos uploaded via Immich to be stored in the specified folder/file structure. But this does not indexes photos in existing folder (not uploaded via Immich) and makes them available via Immich, is the understanding correct? @nijhawank that is correct, the scanning feature is not yet implemented. You can find a more detailed discussion here #1006
OVERLORD commented 2026-02-04 16:35:07 +03:00
Author
Owner
Copy Link

@arnoudius commented on GitHub (Feb 19, 2023):

+1, would be nice if this could be supported

@arnoudius commented on GitHub (Feb 19, 2023): +1, would be nice if this could be supported
OVERLORD commented 2026-02-04 16:35:12 +03:00
Author
Owner
Copy Link

@amokster88 commented on GitHub (Apr 2, 2023):

+1, i would love this and I just deployed this and I am loving this. Can't thank you enough Devs. Keep it up, I hope more people start supporting this project.

@amokster88 commented on GitHub (Apr 2, 2023): +1, i would love this and I just deployed this and I am loving this. Can't thank you enough Devs. Keep it up, I hope more people start supporting this project.
OVERLORD commented 2026-02-04 16:35:21 +03:00
Author
Owner
Copy Link

@poisonborz commented on GitHub (Jun 9, 2023):

+1, even though I'm in awe of what Immich became , for now this is a dealbreaker for me.
I already have an established photo structure which I expose through multiple services. I'd only share this folder as read only with any container, as I wouldn't risk them corrupting or modifying them in a way I don't expect. Metadata/thumbnails should be stored separately. Good (even though different scope) examples for this behaviour would be PiGallery 2 or Nextcloud.

@poisonborz commented on GitHub (Jun 9, 2023): +1, even though I'm in awe of what Immich became , for now this is a dealbreaker for me. I already have an established photo structure which I expose through multiple services. I'd only share this folder as read only with any container, as I wouldn't risk them corrupting or modifying them in a way I don't expect. Metadata/thumbnails should be stored separately. Good (even though different scope) examples for this behaviour would be PiGallery 2 or Nextcloud.
OVERLORD commented 2026-02-04 16:35:23 +03:00
Author
Owner
Copy Link

@charles-997 commented on GitHub (Jun 25, 2023):

As an update, this feature has been added. See docs here
https://immich.app/docs/features/read-only-gallery

@charles-997 commented on GitHub (Jun 25, 2023): As an update, this feature has been added. See docs here https://immich.app/docs/features/read-only-gallery
OVERLORD commented 2026-02-04 16:35:26 +03:00
Author
Owner
Copy Link

@zilexa commented on GitHub (Jul 2, 2023):

Perhaps allow to set a global default of the "External Path", relative to the user path.
Like %userfiles%/%username%/Pictures
Each user would have their photos in a subfolder inside their userfolder called Pictures (or Photos or Albums or whatever).

@zilexa commented on GitHub (Jul 2, 2023): Perhaps allow to set a global default of the "External Path", relative to the user path. Like %userfiles%/%username%/Pictures Each user would have their photos in a subfolder inside their userfolder called Pictures (or Photos or Albums or whatever).
OVERLORD commented 2026-02-04 16:35:34 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Jul 2, 2023):

You can already do this by prefixing the storage template with Pictures and by setting up your volume mounts for the external path relative to the upload location.

@jrasm91 commented on GitHub (Jul 2, 2023): You can already do this by prefixing the storage template with Pictures and by setting up your volume mounts for the external path relative to the upload location.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#16
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?