Lightroom: presets need favourites or recently used

  • 7
  • Idea
  • Updated 4 years ago
With the proliferation of presets, usability of the panel is considerably reduced.

Repeating steps over multiple images (not using auto-sync) becomes very awkward with a lot of scrolling up and down through the list.

Given limited panel space maybe this needs to be on the right-click menu.
Photo of Barrie Spence

Barrie Spence

  • 13 Posts
  • 0 Reply Likes
  • not working as quickly as I could

Posted 7 years ago

  • 7
Photo of Sean Phillips

Sean Phillips

  • 158 Posts
  • 44 Reply Likes
I have a folder called "AAA" in my Presets folder that has my favorites. This ensure that these presets are always at the very top of the preset list so they are easy to find.
Photo of JimmyD


  • 1 Post
  • 0 Reply Likes
I have purchased and downloaded many (several hundred) 'Develop' presets. These presets are contained in the folder created by the developer. It's important to keep these presets together so one can remember which presets came from which developer. In every folder of presets, there are several that one ends up using repeatedly or there are presets in different folders that are similar. Scrolling back and forth between hundreds of presets is time consuming. I could move all my "favorite" presets to one folder, but then I would lose the ability to know where that preset originally came from.
My suggestion would be to have the ability to create "virtual" preset collections, where folders could be created to house favorite or similar presets from different developers but have them remain in their original folders to know and remember where they came from.

This reply was created from a merged topic originally titled
Lightroom: Preset collections.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 370 Reply Likes

Create a favorites folder and in it put links to actual preset.

Photo of John Hoskison

John Hoskison

  • 6 Posts
  • 7 Reply Likes
One click to flag favourites into a favourites folder - other products like OnOne do this as the norm these days. Better still emulate the rest of the DB and allow search filtering using keywords / labels etc. That way we could work across collections searching for specific / generic collections