Bug Reports

Adobe Camera RAW 18.7 problem bug fix help!I updated to the new version 18.7, and the "more image settings" menu isn't working correctly—specifically, expanding the options. It often happens that when I click the three dots, the "reset to open" or "reset to default" function triggers immediately. Why are those settings right there at the very top? I just want to export the settings to XMP, but instead, I end up resetting everything! I’ve actually lost all my edits because of this! The previous version didn't have this issue. Please fix this bug or move the reset option! 

macOS 27.0.1 / Photoshop 27.11 / ACR 18.7This possibly dates back to when Intersecting Masks first came out.It has been bothering me for a very long time. To create an intersecting mask, you create two masks that intersect with one another.And when adding the second mask, the default behavior of the brush is ADD, you press alt/opt to switch to SUBTRACT. As long as you stay in ACR, nothing will go wrong. But if you close and re-open ACR, and go to that very intersected mask, the default brush behavior of the second mask becomes SUBTRACT, and you have to hold alt/opt to ADD. You find this bug only in ACR, not in LrC or LR.Lightroom got the cursor indicators mixed up, though. 

Opened image (TIFF or DNG) via LightRoom ClassicDuplicated layerOpened new layer in ACRSelected Remove toolSelected remove PeopleTwo people selected, one of which I did not want to removeCursor changed to Zoom toolUnable to exit that Zoom mode to select the person I did not want to removePressing H to change to Hand tool did not helpSeems there is no way to deselect the selected peopleTried restarting PS; rebooting computer..  no joy in MudvilleWhat _did_ work was from the main PS window, was to select the distracting person via the lasso tool and use Gen AI to remove with the prompt "remove person".####Mac OS Tahoe 26.2Mac Studio M2 MaxPS v27.11ACR v18.7

ACR is using all 24 GB of VRAM and does not appear to release it. Earlier, I was using an RTX 5070, so I assumed that 12 GB of VRAM might not be sufficient. However, I have now upgraded to an AMD RX 7900 XTX with 24 GB of VRAM, and I am still experiencing the same issue.Any masking or scaling operation in ACR immediately consumes almost all 24 GB of VRAM. The memory is released only after I completely close ACR.

I am using Camera RAW v16.4 and LrC v13.4. A recent RAW photo had a particular item of purple colour but it shows as more like blue when imported to LrC - when using 'Camera Standard' profile. I Have not observed other colours to be quite so obviously different. Shown below, camera faithful, camera standard, and the out-of-camera JPG : Observe the centre image (camera standard profile) is more blue'ish than purple.   Looking at the Adobe profiles and all the camera profiles shows that only camera standard, portrait and landscape have this colour shift - I also included the Canon G9x standard (tweaked to show for the G7x), as I understand this uses the same sensor, it too resembles the JPG colour much better: Whilst I can certainly work around this, I thought I'd report the issue as I expected camera matching profiles to be close to the out-of-camera JPG, as it appears to be with the G9 profile.

ACR masks become misaligned after copying and inverting, or after AI DenoiseSteps to reproduce: Open several photos (I usually work with 30–50). Select all photos (Ctrl+A). Open Masking and select Subject. Without deselecting the photos, rename the mask to “Subject” for all of them. Deselect all photos. Manually edit each mask on each photo using brushes, adding/removing areas, etc. Select all photos again. Select the previously created “Subject” mask and copy it with Invert enabled. Observe that the manual edits to both the original and inverted masks are now misaligned or applied to the wrong areas. Both masks must be manually corrected across all photos. Related issues: Masks sometimes become misaligned if created or edited before running AI Denoise. The same problem occurs with the Remove tool: if objects are removed before running AI Denoise, the removal edits shift by a few percent afterward. These issues can result in substantial rework when processing large ba

one PC two OS, two different PS ver, and same results!ACR from ver 18.5 18.6 18.7 stop working! it just not open...install today new 18.7 nothing change, uninstall and back on 18.4.1 the last ver that works.win10 PS2019+ACR18.7win11 PS2027+ACR18.7  p.s. I checked whether this was a compatibility issue or something related to new library or runtime files, but I found that it isn’t. The problem is with the Camera Raw.8bi file itself. Simply replacing it with a newer version causes the ACR to stop launching, the same is true in reverse: if I take a freshly installed newer version and replace only its Camera Raw.8bi file from 18.14.1, while leaving all the other libraries untouched keeping the newer versions, ACR launches again and works normally. 

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

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

Hi, using latest Lightroom Classic on MacOS 26. I have found that sometimes LRC gets confused about the exposure. I have a two image example where the images are exposed exactly the same but the resulting pano is messed up. One half of the resulting pano is exposed correctly, the other half is light. I've only seen this in iPhone RAW HDR images. The one I kept was from Apple Camera but I've also seen it using Project Indigo camera. On the Indigo forum, another person was complaining about pano issues (black bars ending up in panos). I've also seen this issue and have example RAW images.https://community.adobe.com/t5/lightroom-ecosystem-cloud-based-discussions/p-introducing-the-project-indigo-camera-app/m-p/15440106/page/21#M106426I tried attaching example files but that failed. How can I get images to the Lightroom team?   [moved from bugs to discussions according to the community rules - Mod.]

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)

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?  

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

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 

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!  

See Full Report.txt

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

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

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

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