[Feature] Automatic creation of albums in external libraries

[dharapvj]

The bug

Erstwhile --import option from immich CLI also supported an -al option due to which the folders from external library getting imported would also create albums.

Now with new External Library feature, photos are getting imported natively but they are not creating Albums.

The OS that Immich Server is running on

podman on ubuntu

Version of Immich Server

v1.79.0

Version of Immich Mobile App

v1.79.0

Platform with the issue

• Server
• Web
• Mobile

Your docker-compose.yml content

Same as docker-compose.yaml on immich github.

Your .env content

No special configuration relevant to this bug

Reproduction steps

1. Add external library as volume in docker-compose file
2. Add external library in user -> account settings
3. Let jobs finish all imports
4. Check albums page to see that there are no albums created

Additional information

No response

[Gatherix]

This doesn't seem like a bug, though it would be a much appreciated feature

[dharapvj]

i thought of it as a bug because I felt External library feature as a "natural progression" of import feature in CLI and that feature offered album creation.

[wechsler42]

Well, I second that. Automatic creation of albums from external libraries would be really a nice feature .

[jrasm91]

Definitely not a bug, since it was never designed to do that in the first place. A feature request is more appropriate though. There are actually a lot of library enhancement requests, so it would be good to make a list and include this one as well.

[swap83]

#4186

[alvistar]

Hello,
I had the same issue. For quick and dirty workaround I wrote a python script to create albums from file structure

https://github.com/alvistar/immich-albums

Main issue is that the script needs also access directly to postgres as API to lookup an asset by oiriginal path is not exposed in the controller.

I am sharing hoping this can help somehow and eventually this functionality will be integrated in CLI.

[alvistar]

Hello, sorry was just for lack of time...

#4352

It should be very trivial to implement, but as you know, doing a proper patch with test, pr, etc takes some time.

[etnoy]

This is now competed, feel free to use the new search api implemented in #4931

[etnoy]

And with the 1.88 release, this new API is available for everyone

[alexanderhuzar]

I for the life of me can't get this script working. No matter what I do it ends up with:
"can't open file '/app/immich_folder_album_creator.py': [Errno 2] No such file or directory".

[pin147]

Try this one. An updated version that can also be automated.
https://github.com/Salvoxia/immich-folder-album-creator

[etnoy]

Hello, I had the same issue. For quick and dirty workaround I wrote a python script to create albums from file structure

https://github.com/alvistar/immich-albums

Main issue is that the script needs also access directly to postgres as API to lookup an asset by oiriginal path is not exposed in the controller.

I am sharing hoping this can help somehow and eventually this functionality will be integrated in CLI.

that looks very nice. Maybe you can open a feature request to expose that API? We absolutely want to support external API access for relevant usecases :)

[PJGitHub9]

Yeah same issue here. When i try use the import flag, it asks me if i want to upload all the images which i dont want to do.

[cristiangauma]

For me, this is the last step before migrating to Immich. With this feature, the amount of people that will migrate to Immich will be really huge :). Can't wait to see this implemented!

[etnoy]

Can you give a more detailed explanation of how this feature would work?

[nikolajhendel]

maybe the most flexible option is to use metadata tags (folder?) which can then be used to search based on metadata and manually create an album?
Looking at how photoprism has "done it" there is a folder view (not metadata as such) which allows you to browse - select all photos and manually create an album.

A solution like this takes away any direct coupling of folders and albums - but makes it very easy to manually create albums based on folder structure.
What would probably help is a metadata viewer in immich, as right now it only looks like you can search (and have to know your metadata tags) - I may be wrong, as I'm new to using/trying Immich.

[alextran1502]

@nikolajhendel

and have to know your metadata tags

We use contextual search (CLIP), so it doesn't actually generate a tag but an array of numbers which will be compared to with the encoded search phase you put in.

[etnoy]

maybe this can be done in a one-shot command, possibly from the (new) cli. Click a button and it'll create albums but without any two-way linking

[andyxpert]

And a job to allow for easy triggering library creation (one way from external library)

[mooglestiltzkin]

just wanted to point out, with photoprism, they can create albums by browsing folders then select those pics and create an album for that. that is very fast DESPITE not being an auto album creation. At the very least u can browse existing folders where pics may have already been put into and create albums from that.

whereas immich, it puts them ALL into one single search to mix up all the pics despite being physically in separate folders from the start. Then expects you to create an album by selecting images 1 by 1 from all that jumbled up mess.

i'm no expert but that just seems to be counter productive :{

[tsemachh]

I see it's on discord in alex todo
Will be happy to see it soon.

[maltokyo]

I would also completely migrate to immich if we had this. All of my photos are on the hard drive in a directory called "Photos", curated like this, where of course "Album_N" is a manually input description of the event.

Photos/YYYYMM Album_1
Photos/YYYYMM Album_2
Photos/YYYYMM Album_3

I have 1000s of such directories, curated over the years, as I am sure most avid photographers have... It would be great if we could use the info in a directory structure that is already there!

[davidacampos]

Had the same issue as the rest... existing collection with many folders but now showing "flat" in Immich, so I created a quick and dirty JavaScript snippet that helped me create those.

How it works?

1. Gets all existing assets (photos/videos). This might take a while, in my case the generated JSON was over 100MB.
2. Goes through each one of them, and if they have the originalPath value (I assume that's only for external? I don't have non-external assets) extract the top folder from it and add it to our list of albums to create.
3. With the list of top folders, create albums and include the assets as needed.

For me this is good enough as it's a one-time thing. It currently doesn't handle re-running the script (i.e. removing autogenerated albums and recreating them) meaning you will need to remove the auto-generated albums to start from scratch (is there tagging for albums in Immich? this could help to tag remove them easily).

To run, navigate to Immich's web app in a browser (tested in Chrome), and copy&paste it to the "console" and run it. Make sure to change as needed under the PARAMETERS section of the snippet:

(async function () {

    //** PARAMETERS */
    /***********************************************************/
    let immichHost = "https://IMMICH_HOST";
    let rootPath = "/mnt/pictures/"; // This will be used as the "root" folder... meaning albums will be created based on folders directly under "root" (e.g. /mnt/pictures/ChristmasHoliday will end up as album "ChristmasHoliday")
    let foldersToExclude = []; // Optional, this is to exclude folders from been created as albums
    let albumGenerationLimit = 5; // Max number of albums auto-generated. Need to change to something like 9999 to create all albumos
    /***********************************************************/

    let assets = await (await fetch(immichHost + "/api/asset", {
        "body": null,
        "method": "GET",
        "mode": "cors",
        "credentials": "include"
    })).json();

    let albumsWithAssets = {};
    assets.forEach(asset => {
        if (asset.originalPath) {
            let folder = asset.originalPath.replace(rootPath, "").split("/")[0];

            if (foldersToExclude.includes(folder) == false) {
                if (!albumsWithAssets[folder]) {
                    albumsWithAssets[folder] = {
                        assets: []
                    }
                }

                albumsWithAssets[folder].assets.push(asset.id);
            }
        }
    });

    Object.keys(albumsWithAssets).forEach(async (folder, index) => {

        let body = {
            albumName: folder,
            assetIds: albumsWithAssets[folder].assets
        }

        if (index < albumGenerationLimit) { // Limits the number of albums auto-generated, mainly for testing purposes
            setTimeout(async function () {
                await fetch(immichHost + "/api/album", {
                    "headers": {
                        "accept": "application/json, text/plain, */*",
                        "content-type": "application/json",
                    },
                    "body": JSON.stringify(body),
                    "method": "POST",
                    "mode": "cors",
                    "credentials": "include"
                });
                console.log("Created album [" + index + "/" + Object.keys(albumsWithAssets).length + "] for: " + folder);
            }, index * 250); // Space out each album creation by 250ms to not hit all at once
        }

    });

})()

[davidacampos]

It should still work. As a matter of fact, I just published an updated version as a gist and added an option to be able to re-run the script (i.e. it removes existing folders and create them again).

I just tried it with 1.98.1 and it works.

Is your rootPath parameter correct? In my case my shared folder is mounted in /mnt/pictures/ so my folders are something like /mnt/pictures/FolderA. Do you have more than 3 folders at that level (the script doesn't create albums for sub-folders, just per folders at the root level)?

[koen81]

Thanks for getting back to me, so I have added 3 external libraries added to Immich:

photos_shared (/mnt/media/photos_shared) contains 101 directories
photos_koen (first name :)) (/mnt/media/photos_koen excluded mobile_upload as that has a different structure) contains 110 directories
photos_mobile upload: (/mnt/media/photos_koen/mobile_upload)

I wanted to run the script for each of the different external libraries (perhaps that's my mistake here, as it creates 3 directories, which corresponds to the number of external libraries I have);

So my settings in the script have been;

let immichHost = "http://192.168.1.XX:XXXX";
let rootPath = "/mnt/media/photos_shared/";
let foldersToExclude = [];
let albumGenerationLimit = 999;

Sorry for the late reply.

[aronmgv]

Just wondering if somebody tried to extend the script to consider nested folders as well? So we would have separate album for each leaf folder and name would be the whole "path":

• @cars/Kamiq/2021
• @cars/Kamiq/2022
• @cars/Kodiaq/2023
• @cars/Kodiaq/2024
• @skiing/Apls/2023/January
• @skiing/Apls/2023/February

and so.. thanks!

[miguelarios]

@davidacampos i am getting an error on the forEach unsure how to unblock this.

[davidacampos]

@davidacampos i am getting an error on the forEach unsure how to unblock this.

Are you using the "gist" version?

The one at the beginning of this thread is old and doesn't work in newer versions of Immich.

[mooglestiltzkin]

@davidacampos this actually worked for me.

i went to here
http://my immich ip:2283/photos

then press F12 in browser, this opens up console.

I copied your code to note++ to edit.

i edited the following

let immichHost = "http://my immich lan ip:2283";

let rootPath = "/mnt/media/";

let albumGenerationLimit = 999;

fyi for reference my docker compose volumes for pics are like this

- /share/CACHEDEV4_DATA/Storage/Pictures/Belle:/mnt/media/Belle:ro

then i copied the edited code into the console, then ran it. and it successfully created the albums.

Ty you so much. hopefully the devs add this into the immich app gui as an action button or something. it's so simple to use.

*update

based on the maintainers advice, i opted to remove the quote above (which had the full script) for every1s safety as a precaution. if you want to see the original, refer to the original poster davidacampos who posted above.

what i did leave though is the parts i modified. very minimal edits and you can see for yourself they don't do anything by itself. i only commented based on his code what i changed to get it to work for me.

[alextran1502]

Just general information for you. Not relating to Immich.

It is not wise to post random javascript snippets to your browser's console, especially if you don't understand what the code does. This is an easy way to get hacked.

[mooglestiltzkin]

correct. and ty for the warning. i'm no pro coder, but i can read the code somewhat, and it seemed pretty benign (plz dont take my word for this, like i said i'm no expert). this is the very first thing i did before i considered trying (but yes you are absolutely correct, normally you should not do this especially if you don't understand the code as to what it is doing). and that's why i wanted to confirm for others it actually did what it purported to do.

maybe others who know more about code can also confirm the code is not malicious and does what it claims. i tested myself and worked for me.

i also tested browsing the albums using a different device using the immich android app (no i did not enter any code on that device). albums created from before are working there too just fine.

[AverTry]

Thanks for the walkthrough, I had a few problems though as for the host with /photos causes the script to fail.
worked fine after that.

[thorsten-hehn]

@davidacampos this actually worked for me.

i went to here http://my immich ip:2283/photos

then press F12 in browser, this opens up console.

I copied your code to note++ to edit.

i edited the following

let immichHost = "http://my immich lan ip:2283";

let rootPath = "/mnt/media/";

let albumGenerationLimit = 999;

fyi for reference my docker compose volumes for pics are like this

- /share/CACHEDEV4_DATA/Storage/Pictures/Belle:/mnt/media/Belle:ro

then i copied the edited code into the console, then ran it. and it successfully created the albums.

Ty you so much. hopefully the devs add this into the immich app gui as an action button or something. it's so simple to use.

*update

based on the maintainers advice, i opted to remove the quote above (which had the full script) for every1s safety as a precaution. if you want to see the original, refer to the original poster davidacampos who posted above.

what i did leave though is the parts i modified. very minimal edits and you can see for yourself they don't do anything by itself. i only commented based on his code what i changed to get it to work for me.

Thanks @mooglestiltzkin for the guide. Without it, I would have failed since I did not not what @davidacampos meant by "console".

[mooglestiltzkin]

Thanks @mooglestiltzkin for the guide. Without it, I would have failed since I did not not what @davidacampos meant by "console".

no problem.

i removed the code just in case.

since i last posted, seems others have come up with other solutions, with their own githubs. but i'm not sure if their code is legit or not. wish there was an official solution :/ less worry xd.

But yes i did test the code previously it did work, but i don't know if malicious stuff got added or not. i'm not a coder :{

[alvistar]

Hi all,
I have updated https://github.com/alvistar/immich-albums python script to remove database requirement and use the new api

It still needs some love regarding documentation but the script is working.

Thanks everybody,
a.

[maltokyo]

meh folders?

[amit-handa]

sorry, meh folders => I meant there were spurious folders (having no images) in the path. and script created an album for each folder

[amit-handa]

update: in the weekend. I did deep dive. after album creation, I updated one of the files but the album thumbnail were not updated :( filed a possible issue

[nghiemlong]

Hi alvistar,
I installed pipx, poetry, poetry shell. Then run the shell using: "poetry shell".
Then I run "im --help", error message:
"(immich-albums-py3.13) C:\dev\tools\immich-albums>im --help
'im' is not recognized as an internal or external command,
operable program or batch file."

I am new to poetry, so I don't know how to continue. Pls help!. Thank you.

[nghiemlong]

Windows error, I change to Linux and can run im.py from the poetry console. But when creating albums, it raise not found connection error:

"Exception when calling create_album: (404)
Reason: Not Found
HTTP response headers: HTTPHeaderDict({'X-Powered-By': 'Express', 'x-immich-cid': 'zzw38i0o', 'Content-Type': 'application/json; charset=utf-8', 'Content-Length': '100', 'ETag': '"64-BFSXuOvL+u4UQYhX51cE2AwxLWQ"', 'Date': 'Sun, 23 Mar 2025 19:02:40 GMT', 'Connection': 'keep-alive', 'Keep-Alive': 'timeout=5'})
HTTP response body: {"message":"Cannot POST /api/album","error":"Not Found","statusCode":404,"correlationId":"zzw38i0o"}"

You can see that the message is "cannot POST to /api/album".

Yes, "/api/album" does not exists, because with Immich 1.129 i am using, the path should be "/api/albums" (link: https://immich.app/docs/api/create-album)

I don't know how to fix that.

[snakuzzo]

I just shared a small Python script that creates albums in Immich based on your local folder structure using the Immich API. It scans your media folders and auto-generates albums accordingly

https://github.com/snakuzzo/immich-album-creator

[uchimata2]

Hey all,

If the search function were improved to find patterns in the full path of the file, then manual album creation would be awesome for external libraries. For me it would simply do all my dreams. E.g.:

Search pattern: "joe archive nepal"
Matching photos: "/mnt/NAS/Photos/JoeArchive/2020_Nepal/IMG112313.jpg"
NOT matching photos: "/mnt/NAS/Photos/JaneArchive/1992_Nepal_Concert/DSCF4411333.jpg"

This way I could find the photos across multiple directories which are preorganized in the external folder structures, so I could select them all in Immich and assign them to a new album. It provides even more flexibility compared to the Ext lib folder strucure --> Album name mechanism. What do you think?

BTW, Immich is just a gemstone, I love U guys!!!

[Otiel]

You should try https://github.com/Salvoxia/immich-folder-album-creator, I believe you can do this with all its filter options

[RamblinWreck77]

9/19/25 and this is still missing

I was shocked when I tried this on recommendation of a lot of different home-labers only to find immich can't handle a basic folder structure.

What is going on upstairs?

[maltokyo]

Not even Google photos has nested albums

[bphenriques]

I may understand your situation but you can always contribute if you think it is trivial. Donations .. are donations .. not a way to feel entitled to demand features. Especially in a language that I do not consider respectful.

[Lordx3n0saeon]

FWIW I'm migrating from synology photos, which handles this very well in my opinion.

[jakoss]

It's a real shame as this project has so much potential, but doesn't seem to be prioritizing the things that would grow adoption.

Do you have any data that proves that this is some kind of show stopper for adoption? Or do you just assume that problems that you have are the most fundamental? This is purely anecdotal.

I would like to have the feature, but I live without it just fine and gladly pay my share to keep the project going. I might not agree with some stuff and prioritization, but it's their project.

[Lordx3n0saeon]

It's a real shame as this project has so much potential, but doesn't seem to be prioritizing the things that would grow adoption.

Do you have any data that proves that this is some kind of show stopper for adoption? Or do you just assume that problems that you have are the most fundamental? This is purely anecdotal.

I would like to have the feature, but I live without it just fine and gladly pay my share to keep the project going. I might not agree with some stuff and prioritization, but it's their project.

All the people leaving angry/frustrated comments over years are potential users (and subscribers/donors).

a quick low effort search finds many comments saying they would pay for this feature, or that it is preventing them from moving to immich

https://www.reddit.com/r/immich/comments/1crux8h/nested_albums/

https://www.reddit.com/r/immich/comments/1kop5qu/comment/ncby9vc/

https://www.reddit.com/r/immich/comments/1kop5qu/comment/msrska6/

I also did try folder view, but it doesn't work well on mobile/feels tacked on.

[MrSimmo]

Would this work as a branch for testing? I haven't had time to clone the repo and look into it properly but might be a useful start to someone. It's probably missing some vital code but just my thoughts...

The idea is:

• Files in /August 2025/img123.jpg will automatically create an album named "August 2025"
• Multiple files in the same folder will be grouped into the same album
• Existing albums with the same name will be reused
• The feature works during both initial scans and incremental updates

1. server/src/services/library.service.ts
Add album creation logic in the library scanning process:

// Add this import at the top
import { IAlbumRepository } from 'src/interfaces/album.interface';

// Inject AlbumRepository in the constructor
constructor(
  // ... existing dependencies
  @Inject(IAlbumRepository) private albumRepository: IAlbumRepository,
) {}

// Modify the handleAssetRefresh or scanAssets method
async scanAssets(library: LibraryEntity, importPaths: string[]): Promise<void> {
  // ... existing scanning logic
  
  // Track folder-to-album mapping
  const folderAlbums = new Map<string, string>();
  
  for (const asset of discoveredAssets) {
    // Extract folder name from asset path
    const folderName = path.basename(path.dirname(asset.originalPath));
    
    // Skip if folder is root or empty
    if (!folderName || folderName === '.' || folderName === '..') {
      continue;
    }
    
    // Check if album already exists for this folder
    if (!folderAlbums.has(folderName)) {
      // Create or find album
      const album = await this.findOrCreateAlbum(library.ownerId, folderName);
      folderAlbums.set(folderName, album.id);
    }
    
    // Add asset to album
    const albumId = folderAlbums.get(folderName);
    if (albumId && asset.id) {
      await this.albumRepository.addAssets({
        albumId,
        assetIds: [asset.id],
      });
    }
  }
}

// Add helper method
private async findOrCreateAlbum(userId: string, folderName: string) {
  // Check if album with this name exists
  const existingAlbum = await this.albumRepository.getByName(userId, folderName);
  
  if (existingAlbum) {
    return existingAlbum;
  }
  
  // Create new album
  return await this.albumRepository.create({
    ownerId: userId,
    albumName: folderName,
    description: `Auto-created from folder: ${folderName}`,
  });
}

2. server/src/interfaces/album.interface.ts
Add method signature for finding albums by name:

export interface IAlbumRepository {
  // ... existing methods
  
  getByName(userId: string, name: string): Promise<AlbumEntity | null>;
  addAssets(data: { albumId: string; assetIds: string[] }): Promise<void>;
}

3. server/src/repositories/album.repository.ts
Implement the new repository method:

async getByName(userId: string, name: string): Promise<AlbumEntity | null> {
  return this.repository.findOne({
    where: {
      ownerId: userId,
      albumName: name,
    },
  });
}

async addAssets({ albumId, assetIds }: { albumId: string; assetIds: string[] }): Promise<void> {
  // Add assets to album_assets_assets junction table
  await this.repository
    .createQueryBuilder()
    .relation(AlbumEntity, 'assets')
    .of(albumId)
    .add(assetIds);
}

4. server/src/dtos/system-config.dto.ts
Add configuration option to enable/disable this feature:

export class LibraryConfig {
  // ... existing config
  
  @IsBoolean()
  @Transform(toBoolean)
  autoCreateAlbums!: boolean;
  
  @IsBoolean()
  @Transform(toBoolean)
  useNestedFolderNames!: boolean; // For "August 2025/Vacation" -> "August 2025 - Vacation"
}

Some other thoughts about a further build..

• This doesnt deal with nested folders.
• Exclusion patterns: Respect the library's exclusion patterns when creating albums would need to be added
• For large libraries, batch the album creation/asset addition operations to increase performance
• Ensure the user has permission to create albums - check permissions

[francoposa]

Would it help to down-scope this for the first version?
Ideally in a way that allows punting on the harder decisions until later without backing the setup into a corner.

How about:

• Every external library is an album (or can be an album if configured in the external library setup)
• The album contains only the photos directly in the folder path - subfolders and their contents are ignored

This means if you really want nested albums (this is not a particularly helpful way to organize photos IMHO), then you can manually mount each path separately as an external library without worrying about duplicates/conflicts, e.g.

• /external-location/photos/2025
• /external-location/photos/2025/Vacation
• /external-location/photos/2025/Graduation
  can each be mounted and become an album.

This should not conflict with any future feature of auto-discovery or support for nesting, if it would ever comes to pass.

[sjauquet]

"This is not a particularly helpful way to organize photos IMHO"
Eh ! Sorry ??? This is an universal way to organise photo and not be tied to a database (who is usually not migratable !!)
So if you want at least sorting your photos by year, month, event, kids, .... this is the most persistent way to date to keep it slightly organised, and keep it even if you change the software to display them.

[francoposa]

I am specifically referring to having both photos and subfolders within a folder.
If we map this conceptually to "albums" as most photo apps handle them, I do not know of any common ones that have an "album within an album" concept.

I personally do not see the value in having "2025" album that contains both pictures and further sub-albums, when those could be much more easily mapped to their own albums, e.g. "2025 Vacation" not as a child album of "2025".

Regardless, there is no value in throwing a little fit about your personal desires for photo organization.
My suggestion is to down-scope the idea to get a minimal basic version started which provides functionality without having to make any controversial, hard-to-reverse decision know about more complex automatic traversal and mappings.
Everyone demanding their preferred complex auto-mapping is only making this less likely to get any traction.

The goal would be:

1. To get something working to fit the bill even if it's a bit manual to configure in UI - that beats an external script
2. For the minimal version to not back the design into a corner for future decisions regarding the various competing auto-organization suggestions which are being debated and wildly expanding the scope here.

If we can get something where each of these folders can easily be mounted as separate albums:

• /external-location/photos/2025
• /external-location/photos/2025/Vacation
• /external-location/photos/2025/Graduation

then that goes a long way towards the desired outcome and should be massively simpler to implement.

[sjauquet]

I am specifically referring to having both photos and subfolders within a folder.

ok, that makes sense

each of these folders can easily be mounted as separate albums

ok, but having to mount every album is not possible (for me at least) when there is 100's if not 100's albums ... (I have around 600 albums)

[holocronweaver]

Can we create an issue to track implementation of this feature? I want to subscribe and be notified when the feature is released, which is not possible currently with discussions, but is with issues.

[Otiel]

Subscribe to the releases, and you'll know when (if) it drops

[holocronweaver]

...by reading the entire release notes of every release until my feature comes up. Not the same as subscribing to a particular issue by any means.

[bo0tzz]

We track features in discussions, so we won't create an issue for this. What's stopping you from subscribing to this thread?

[holocronweaver]

With issues you can subscribe to only when the issue is closed / reopened to avoid noise from comments. That way you are notified only when the issue is resolved. This is not possible with discussions to my knowledge.

[maltokyo]

But, this is not an issue... Nobody understands you.

[RobinEd]

So far I can see 4 external solutions for this, not sure which one to implement (NB also trying to move from Synology Photos, using Digikam and really want to keep the folder structure I have built up over decades):

https://github.com/alvistar/immich-albums
https://github.com/Salvoxia/immich-folder-album-creator
https://github.com/ronbruins/immich-autoalbum
https://github.com/Demian98/immich-sftp-server

which are all a little different. No idea which is 'best' for my usecase (converting from Synology Photos and wanting to keep my folder based structure whilst sharing with my family) though. I think the length of this discussion (and the one on #10089) shows that there is a demand for this as a feature...

[mooglestiltzkin]

you can now browse existing folders with immich. no need to do any extra methods like before.

so, if you got a folder layout e.g. on truenas server in your dataset, you can simply to go immich, add those mnt points to those folders. then in immich u can access those folders.

u however have to manually mount those folder locations for each of those folders.

[jdumas]

When was this feature introduced? I know we can browse folders on the web app, but I don't find such option on the phone. Also, browsing starts from the root /, doesn't show any thumbnail of the content... and it doesn't create albums that can be shared. Overall it's pretty far from being user-friendly, and not a replacement for having the ability to organize albums into "collections" with nested levels of organization.

[nalpo]

I also would like this feature. Since the folder structure is already visible, why not start there with a bare functionality? For example adding an option in folder view like "Automatically add pictures in this folder to an album". For starters, that album could be named manually and include all files in the folder. I think from there it would be easy to give some more options, like including/excluding subfolders or having a naming scheme.

[ejkarne]

If anyone is running the v3 RC can you check if this is something that can be accomplished using the new Workflows feature?