Feature Requests

Lightroom for Linux - is it possible? Most my friends and I need it, because of not using Windows and current Linux tools can't get so great instruments for raw preprocessing and organizing...

I created folders and albums in LR and now have started using LRC, but Lrc doesn't automatically create the same structure as Collection Sets/Collections.  It'll be very annoying if I have to do it manually as as far as I can see Collection Sets = Folders and Collections = Albums.  Shouldn't be rocket science....  At the moment, every single folder from Lightroom (cloud) is just listed in a single list under "From Lightroom"... great, thanks!   Also would be good if this was automatically maintained when I sync the two, if it doesn't already.

In the custom presets, it is annoying to have to click on the arrow to scroll down. Also it would be more convenient to right click on a preset and be able to have a delete option.

The problem:Lightroom Classic’s current Luminance and Color Range masks often produce harsh, unnatural transitions. Even when using the available range feathering, fine details and local contrast are still flattened or even destroyed. This happens because the existing feathering only softens the tonal selection (the range), not the spatial edges of the mask.The solution:Introduce a spatial edge feathering slider, similar to Photoshop’s mask feather control (see picture). This would soften the geometric edges of the mask independently of the luminance or color thresholds, so that local contrast and fine details are preserved.  

I’d like the option to display flags (Pick/Reject) and star ratings while using Full Screen / Lights Out mode in Lightroom Classic.   Right now, pressing F disables the "I" key info overlay, which prevents seeing critical culling information while viewing images distraction-free.   Suggested enhancement: Allow the "I" key (or a preference toggle) to show flags and star ratings in Full Screen mode, similar to how it works in Loupe view.   This would significantly improve culling and review workflows by combining a clean viewing experience with essential rating visibility.

A simple proposition.We could given the ability to crete custom history steps. How would it work:Via a dialog we could enter a custom name for a step OR use the current date/time.UI dialog presentationCustom Name for history stepCurrent Date and Time for history stepWe could custom steps via a + icon in Develop panel akin to SnapshotsCustom history step name creation also doable in Library via an option.Creation of “Custom History Steps” should “AutoSync”Advantages:No need to change the edits in the photo to generate a step.Users can use this option to create critical events in history in ways LrC can’t or create steps if history is missing.Unlike snapshots nothing ends in XMP when saving. 

Hello, In the current version of Lightroom Classic, the GPS track used to geolocate the photos is limited to 50.000 points. It is not enough in 21e century. The modern watches are able to take the GPS position every seconds. In that case 50.000 points correspond to 14 hours only ! For the modern outdoor endurance activities like ultra-trail running, mountaineering and even long hikes it is not sufficient. Please, extend the Lightroom Classic capacity in order to accept at least 40 hours of such a activity (UTMB like ultra-trail) = 150.000 GPS points. BR, Maciek

I think all portrait photographers would like to have any AI portrait retouch system on Lightroom classic and photoshop, like FACEAPP. We really need something like that. And I know that Adobe can do better than faceapp

Often corporate head shot sessions are done in tight spaces, with a small backdrop, so the image will show parts of the wall or other distracting things, that we need to crop out. Example belowAlso, the hight difference in i.e a corporate shoot, means you often don’t use a tripod, and all the images looks a bit different in terms of positioning and framing, focal length etc. When editing this means I’ll have to do a few tweaks to each and single image (and it might be houndres in a single shoot)Reframe and reposition Use some sort of generative fill to fill in edges or remove distractions (sometimes settings can be copied and pasted between shots, but often they are not familier enough)These features will have to be reaplied to every image.. It’s a very very time consuming task.Also - often we have a framing that’s too tight - and I want to add more head space. This would require me to go into photoshop, extend the image and do some generative fill.  Image if these changes could all be

Users (thinking of my students, who are new to photography) should be able to import files without going through 32310 steps. If, like in Adobe Premiere, they had the ability to simply drag things from the desktop into LrC, that would streamline things immensely.For exporting JPGs, there should be an option to right-click (or hit file) > export > export as JPG to [location] without having to navigate the window with all the information specifications (and really small text). Keep that option, sure, but there should be a more simplified option. 

HiI do a lot of video editing and really like using the RGB Parade and Vectorscope. Histogram for photos aren't as detailed. Is there any plugins or features that have similar functions like RGB Parade and Vectorscope for use inside Lightroom or maybe as an external editor? Best regards Simon

Add desired file/folder name to search dialog so it can be easier to compare to long list when browsing existing folders/photos.Something like this: To help me remember when searching to link something like this nightmare again 1 folder at a time.  :( 

On one of my cameras, because it only has one memory card slot, I shoot both Raw and jpeg onto the same memory card. When importing the files into Lightroom I want to only import the Raw files, and not import the jpegs. Currently, in order to do this, I must manually de-select each jpeg from the import. This is extremely tedious and I would like a way to de-select all the jpegs at once to prevent them from being imported. Thank you!

In Lightroom Classic sollte es im Entwicklungsmodul bei einer Entwicklung eines HDR-Bildes für die Vorschau der SDR-Anzeige auch eine Automatik geben wie in CameraRaw  

Hi,I’d like to suggest an improvement for the Reference View feature in Lightroom Classic.Currently, when using this view, hovering over the image shows the RGB values for both the reference and active images below the histogram. However, this is only useful when the tones you want to compare happen to be in the exact same position in both images — which is rarely the case. My proposal is to allow users to place pairs of color sample points (eyedroppers) — one on the reference image and one on the active image.Ideally, we could place multiple pairs (e.g. up to 3–5), and click on the pair we want to activate. This would display the RGB values of those two specific points side by side under the histogram (e.g. R: 120 / 135 — G: 200 / 185 — B: 180 / 170).This would allow for much more accurate and targeted color comparisons between images, which is especially useful when trying to match color, light or white balance across a series or between unrelated shots. Alternatively —and

It would be really useful if Lightroom could have more color labels to categorize quickly visually . 5 is a really low number. For example, Davinci Resolve resolve has many more. And this makes it very easy to categorize and quickly filter by color. It would be even better if you can let us make unlimited labels with the colors we want. For example, 5 different shades of blue , red etc.     

I will often create a VC at a point where I am happy with what I have, but want to diverge or try other things.  Later, I may want to understand at what point in the development I created the VC(s).I requested that, when a VC is created, an entry be made in the history list, indicating the creation…and, if possible, the VC’s copy name.

The only choices today for managing previews are to set a fixed size limit (very useful if that drive doesn’t have unlimited free space) OR remove 1:1 previews after ‘n’ days. And if you set a fixed size, you get nagged constantly about increasing the cache size. First, why on earth can’t we have both choices active?Second, more options for how to manage the retention and discard of previews from the cache would not be especially complicated to implement but would speed editing. The principles of buffer management are common to many kinds of IT systems so there are many approaches - including algorithmic guesses at what might be viewed next - that would improve the chances that a suitably sized preview is found in the cache when needed.

Lightroom Classic’s current watermarking workflow is primarily export-based. I would like the ability to configure and preview a watermark on the actual photograph while editing in the Develop module, before export.The desired workflow:Add a PNG watermark with transparency to a photo. Display the watermark directly over the photo while editing. Adjust position, size and opacity visually for that specific photo. Store those watermark settings as part of the photo’s Lightroom metadata/develop settings. Move to the next photo and adjust the watermark independently if necessary. When finished, batch-export the photographs, with Lightroom using the individual watermark position/size/opacity stored for each photo.

When dropping multiple collections to collection set, If already same name collection existing in target collection set.Now: Deny all of collections to move.It’s unable to know which one is the cause of being rejected until open target collection set.Want to request: Skip to drop collection only source collections has same name in target collection set, stay on current place. And move rest of all collections.

I'm a relatively newbie to Lightroom and I think it is fantastic. It does occur to me that pros who have been using Lightroom for a while understand all the issues about selections, settings, copying, pasting, synchronising etc etc. Like many things in life the people who do things almost as second nature forget what it was like to be a beginner. The one thing that has surprised me about lightroom is that I cannot find a way of indicating "I am happy with this - I just want to lock it to ensure I don't damage, amend or delete it" through my own incompetence.

When searching for a keyword in the keyword list (using the keyword filter) only matches with keywords but not those matching with synonyms are displayed. In Lr 2 also matches of those keywords were displayed which had a synonym match. I would like this to be an option in Lr 3, too, maybe user-definable. Usecases: I've got a large list of keywords with most of them having at least one synonym (my keywords are in German and I use synonyms for english translations and other synonyms). (1) When I look for the existence of a keyword I would like to make sure that I've not included it as a synonym already. (2) While searching for a specific topic sometimes I can only remember the synonym (yes, growing older...). In Lr2 I could find it easily by keyword filter.

Let be able to use all masking tools including combination (intersect, invert, add, substract) to define areas to be remove by AI in the remove panel

Modern mobile devices run on ARM processors, and that is the future. Look at Apple. Please develop native ARM versions of Lightroom Classic and all other Adobe products. Even with the current version of LrC, it is impossible to take advantage of ARM-based AI for noise reduction! Noise reduction takes hours, despite using a fast Snapdragon processor. That is simply unacceptable.After all, you rewrote the software for Apple in record time—why not for Windows? Otherwise, I will be forced to switch to Luminar Neo, and I could replace Photoshop with Affinity; both run natively on ARM. Adobe is still relying on the outdated x86 architecture. I urge you to change this. ARM is many times faster than x86.Many thanks in advance!

When using the Lightroom Classic SDK it would be great to be able to move photos in the catalog between folders programmatically.   A simple example would be for writing a plugin that moves selected photos between parent catalog folders, while maintainig folder structure (to move files between disks).   While it is possible to create folders and move disk files using `LrFileUtils`, any catalog photo moved that way ends up as 'missing' in the catalog because their disk location is changed by `LrFileUtils` but the photo `path` in the catalog is not updated.   It is possible to read a photo's path using `photo:getRawMetadata("path")`, provided by `LrPhoto`, but it is not possible to change a photo's path using `photo:setRawMetadata("path")` because `path` is not a valid key for writing back to the catalog photo.   So in summary, it is currently not possible to move a photo between catalog folders in a Lightroom Classic catalog using the SDK.  `LrFil