Skip to main content
.random..
Inspiring
June 14, 2026
Open for Voting

Erx: Allow Smart Collections to use other Smart Collections as a source

  • June 14, 2026
  • 2 replies
  • 29 views

Lightroom currently allows Smart Collections to filter the contents of regular Collections, but not the results of another Smart Collection.

Example:

Smart Collection A:

  • Camera Serial Number = X
  • Filename contains Y

Smart Collection B:

  • Source = Smart Collection A
  • Folder contains “2603

This currently does not work, even though the exact same setup works when Smart Collection A is replaced by a regular Collection.

Supporting Smart Collection → Smart Collection filtering would eliminate duplicated rules, simplify complex workflows, and make large archives significantly easier to manage.

The current workaround is to create a regular Collection and continuously copy the contents of a Smart Collection into it. This feels like an inadequate solution to a problem Lightroom should be able to solve natively. It also introduces unnecessary maintenance and creates additional opportunities for user error, especially in larger workflows with multiple collections.

    This topic has been closed for replies.

    2 replies

    Rikk Flohr_Photography
    Community Manager
    June 15, 2026
    Idea merged into:

    All the votes from this idea have been transferred.
    Rikk Flohr: Adobe Photography Org
    johnrellis
    Legend
    June 15, 2026
    .random..
    .random..Author
    Inspiring
    June 15, 2026

    Thanks for the suggestion.

    I can see the overlap, but I believe my request highlights a more specific workflow limitation.

     

    The older feature request focuses on recursive Smart Collections in general. During testing, I discovered that Lightroom can already use regular Collections as a source for Smart Collections, but it cannot use another Smart Collection as a source.

     

    This becomes a significant limitation in real-world workflows because it forces users to manually duplicate the contents of a Smart Collection into a regular Collection just to apply additional filtering. That workaround is fragile, creates maintenance overhead, and introduces opportunities for user error.

     

    I would be happy to support the older request, but I think this specific limitation deserves its own discussion and visibility because it affects large production workflows in a very practical way.