Repository navigation
[Feature] Grouped Album View based on Album names (Web & App) #32283
Closed
zerknorscht
started this conversation in
Feature Request
Replies: 1 comment 1 reply
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have searched the existing feature requests, both open and closed, to make sure this is not a duplicate request.
The feature
Summary
Add an optional, per-user hierarchical view of existing Immich albums, using a configurable separator in album names.
This is not a request for nested albums or new album entities (but might verry well satisfy some of those requesters pragmaticaly).
Immich's existing flat album structure, album IDs, photo assignments, ownership, and sharing permissions would remain unchanged.
The feature would simply provide an alternative way to browse albums that share common name prefixes.
Example
Consider these existing Immich albums:
Today, these appear as seven separate albums in the album overview.
With hierarchical grouping enabled and "/" configured as the separator, the initial view could instead show:
Opening Family would show:
Opening Holidays would show:
The important distinction is that "Family / Holidays" is an actual Immich album containing its own photos, while its name is also a prefix shared by other albums.
The photos from "Family / Holidays / Italy 2025" and "Family / Holidays / Baltic Sea 2026" would not be merged into the parent album. They remain in their original albums.
Proposed mobile UI
The feature could integrate naturally into Immich's existing mobile album and photo views:
This accommodates three cases:
Virtual groups could be visually distinguished from actual albums using a small folder or group icon.
The exact visual design can follow Immich's existing UI conventions.
Web UI
The web interface should offer the same logical hierarchy, potentially using expandable groups in the album overview or navigation into grouped album views.
As on mobile, actual albums and virtual groups should remain distinguishable, and a path matching an existing album should preserve access to that album's own photos.
Settings
Only two per-user display settings are proposed:
These are personal presentation preferences, not album properties or server-wide settings.
Different users viewing the same shared albums could independently choose whether to enable grouping and which separator to use.
With grouping disabled, the existing flat album view remains unchanged.
Expected behavior and scope
Motivation
As an Immich library grows, a flat overview containing dozens or hundreds of albums becomes difficult to navigate, particularly on mobile.
Many users already organize albums through naming conventions. An optional hierarchical view would make those existing conventions useful for navigation without introducing the complexity of true nested albums, permission inheritance, or album migration.
This could offer much of the usability of album folders while preserving Immich's existing data model.
It might solve with low effort what might be the pain behind the requests fir grouped or nested Albums, committed in the past by a simple non distractive UI behavior extension...
Platform
All reactions