Bug Reports

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.

This is in respose to this problem persisting for me. To reproduce:   1) Open an image in ACR. 2) Press the B key to bring up Remove panel (or select from tool bar) 3) Brush over area to be removed 4) Press E key to bring up edit panel (or select from tool bar) 5) Press B key to return to Remove panel (or select from tool bar) 6) Note that pins are not visible. 7) Hover mouse literally over text on panel that says "Show overlay on Hover." 😎 Pins appear 9) Move mouse over other text on Remove panel, and pins disappear. 10) Hover mouse over image, pins now appear. 11) Return to step 4 and the process repeats.Note the ONLY way I can seem to get the pins to show up is if I perform step #7. This is new behavior, and never was an issue with versions beyond the last two updates of ACR.Video of behavior is attached.Apple M2 OS 15.6.1ACR 17.5

Dear Adobe Team,   I would like to report an issue regarding the Cinelike A2 profile on the Panasonic DC-S1M2 camera when processed in Adobe Lightroom/Camera RAW. Specifically, the Camera Matching setting for Cinelike A2 does not accurately replicate the colors seen in-camera.   To verify this, I conducted a test by simultaneously capturing two files—HEIF (10-bit) and RW2 (RAW)—and importing them into Lightroom for comparison. The discrepancies observed include:       1. Black & White Point Compression: The Camera Matching Cinelike A2 profile exhibits excessive compression in Black Point and White Point, whereas the HEIF file remains unaffected.   2. Color Shift in Yellow/Orange Tones: The yellow/orange lines in a parking lot appear shifted and even clipped, creating unnatural edges.   3. Incorrect Saturation Transition in Reds: The red tones in hair show improper saturation gradation—instead of darkening naturally in shadowed areas, the sa

I apologize if this has been asked before but it's tough wording to find in search and I may not even be using the right terms. So anyway, with the last handful of updates, all my "interface/layout" settings in Camera Raw have been resetting on my Silicon MacBook (but NOT on my Intel iMac). It all goes back to default... favorites are gone (profiles AND presets), vertical is horizontal again, it's back to light gray, custom panel order is reset... seems trivial (and is certainly less of a hassle than all the issue the program was putting me through a couple years back) but it is a huge time-suck and I can't figure out why it is happening on one and not the other... which also makes me feel like there may be a fix. Anyone have any insight?BOTH MACHINES : Version 17.5.0.2318MACHINE WITH ISSUE : 2024 MacBook Air, 15-inch, M3, 16 GB, Sequoia 15.6.1MACHINE NOT HAVING ISSUE : 2020 Retina 5K iMac, 27-inch, 3.6 GHz 10-Core Intel Core i9, AMD Radeon Pro 5700 8 GB, 32 GB 2667

Hello everyone,I’ve noticed that on Camera Raw, the RAW-S and RAW-M files from the Sony A7RV are rendered poorly, both in terms of color but especially in distortion correction. On Capture One and Sony’s Image Edge, the images look perfectly identical and distortion-free.On Camera Raw, however, they appear overly distorted. Here is the download link for the RAW files:  https://www.swisstransfer.com/d/2610f26d-8328-4694-b9c9-ddf1f63f33f4I did tests with RAW, RAW COMPRESSED, RAW-L, RAW-M, and RAW-S, and the issue only occurs with M and S. I need the distortion and vignetting to be corrected properly, considering that I pay for the software.I hope someone can help me.Thank you

The backward compatibility of DNG Converter seems to be broken, in particular it creates Opcode List 2 tags even when "Camera Raw 4.6 and later" or "DNG 1.1" compatibility is selected (both of which do not support Opcode List tags, as they were introduced with DNG 1.3 and Camera Raw 5.4).    This is on macOS 14.6.1 (Sonoma) and I can observe this back to at least version 13.0 (probably the oldest version that still works on Sonoma).  

I've reported on memory issues with the DNG Converter before, but it's getting worse and someone needs to tell the developers. Today it failed to convert 11 images because it ran out of memory.  This is on a 64Gb system with 32 threads (AMD Ryzen 9 3950X 16-core)From the outside looking in - I'm pretty sure there is a memory leak. I'm guessing that it opens the Sony ARW files and doesn't free up memory after converting and writing the DNG to disk.  So the more files it processes, the more memory it uses and pretty soon it runs out of memory.  It had successfully converted 42 files before it started showing the "not enough memory" errors. Before anyone suspects there was something wrong with the 11 images that it failed to process the first time, I re-ran the DNG converter and JUST those 11 images and it finished all of them very quickly and without error. This is with version version 17.1.0.2100 set to:Camera Raw 16.0 and later JPEG Preview: Full SizeEmbed fa

Dear all, Somewhere over the last few months, Lightroom's panorama merge has taken a steep nosedive. I used to merge panoramas from very challenging shots seamlessly. Aurora shots at high ISO's and dark conditions. Now however, even well lit and simple compositions come out absolutely unusable. Often, Lighroom will merge things even completely twisted and mirrored. Lightroom CC 8.4, MacOS 15.5 (2023 MacBook Pro M3 Max) Lightroom version: 8.4 arm64 [ 20250603-0500-10f89fb ] (Jun 2 2025)NGL Version: 1.41.0.11WF Version: 7.4 a9dfbadVF Version: 1.0.154HIL Version: 40501CAI Version: c2pa-c/0.6.0 c2pa-rs/0.46.0PH Version: 5.2.3 Operating system: macOSOS Version: macOS 15.5 (24F74) The images are all shot on Sony A7IV in ARW and then imported into Lightroom off the camera. I select them in the Detail's view and select "Photo Merge > Panorama Merge" and untick the Auto settings. Am happy to share RAWs with Adobe staff if needed.  Two or three landscape images, but regard

  Hello guys, I'm using Adobe Lightroom on my mobile phone (Xiaomi 15 based on Android 16) and when i try to import HEIC photos, the preview come green. I'll attach some photos.   Can some body help?       

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.

When using the Remove tool, the borders and pins don't always appear. I have to hover over the "show overlay on hover" text on the right to make them show up, and then sometimes they disppear. This is a new issue with 17.4. This was not an issue with prevous verisons of ACR. See video attached.Mac M2, ACR 17.4

LR doesn't correctly display the colors of JPEG XL's created in various color spaces by Photoshop 26.8, though several other programs on Mac and Windows do. Since Photoshop and five other programs all display the .jxls identically, that strongly indicates a bug in LR.   Tested on LR 14.4 / PS 26.8 / Mac OS 15.5.   1. Download and open this catalog:https://www.dropbox.com/scl/fi/vjd3laedf2jffxrle602i/photoshop-jxl.2025-06-24.zip?rlkey=8zbxn5so4y35j7n9clf8hmls4&dl=0    2. The catalog contains x.png, in the Prophoto RGB color space, plus five eponymous .jxl's created by selecting x.png, doing Edit In > Photoshop. In Photoshop, do Convert To Profile, select the desired profile, then Save As, JPEG XL, Embed Color Profile, Lossy, Quality 100.   The files and color spaces appear in LR:   x-srgb.jxl (correct) x-displayp3.jxl (correct) x-adobergb.jxl (incorrect) x-prophoto.jxl (incorrect) x-rec2020gamma2-2.jxl (incorrect)   appear as:   3. These p

In ACR 17.4, select multiple images and apply denoise. Highlight the amount number field and try to type something like "65". Expected: Denoise will be updated to level 65 Actual: Denoise changes start while typing and are updated at level 6. Entering 65 is not possible.   Then with multiple images still selected, try to move the slider   Expected: Denoise will be updated on mouse up, once user stops moving slider  Actual: Denoise is applied immediately, so the desired level cannot be selected   The only workaround i have found is to copy/paste the desired adjustment into the amount field.   Noted on Intel Mac, ACR 17.4, Sequoia 15.5.

ACR 17.4. I already reported that copy/paste is the only way to make a change to denoise amount, typing into the amount field or moving the slider doesn't work. Even then, multiple image settings cannot be changed.   Load multiple images into ACR Select all, apply denoise Copy/paste a new amount into the denoise amount field Expected: Denoise amount will be changed for all selected images, LIKE EVERY OTHER ADJUSTMENT IN ACR Actual: Nope. Only the first image will be changed. EVERY IMAGE MUST BE INDIVIDUALLY UPDATED.   ACR on Intel Mac, 15.5 Sequoia.

I had an unusual experience when I demonstrated PS and ACR to a meeting. I had my laptop screen duplicated to the projector and had opened a RAW file in ACR at some stage before doing other things in PS.   I closed the lid of the laptop and when I got home and tried to open a RAW file, the PS blank screen came up and the laptop froze. There was a ding when I tried to do anything.   It took a while for the penny to drop and I attached a second screen and there was ACR still on the second screen when I extended the laptop screen reather than duplicating.   I seems that ACR still retained athe second screen redirection even when there was only the one screen available, being just the laptop.   This appears to be a bug to me as PS knew to display on the single screen but ACR does not.   I was lucky to have access to a second screen. But if I could not then PS would have been unusable for RAW files showing on the 'hidden' ACR on a pseudo second screen.

Hello, After updating Photoshop, I’ve encountered the following bug in Camera Raw. When I open several *.cr2 files in ACR and use Merge to Panorama, I then try to apply Denoise. However, instead of denoising, the entire panorama turns green. The only way I can successfully apply denoising is by first saving the panorama as a DNG file and then reopening it. In this case, Denoise works as expected. Additionally, Denoise does not work properly if applied to the individual *.cr2 files before merging. Although the panorama merges correctly, the original noise reappears in the final output. I'm currently using Photoshop version 26.8.0 and Camera Raw version 17.4.0.2272. Thank you for your attention to this issue.

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.]

The most recent firmware update 10.08.03.67 for the DJI FC8282 Air3 broke the ability of LR / Camera Raw to recognize its camera as a supported camera, and the Adobe camera profiles are no longer available for the camera's DNGs.   The update changed EXIF:UniqueCameraModel from "DJI FC8282 Air3" to "DJI FC8282". But "DJI FC8282 Air3 Adobe Standard.dcp" is defined on the former camera-model name and doesn't recognize the new one.   You can download two sample DNGs from here: https://www.dropbox.com/scl/fi/is3vqeiyatkfe0m73or87/not_works_DJI_20240101111934_0001_D.DNG?rlkey=olocbbemz6vzg8l32yqsqosg2&dl=0 https://www.dropbox.com/scl/fi/4e3dgl8p5s66a9lk3lv4l/works_DJI_20231210105602_0005_D.DNG?rlkey=22xdldkjdmrbxb0i0ag0vo982&dl=0    When you import them into LR 13.1, observe that the Adobe camera profiles are available for the "works" DNG but not the "not_works" DNG. Here is the relevant output from Exiftool:     ======== not_works_DJI_2024010111193

DNGs from Google Pixel 6, 6a, 7a, and 7 Pro don't show the Adobe camera profiles in LR 13.2 and CR 16.2:  See this sample Pixel 6 photo:https://drive.google.com/file/d/1nTj7ZfUSYKXA9N3KIv22eTXnzDpBAFoy/view?usp=sharing and this Pixel 6 Pro photo:https://drive.google.com/drive/folders/144rrzLqVr7agPSGKxQOe4cgqsGCbf8LF and this Pixel 6a photo:https://www.dropbox.com/scl/fo/drz2yq2yk4q9sxd3pvn46/h?rlkey=gh1wa65jtyud6ll1mp5l33eg5&dl=0 and this Pixel 7a photo:https://www.dropbox.com/scl/fi/vsuob87pogxmj22rq0w1t/20240127.1729-Pixel-7a-3.DNG?rlkey=1yg1f0vo5x5zli1r7znorhems&dl=0  and these Pixel 7 Pro photos:https://drive.google.com/drive/folders/1NnOJ7WfKzgtKKLuPZVAOOJaqWJBb73cr?usp=sharing A similar bug was fixed in LR 13.2 for the Pixel 7:https://community.adobe.com/t5/camera-raw-bugs/p-imported-dng-files-from-a-google-pixel-7-phone-do-not-have-adobe-raw-profiles/idc-p/14446671

Description:When applying Noise Reduction in Lightroom Classic 14.4 to ARW files from my Sony A7C2, I encounter persistent green borders appearing along the left, right, or bottom edge of the image. This happens specifically when I enable the “Noise Reduction” checkbox in the “Detail” panel. Lightroom then automatically processes the image using AI-based noise reduction. Once the processing finishes, a slider appears to adjust the strength (default is in the middle). Regardless of whether I increase or decrease the slider, the green border always appears—only the intensity of the green varies (e.g. sometimes a very bright green, other times more subtle). This issue: Occurs only on Sony A7C2 .ARW files. Does not occur on Olympus .ORF files tested with the exact same steps. Does not exist in the original image (confirmed with ACR, Capture One, and FastRawViewer). Can be slightly reduced by disabling GPU acceleration or converting the file to DNG. Is clearly related to how Light

When I use the AI denoise feature a very distracting purple streak/band appears on the lower edge of the image (see screenshots). I expect Camera Raw to not produce a purple streak on the onage after using AI denoise. I was looking back at some files with AI denoise that I created with earlier versions of camera raw and I do not see this happening. The original file of which the screenshots have been taken after adding denoise AI is available here.   I´m using the AI denoise feature in the latest version of camera raw (17.4.1) , same happens in Lightroom Classic in the latest version (14.4). MacOs version is Sequoia 15.5 (24F74). The camera used to shoot the attached dng  is a Leica SL2.Many thanks for your quick help/action on this!

If multiple images are selected with different specific settings (say, Exposure) the Exposure field will be blank to indicate that there are differing settings across those images. However, if two images with different Denoise amounts are selected, the amount field is not blank and will display an incorrect value for at least some of the images.

As much as I love the Dehaze slider, there is one thing about it that I absolutely HATE and that is when it decides to go psycho in altering the color-balance/white-balance of photos.These example photos may not show up (I've had issues with photos disappearing from being uploaded), but here is one pair from earlier today... the tint setting on WB is just 50k apart, one click on the arrow key.. but the difference is HUGE.All settings are identical between the 2 photos, the only change was hovering the mouse over the WB tint slider and pressing the up/down key once.. changing from 5850k to 5800kI often get similar shifts going from consecutive, continuous-high photos from frame to frame with the exact same settings, no changes in wb settings, and it all seems related to the dehaze slider and the way it analyzes the photos.Years ago, I thought I actually had a defective camera, as the photos would change biggly even using the same exact settings 0.1sec apart.  Eventually, I tracked

Right now the 12 bit raw files of the Lumix S1RII are about 2 stops underexposed. I was hoping that with the latest Camera Raw update 17.3 a full support would be added, but it seems like it didn't happen. Will this support come in the near future? Attached is a comparision of Capture One and Lightrom, both adjusted to almost same exposure. C1 i had to increase by .5 while I had to bump up the exposure in Lightroon by 2.5, resulting in a higher noise. Shooting in 14 bit, Raw files are correctly exposed. but higher burst rates are only achieved by 12 bit.