Skip to main content

Filter by idea status

10000+ Ideas

gadgetgeek2000Known Participant

P: Simplify moving foldersOpen for Voting

I have a large catalog and my workflow is this:Import photos onto my local computer. Store pictures in the Pictures folder in a subfolder with year/year-month-day folder structure. Edit my photos Move my photos to my NAS storage by dragging the folder in Lightroom to the storge drive. I have photos on the NAS going back many years. Dragging in Lightroom is a complicated process:Expand the NAS drive letter Expand the year target folder Roll up any other year folders because the list is extremely long Grab the folder and drag it down. The target folder is off the screen. Drag close to the bottom and get the list to start scrolling. Scroll scroll scroll until I get to the target year, and then release.  In the middle of scrolling if I pause for even a moment, it will expand a year folder that is NOT the intended location. So I then have to scroll through all the photos in that year to move to the bottom of the list and get to the next year.All this maneuvering is done while holding the mouse button down and hopefully it doesn’t release. This is REALLY difficult to do on a trackpad on my laptop and a challenging operation for anyone who might require some sort of physical accommodations.Moving folders in the library module with a large catalogMy suggestion:Make a new menu item when right clicking on a folder in the Library module. The new menu item should read Move Folder .... The user should be able to select one or more folders for this operation. When the user selects Move Folder … a dialog box should show to say “Select target location”. It should be a parent folder selector that would use the standard “browse” or “save as” system dialog box to pick a folder.  If you don’t use the system dialog box, make your own dialog box here that only includes folders that already exist in the catalog. If the solution is developed to use the standard system dialog box and the user adds a folder location that is outside the Lightroom catalog known folders then consider warning the user or adding the new location to the catalog automatically. Sample “select folder” dialog box​​​​ in Windows When the user clicks Select Folder then each of the folders are moved in the same way as drag and drop in the application. Confirm the move as normal, move both single and multiple folders as normal.This solution should be much simpler to move folders in the catalog, especially with large catalogs, and especially for those that need accessibility assistance to not require the complicated click/drag/find your target and never let go operation that we currently use.Thank you for your consideration!

GlynAStanleyParticipant

P: Add a master catalog view for browsing multiple catalogsOpen for Voting

I’d like to request a master catalog feature in Lightroom Classic that lets users browse thumbnails from multiple catalogs in one unified view without fully merging them.Why this mattersMany photographers organize work into separate catalogs for practical reasons such as client jobs, years, shoots, or business divisions. That structure is useful for performance and organization, but it creates a major drawback: there is no fast, visual way to search or compare images across catalogs. Right now, if I want to find a photo, locate similar shots, or review older work, I have to open catalogs one at a time, which is slow and inefficient.What I’m asking forA master catalog or global browser that can: Display thumbnails from multiple catalogs in one place. Search across catalogs by filename, keyword, rating, date, and other metadata. Let users filter by catalog, project, client, or folder source. Open the source catalog when a photo is selected for editing. Optionally sync or reference previews only, so the feature remains lightweight and does not require fully merging catalogs. Workflow benefitThis would make Lightroom much more practical for photographers who manage large archives, separate client work from personal work, or maintain catalogs by year or project. It would preserve the organizational benefits of multiple catalogs while solving the biggest downside: fragmented browsing and search.Suggested implementationA good approach might be: A new “Library” or “Catalog Hub” view. Support for adding multiple catalogs as indexed sources. Cached previews and metadata-only indexing for speed. An option to pin favorite catalogs for quick access. Why Adobe should consider itThis would reduce friction for advanced users, improve archive management, and make Lightroom a stronger long-term cataloging tool for professionals with large photo libraries. It would also help users avoid the need to merge catalogs just to find and review images efficiently.

P: Allow Queueing/Batching for Generative Remove to Prevent Workflow InterruptionOpen for Voting

Request: Allow Queueing/Batching for Generative Remove to Prevent Workflow InterruptionThe Problem: Currently, using the Generative Remove tool requires a strict "one-by-one" workflow. After painting a mask, navigating away to another image before clicking "Generate" discards the mask. This means I am forced to click Generate and sit waiting for the AI to process before I can move on to the next image.Because the generation process takes time, my entire editing momentum is derailed. The majority of my editing time is now spent waiting on progress bars rather than actually editing.The Solution / Proposed Feature: I would like to request the ability to paint Generative Remove masks on an image and navigate away without losing them, allowing Lightroom to cache or "hold" the pending mask.This change would unlock two massive workflow improvements: Asynchronous Editing: I could paint a mask, move immediately to the next photo to keep editing, and let the background generation happen without blocking my workspace. Batch Generation: Similar to how we can currently batch-remove distractions, we could mark removal areas across an entire photoshoot/set of images, and then initiate a single batch-generation command for all pending masks (e.g., during a break or at the end of a session). How this impacts my workflow: This single adjustment would be a massive game-changer for efficiency and user experience. Instead of being held hostage by individual AI generation render times, I could stay fully immersed in the creative flow of culling and editing. It shifts the AI processing from an active bottleneck into a passive background task, saving hours of cumulative waiting time on large catalogs.