We need this!
We need this! I have a collection of video diaries that I would like to be in a collection that is sub-nested into the TV show.
Hopefully this is the year! ![]()
Only after another dozen features the core users donât want are released.
Iâm moving my suggestion here to merge with this existing post. But after seeing that this request existed in 2018 and with so many votes but with no movement on this from Plex, I have very little faith that this will be implemented. /sigh What is this suggestion forum even for?
------- Original --------
These images should be self-explanatory.
Perhaps an option to force a new row when you click on the collection menu? This wouldnât work in âLibraryâ view, but this should be possible in âCollectionsâ view since collections are only sorted alphabetically there.
Or maybe add a âcollection groupâ property in the tags? More complex to implement, but would be the best and more robust way.
This is also my request!
I would love this request.
Recently generated Collections for the different streaming services using PMM.
A Nested Collection of the different streaming service, which could then be pinned onto the Homepage or library page.
This is truly the ONLY feature Iâm missing from back when I used Spotify. Iâd love to be able to neatly organize my playlists in folders (i.e. Plexamp > Playlists > Folder called âMovie Soundtracksâ > Here, all the playlists from that folder). That would have a HUGE impact in usability, especially for playlist-heavy users.
Hello, I am extremely new to the community (though have been using Plex for many years).
I also would LOVE to have the functionality to nest collections within collections . I can imagine numerous use-cases for this that I would take advantage of, but two examples would be
- a Star Wars (or Star Trek) collection; within that collection I would like to have a (âsubâ) collection of original episodes, and a separate for the First Order (or alternate reality) movies.
- Another might be to have a collection of Disney movies for my children, and within that collection, separate (sub)collections for Disney Nature, or a (sub)collection for Toy Story movies, etc.
I know that I could potentially use Plex Categories, to achieve something similar to what I have described (well, not really!), though honestly I find the functionality of collections (eg; to add posters and other artwork and content) so great to work with that having nested collections would transform my movies organization in Plex into something incredible!.
Lastly, I believe âPlex Meta Managerâ can achieve this, though frankly I do not know if my coding skills would be sharp enough to achieve it without ruining my Plex DB.
Yes absolutely this⊠example uses;
- Nest all actors/directors/studios collections etc into folders so they donât take up a massive amount of space on the collections page.
2 also then to be able to include these as a neat strip on the home page, library. - Best tv network sub collection folders into one TV networks collection folder so we can have a neat strip of different networks on a home page/library. Rather than a strip for each network.
This is the one feature in Plex that I have always needed. Dividing collections into groups, such as Director, Studio, Franchises, Oscar Winners, would make for a much better user experience. There are some great example pictures above that depict exactly how I imagine it should be implemented.
Coming up on six years since this was suggested. Hopefully we get something like this really soon.
As a developer, this is incredibly simple to implement. The fact that they havenât after 6 years means they donât want to. It would take a competent developer an hour to get this done. Even a mediocre one would take no more than a day.
This is a long overdue feature. How hard can it be to create a âsubfolderâ within Plex? This is important because I need to be able to do things like separating the good DC movies from the bad ones etcâŠ(which honestly that eliminates more than half but stillâŠ)
This is wild!
As a developer, have you ever experienced a customer who thought something should be trivial to do, but you knew it was more complicated and would take more time?
As a product owner, have you ever experienced a customer who wanted a change, but it didnât align with the features you wanted in an app at all, or the customer ignored the complexity and cost to support the changes in perpetuity?
What nesting is allowed? Is circular nesting allowed? When a collection is deleted, what happens to nested collections? Are they deleted or re-parented? Can a collection contain both other collections and single items? What changes to database schema are required? How is the database schema migrated up/down between versions for upgrades and downgrades? What testing is required? What changes to the UI/UX are required for editing? What changes to the UI/UX are required to show item membership in multiple nested collections? What additions to âshowâ vs. âhideâ collections are required at different depths? How do you edit the details of a nested collection, or edit nested collection membership? Is a nested collection tree view required? How much localization is needed? What changes to documentation are required? What about changes to the search index, or search results? What changes to the API? What performance impact might be associated with nested collections? How does this interact with automatically created collections? Is there a metadata source for nested collections? What changes to client apps are required? How should legacy clients be treated when connecting to an updated server? How much additional support will be required in the forums forever?
This is why I never say something would easy to develop or make. I might say something âseemsâ easy or similar. But if Iâm not knowledgeable in an area, I wonât presume to know how easy something is.
Iâve been in IT for almost 2 decades and did many semesters of coding(which I did not enjoy) and I all of the questions you asked are 100% valid. And who knows, maybe the reason nested collections arenât implemented is because thereâs just no way to code it without opening up bigger bugs or ways to break things. Itâd just be cool if the devs could comment on this request.
It really shouldnât and yet here we are 4 years later. Youâd think some of the obviously asked for features would be added and tossed into the Plex Pass. Iâd pay for that. Iâd also pay to get rid of the âRecommendedâ tab in my libraries or the ability to choose pictures for folders in the âBrowse by folderâ option which would kind of give people defacto âpsuedo-collections within collectionsâ ability.
I would love to have the ability to create sub-collections inside existing collections in Plex. For example, in a main collection like âHorror Movies,â I could have smaller sub-collections such as âFreddy Kruegerâ or âThe Conjuring.â This would greatly help with organizing large collections and making it easier to navigate through sagas or series within a specific genre.
Thanks for considering this feature!
There is a way to get your specific use case already: âCategoriesâ
E.g. there already is a âHorrorâ Category:
And most media is somewhat reasonably auto-categorized already.
For when it is not, you can manually change this in the media details:
Oddly, it is called âGenresâ, there.
And movies can be part of multiple categories.
Itâs unclear if Plex will ever provide this, it could be because of how Plex Server is written and it would require a lot of recoding. I currently run Plex and Emby server side by side, and Emby allows you to create collections and inside those collections you can have sub collection folders. Itâs one of the main features I love with Emby vs Plex. Iâve found that Plex does other features that Emby doesnât do and Emby has itâs own features and layout. Guess you have to pick your pleasure and preference.






