Camera Raw

Lightroom Classic version: 15.4.1 [ 202606201310-b9f148a4 ] Operating system: Mac OS 26 Version: 26.5.2 [25F84] Computer: Mac Studio M4 Max Camera: Canon R5 Mark III noticed that in some photos enabling Denoise results in a checkeboard-like pattern, there are very distinct tiles. This is shown in the following photo:Checker BoardI exported a catalog with the above photo including the edit history that demonstrates the issue. I couldn’t attach it as it’s ~100MB, instead I uploaded it to google drive: Exported Catalog with the above photo

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

Adobe Camera Raw 18.5This problem occurs on both Nikon D850 and D500 raw files which have been opened in ACR by right clicking on the files in the Mac finder and selecting open in photoshop.  The files have not been previously processed in any way.When I right click on the image in Camera Raw, the option for “Show Autofocus Points” is greyed out and not responsive.  I have repeated this with multiple files from both cameras taken using different autofocus modes.I have checked two of the files (one D500, and one D850) in Raw Digger to examine the EXIF data, and both show values for “Focus Position” (0x11 on a D500 file) and “AF Points in Focus” (E9 on the same file), so this metadata information should be available to Camera Raw.Are these cameras supposed to be supported by this feature?  Adobe’s documentation says nothing about what cameras are supported.I watched a video today showing someone using this feature (although with a different camera’s files), so I know that I was looking a

Hello Adobe Team,In a series of identical tripod shots, a manually created mask does not synchronize correctly.When I copy the mask to a single image, it is positioned correctly. When I synchronize it to multiple images simultaneously, the mask appears shifted—even though the camera, subject, framing, and image dimensions remain unchanged. Is this a known issue?Thanks - Michael

In some photos, applying the Adaptive Color Profile produces weird, blotchy artifacts in brighter areas, particularly in a sky where there is strong contrast between the bright and dark areas, like a sunrise or sunset. In the attached video, the photo in Develop begins with Adobe Color as the Profile, adjusting the Highlights slider brightens and darkens the sky as expected. Changing the Profile to Adaptive Color produces noticeable, blotchy artifacts in the sky. Adjusting the Highlights slider dramatically changes these blotchy artifacts. Adjusting the Profile Amount slider also changes these artifacts. Enabling HDR mode makes these blotches disappear; adjusting the Highlights moves a prominent bright band up and down in the sky, but the blotches do not appear. I reported this in another photo a year ago, but the problem remains. It means that for some photos, Adaptive Color is quite useless. Has anyone else seen this problem when using the Adaptive Color Profile?  

Attached is a photo I took this afternoon witih my new Pixel 10.  The various C2PA verifiers and inspectors are happy with it. I pull it into LrC (via the Android Lr app) and try to export it with C2PA attachment enabled. It refuses to do this, simply saying "Couldn't apply Content Credentials (1) and then the file name.   In Ps however I can open it, enable Content Credentials and then export. c2patool likes it, but the online c2pa verifiers/inspectors report breakage and failure to validate.

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

Recent Camera RAW update… when I access the Geometry panel  Shift T, the default is collapsed, I always have to click it to expand. Used to not be this way… any fix?  

I am writing this report as a long-time paying Adobe customer (over five years) because this issue has reached a point where it is seriously impacting my professional work.Today was the third time I lost 100% of my AI Denoise progress because Camera Raw exhausted all available memory and crashed.This is no longer an isolated incident. It has become part of my workflow, and I am now spending more time repeating work than actually editing photographs.My system:MacBook Air M4 16 GB Unified Memory 512 GB SSD Latest version of macOS Latest version of Photoshop 2026 Camera Raw 18.4.1I primarily work with Canon EOS RP (.CR3) files.The crashes happened so frequently with CR3 files that I completely changed my workflow and started converting every image to DNG before editing, hoping to avoid the issue.Unfortunately, that only delays the problem.Today’s session contained 347 photographs.I had already processed almost every image with AI Denoise when macOS displayed a warning that system memory h

I have some feedback and idk where else to put it! With the new update, while using Camera Raw to edit I’ve noticed some changes with the crop tool. I used to click on the crop tool and it would automatically make my image a little smaller, leaving me space on the side to grab the crop tool and you know, crop. With the update, the image size does not change when you select the crop tool, which means there’s no space between my image and the side panel, making it harder to grab the crop window. Now I have to zoom out, crop, then make my image full size again, where this step used to happen automatically.  

Using an R6III with en EF 11-24 F4L via an EF to RF adapter, and I am noticing significant barrel distortion at the wide end that the profile in Adobe Camera Raw isn’t taking out.The strange thing is that I used the exact same lens and adapter on my R6 mark 1, using the same lens profile in ACR and it corrects the distortion well.Anyone have any insights?I can correct manually but it gets tedious (shooting real estate)

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