Bug Reports

If the working profile in both Photoshop and ACR are the same, the skin tones match the proper hue when a photoshop image is brought into ACR.  However, the skin tone line on the new vector scope is not moving to adjust for the fact that the Hue value associated with skin tone varies between color spaces.  The skin tone line seems to be set at a hue of about 18 regardless of what the working export color space is, so it gives incorrect skin tones unless you are exporting to Rec709. space.Open an image in photoshop with skin and convert it to Rec709 color space.In the settings panel ensure that ACR working space is also Rec 709. Open the base layer in ACR and select the skin of the subject.  The skin tones will properly align with the skin tone line on the new vector scope, at a hue of about 18-19 degrees. Now, cancel in ACR and use the Edit menu to convert the image to ProPhoto color space.  In the settings panel, change the settings to ensure that ACR is also exporting to the ProPhoto

I'm not seeing any noise reduction using Denoise AI on Pentax K3iii DNG files in Lightroom Classic v12.3. Any future solution to this issue? Thanks Tom

Die KI-basierte Entrauschungsfunktion in Lightroom Classic hat mit HDR-Bildern, die in Lightroom generiert wurden (dng-Format) erhebliche Probleme in Zusammenhang mit Fenstern. Es entstehen im Bereich von Fenstern regelmäßig sehr unschöne Karo-Muster. Anhängend jeweils JPG-Output mit aktivierter und deaktivierter Entrauschungsfunktion.Die DNG-Dateien sind abrufbar unter: LR-Denoise-Bug The AI-based denoising feature in Lightroom Classic has significant issues with HDR images generated in Lightroom (DNG format) related to windows. Regularly, unattractive checkerboard patterns occur in the window areas. Attached are JPG outputs with the denoising feature both enabled and disabled.The DNG files can be accessed here: LR-Denoise-Bug 

1. Description of the Issue After opening a photo and attempting to use the "Select People" mask, the error message "Unable to select people in the photo" appears, and the feature fails to function.2. Camera Raw Version(s) 18.3, 17.5 3. OS Version macOS Tahoe 26.3.1 4. Steps Taken & Troubleshooting Performed (Reproducible) The following steps were taken, but the issue persists: Changed Performance settings in Camera Raw Preferences. Reset Camera Raw Preferences. Reset Host application settings. Reset UXP and CEP folders. Deleted System Fonts. Granted Full Disk Access to Adobe applications in macOS settings. Performed a clean reinstallation of all Adobe apps and downgraded Photoshop to 26.11.4. Downgraded Camera Raw to 17.5. Switched Image Processing settings between "Cloud" and "More Stable". Tested on a New User Account (macOS). Note: The user confirmed this issue began immediately after updating to the latest macOS version. 5. Expected Result The AI should det

After upgrading to 15.4, several, but not all, of my hdr pano photos report the above error, along with “The file appears to be unsupported or damaged”. Restored these “damaged” photos from versioned backup on Backblaze from versions several months old and still received the error. Reverted to 15.3.1 and these files no-longer show the error. So, 15.4-->Broken; 15.3.1-->Working

Hasselblad’s FFF. formats are not supported anymoreProblem occurs in both Mac OS 15.5 (24F74)  & Windows 11 pro (Betriebssystembuild: 26100.7840)When opening fff. files in the newest Bridge (16.0.3), Camera RAW Plugin (18.3.) opens and creates an error, claiming the file format is not supported. Same Problem occurs with  the newest Lightroom Classic (15.3). The Import is not possible cause the file format is not supported.Thank you for your help!

Just notice something strange following this week's updates: The histogram in Adobe Camera Raw 18.3.1.2580 is not visible, although one can drag a mouse pointer in the blank area and change the luminance. So, it seems to be just not showing. Conversely, when using Photoshop and clicking on the Camera Raw filter, that version of ACR has a visible histogram, with the same functionality as expected.Updating NVidia drivers to the latest release did not correct the bug.At least one other user experienced the same bug. His correction was to rollback to 18.3.0

I've lost the ability to Control-click (or right-click) to rename or delete a local preset in Adobe Camera Raw, 18.3.1.2580.I’ve tried via Bridge, and via the Filter in Photoshop.

The Adobe DNG Converter that we use in LRTimelapse for the downscaling of Raw files and DNGs is broken in Version 18.3 and 18.3.1 (18.2 works fine).The issue seem to affect DNG files only.Here is how to reproduce it:"/Applications/Adobe DNG Converter.app/Contents/MacOS/Adobe DNG Converter" -dng1.4 -cr7.1 -side 1024 -p1 -fl -d /Users/xxxx/Desktop -o conv.dng /Users/xxxx/Desktop/test.DNGOn 18.3 and 18.3.1 this command doesn't return, while on 18.2 it works fine.Adapt the paths, you can download the test.DNG file from here:https://www.dropbox.com/scl/fi/ce5muil4r0wm7ms6zsnqs/test.DNG?rlkey=0r61gyqc2u7w3u8i4727qsdim&dl=1I hope you can fix this asap! Thank you so much!

macOS 26.5Photoshop 27.7Camera Raw 18.3.1 none of the menu items workSteps to reproduce:Open any image in ACR Create a mask Do something in the Color Grading panel Right click on a color wheel to call out the context menu Choose Reset or copy / paste It does not wokThis happens only in masks.You can still press ⌥ and click the Color Grading panel header to reset. p.s. This new forum is a disaster. 

I have never had an issue with ACR before.18.3 freezing saying not responding saving files took twenty minutes instead of seconds everything was super laging, when I disabled the GPU acceleration it improved I see on the other pages I am not alone I'm using the most up to date windows, Nvidia drivers ETC: I have a 7950x, 5090, 64GB and NVME drives. Please fix as soon as possible or at least give a link to the previous version which I had no issues with.Solution:Update following the instructions in this link:  

When creating a new brush mask in ACR, if the brush is resized in between changing a slider and making the first brush stroke, the slider resets to zero.  For example- Press K to create a new brush mask- Set the highlights slider to -100- Right click on the mouse to resize brush- The highlights slider resets to zeroIf you don’t change the brush size, the mask works as intended.  This seems to have started happening since version 18.3.1 

People masking fails to detect the person shown in a raw photo but does detect the person in a TIFF exported from the raw.  That's incorrect -- the images are visually identical. To reproduce on LR 15.3 / Mac OS 26.4.1: 1. Download and open this catalog, containing a .nef and a .tif exported from the .nefhttps://www.dropbox.com/scl/fi/awz18x0px6nxb5dvauu9g/people-mask-raw-bug.2026-05-29.zip?rlkey=wy2h85fmasbr39y9q10z27mnv&dl=0 2. Select the .tif and create a People mask. Observe that it succeeds. 3. Select the .neft and try to create a People mask, and observe that it says No People Found.

There is a persistent bug when synchronizing "Spot Removal" (Heal/Clone) adjustments across images that involve HDR merges in vertical orientation. The adjustment coordinates are not being mapped correctly between standard RAW/DNG files and the DNG files generated by Lightroom's HDR Merge feature.Steps to reproduce: Take a series of vertical (portrait orientation) RAW images. Perform an HDR Merge to create a new DNG file. Apply a spot removal adjustment (e.g., to clean sensor dust) on one of the nont merged files. Sync that adjustment to the newly created HDR DNG file. Expected result: The spot removal should be applied to the exact same visual coordinates in both the source and the target HDR image.Actual result: In vertical images, the spot removal adjustment is shifted to an incorrect position on the HDR file. This does not happen with horizontal (landscape) images.Additional notes: The issue occurs regardless of the camera brand/model. The offset happens both ways: from RAW

Steps to reproduce: 1. load image in ACR 2. choose the crop tool (C)  3. enlarge the canvas (check "enable expand" first) 4. apply a manual transformation   Result: the stretched image is confined by the dimension of the imageExpected result: the stretched image is only restricted by the size of the canvas   Workaround: Export image with enlarged canvas and use ACR from there

Camera Raw 18.2 forces all WebP files to open in ACR. Version 18.1.1 did not support WebP, so Photoshop opened them normally. Now there’s no way to disable WebP handling. Please add a toggle.

Just find out, that DENOISE dont work for RAW files from Ricoh GRIIIx (DNGs)

Landscape AI masking does not work in LRC V15. After a while no mask is generated nor displayed. Using latest W10 64 version, i7 with 32GB RAM,  Nvidia Quadro p620 with latest drivers (DirectX V12) and latest LRC process (V6). Everything worked fine until the update. Have tried disabling graphic card and same results. Any clue ? Is that happening to someone else ?

The enhance details feature appears to produce some rectangular and square noise artifacts in the processed image. My baseline is a daylight RAW landscape (call it X1) photograph taken at ISO 100. The artifacts appear in the upper half of the photo (a partly cloudy region above a mountain range).   Lightroom Version: 11.2 OS Version: Windows 10 Pro, Build 19044.1526   The steps outlined below are intended to illustrate the difference in images produced by Lightroom's baseline demosaicing algorithm with the "enhance details" demosaicing algorithm. Of course, the artifacts could be due to issues with the baseline algorithm ... but I doubt this is the case as it has been fielded for quite some time.   The TIFF comparison process (steps 11-19) has been successfully used to evaluate Lightroom sharpening and noise reduction combinations. Other than the "enhance details" DNG, I have not seen similar artifacts produced by Lightroom.   Steps to reproduce the are as follows:

On the attached photo, Distraction Removal > People replaces a group of people with a black patch, not a generated removal.   Tested on LR 15.0.1 on Mac OS 15.7.1, Mac OS 26.1, and Windows 11 Intel (so not specific to a GPU or driver). See the attached screen recordings for each of the three installations.   To reproduce:   1. Import the attached photo DSC02574.ARW.   2. In Develop, select Distraction Removal > People. Observe the group of people and their reflections are selected:   3. Click Remove, and observe that selection is replaced by a black patch rather than a generated removal:    

This is a pretty simple bug that was introduced when "Raw Details" was changed into a button instead of creating a new DNG, it removed the ability to apply raw details to several raw files then merge them to a Panorama. You used to be able to do this with separate DNGs, but now this ability has been removed, please put it back!!!   I have tried this many different ways, applying Raw Details to the raw files, when merged to Panorama it's undone and turned off permanently (visible when comparing the raw and merged Pano side by side). I tried applying raw details, then converting to DNG, then merging to panorama, same effect. The wonderful algorithm of Raw Details is completely wiped out when the image is merged to a Panorama, it used to work when it made a separate DNG, PLEASE FIX this newly introduced bug.   Have not tried but likely the same with HDR merging!  

Title: Data Loss/Corruption in .HIF files (Panasonic) when writing XMP metadata (v15.1) Description: After performing a "Save Metadata to File" (or having "Automatically write changes to XMP" enabled), Panasonic 10-bit .HIF files are becoming unreadable. ExifTool diagnostics show a "No Extents for jpeg item" warning, and file sizes are truncated (e.g., from 12MB to 4.8MB). Lightroom Version: 15.1 OS: [MacOS Tahoe 26.2] Camera: Panasonic [S1RII] Reproduction Steps: Import .HIF files from CFexpress Type B card using "Move" or "Copy". Enable "Automatically write changes into XMP" in Catalog Settings. Make any edit (e.g., Exposure +0.5). Observe file becoming "Damaged or Unsupported" in Develop module. Expected Result: Metadata is embedded without altering the image data extents. Actual Result: The HEIF container is corrupted; the image data pointers (extents) are lost/deleted. ** I am unable to attach the corrupted .HIF file as this forum does not support it.. I tried converting

Title: Camera Raw – Point Color UI bug inside Masks (color field not draggable, panel disappears) Product: Adobe Camera Raw 16.1–16.3 (also affects Camera Raw Filter in Photoshop)OS: Windows 11 Home 25H2GPU: Any (bug is not GPU‑dependent) Description:When using Point Color inside an active Mask, the color field becomes non‑interactive.The color selection circle cannot be moved with the mouse. Only the Hue/Sat/Lum sliders below the color field respond. Additionally, when clicking inside the color field, the entire Mask panel on the right side disappears while the mouse button is held down, and reappears when the mouse button is released. This makes the color field unusable. This issue does NOT occur when no mask is active, and it does NOT occur in Lightroom Classic.It happens both in Camera Raw and in the Camera Raw Filter inside Photoshop. Steps to reproduce:1. Open any image in Camera Raw.2. Create a new Mask (any type: Brush, Linear Gradient, Select Subject, etc.).3. Inside the Mask,

I have a Windows 11 pc that has all requirements to run Photoshop properly ( 4 gb graphic card , 32 gb ram, 100gb cache ) . However when working in Camera Raw(latest version) i get an error message only when using the "Landscape mask" option. The message i get is in the photo below . I tried all options possible in the performance window.....non work. Everything else works perfect until i want to use a Landscape mask.