Questions

The bottom image is the original one. With person removal, only the person on the bottom right corner was detected. Also, the man on the right as his right leg bizarrely recreated. 

DescriptionSince updating from Camera Raw 18.3.2 to 18.4.0 and 18.4.1, the Subject masking feature no longer works.When clicking Masking → Subject, Camera Raw immediately displays the error:"The AI selection model cannot be downloaded."No subject mask is created.SystemWindows 11 (latest updates installed) Adobe Photoshop (current version) Adobe Camera Raw 18.4.1 Intel Graphics (Geekom GT1 MEGA) Intel Graphics Driver 32.0.101.8801 Internet connection available Creative Cloud Desktop running and signed inSteps to reproduceOpen any RAW file in Camera Raw. Open the Masking panel. Click Subject. Camera Raw immediately displays:"The AI selection model cannot be downloaded."Expected resultThe Subject mask should be created normally.Actual resultOnly the Subject mask fails.No mask is created.Additional informationThis issue is 100% reproducible on my system.The following comparison was performed on the same computer, with the same RAW files and no hardware or operating system changes.Camera Ra

Only ONE distructing person is identified, while there are several.  “Exclude area from remove” doesn’t work, since cursor turns into ZOOM mode when moved to that area and you can’t point to the pin.Previous version worked much better !(I work in Windows 11)

Problem:Benutzer-Presets von Adobe Camera Raw, die Maskierungen enthalten, werden im Camera-Raw-Filter von Photoshop nicht angezeigt.Ich arbeite professionell mit Photoshop und Camera Raw unter Windows 11 Pro.Mein Workflow:Ich öffne ein DNG direkt in Adobe Camera Raw. Ich verwende bzw. erstelle ein Benutzer-Preset, das neben normalen Entwicklungsparametern auch Maskierungen enthält. Dieses Preset wird im normalen Camera Raw korrekt unter meinen Benutzer-Presets angezeigt und funktioniert einwandfrei. Anschließend bearbeite ich das Bild in Photoshop und erstelle daraus eine zusammengefasste/gesamte Pixel-Ebene. Ich öffne diese Ebene über Filter → Camera Raw-Filter. Das betreffende Preset ist dort nicht vorhanden. Auch nach Aktivierung von „Teilkompatible Presets anzeigen“ erscheint es nicht.Interessanter Vergleich:Wenn ich aus demselben Preset eine XMP-Version ohne die Maskierungsdaten erstelle, wird diese im Camera-Raw-Filter angezeigt und funktioniert dort korrekt.Damit lässt sich das

This post applies to Camera Raw.  Feedback for Lightroom Classic and Lightroom Desktop should be posted here.   Update February 2025:Adobe has introduced two Adaptive Profiles – Adaptive Color & Adaptive B&W.   Getting started with the Adaptive Profiles:  Access a profile inside the profile favorites menu.  In addition, there is a new section for Adaptive Profiles in the Profiles browser.  Enable the profile and adjust the ‘Amount’ slider as desired.  Use the rest of the Camera Raw tools just like you would otherwise.  Check out the Help Page for more detailed usage information. For more technical information on the underlying technology, please refer to this blog post.    Please try the profiles and share feedback in this community forum thread. It would help to include details like how you access Camera Raw (via Adobe Bridge or Photoshop), your computer system details, and as much information as poss

Camera Raw 18.4+ – Subject Masking Regression: identisches WinML-Modell funktioniert in 18.3.2, wird ab 18.4 nicht mehr korrekt geladenIch konnte das Problem inzwischen anhand der Camera-Raw-Logs und des ModelZoo genauer eingrenzen.SystemWindows 11 Photoshop 27.10.0 Camera Raw 18.3.2 / 18.6 Intel Arc Graphics, Meteor Lake, 128 EU Intel Grafiktreiber: 32.0.101.8860 identische Hardware und identische Photoshop-Version für den VersionsvergleichDas Problem tritt auf zwei unterschiedlichen Windows-11-Systemen auf.FehlerbildSeit Camera Raw 18.4 funktioniert in Maskieren → Motiv auswählen die automatische Motiverkennung nicht mehr.Camera Raw zeigt:„Das KI-Auswahlmodell kann nicht heruntergeladen werden.“Andere KI-Maskierungsfunktionen, insbesondere Himmel, funktionieren weiterhin.Außerdem funktioniert in Photoshop selbst:Auswahl → Motivproblemlos auf derselben Hardware.Ein Downgrade auf Camera Raw 18.3.2 behebt das Problem sofort.Adobe führt für Camera Raw 18.4 selbst eine Änderung an genau d

Updated on July 7th, 2026.This post is to collect in-app customer feedback on the Generative Expand feature in Camera Raw.  Generative Expand seamlessly blends the edges of your existing image with newly generated content that naturally fits into the background without taking away from your photo’s original subject. Some use cases for Generative Expand are: Expand the canvas for images that were accidentally cropped  Fill in the edges of Geometry Edits Adjust the aspect ratio of a photo for social media  We'd love to hear what it does well, what it doesn't, and how you'd like it to work.  Please also include the following details in your post:  Camera Raw version System details Example image(s) if you wish to share Our team continually monitors this thread. Thanks!Thanks!Peter Baust - Dir, Product ManagementPosted by: Rikk Flohr

Please can someone explain the changes to the crop tool in Camera Raw (18.3)?When using the gemoetry options I cannot crop to the edge of the image no matter what I do - this was no problem before. When the crop area is maximised, the crop tool no longer drags the cropped area, it only draws a new area to crop.This is incredibly frustrating. Please can someone tell me how to get the legacy crop tool back? This wasn’t included in any “What’s New” content I have seen.

★ I'm re-uploading because there are some corrections to make.  Starting in 2025, when using Camera Raw, a phenomenon occurs in the “Optics” section where color aberrations actually increase during distortion correction.  Even though "Remove color aberration" is checked, the color aberration is not being removed cleanly.  Color aberration is only somewhat reduced when the 'distortion" correction amount is set to 0.  When the “distortion” correction value is 1 or greater, chromatic aberration actually occurs. (This also includes the default setting value of 100.)  Also, in the latest version, even if you set the “distortion” correction to 0, it still feels like chromatic aberration is not removed cleanly, as in version 17.0.  I’m wondering whether it’s my laptop’s specs that are the problem, or if others are experiencing the same issue.   * I am currently using a Canon body and lens. I used the matching lens profile in Camera Raw as well.       

Subject: Camera Raw 18.6 – Glow/Schein effect not updating until cache resetHello Adobe Team,I am using Camera Raw 18.6.0.2698 on a Mac with Apple M5 Pro.I tested the new Glow/Schein feature on a Sony ARW file. The controls were available and responsive, but initially there was no visible change in the image preview at all, even with extreme values such as Glow 100, Range 100, Spill 100 and Warmth +100. Switching between Diffusion, Bloom and Halation also produced no visible result.I reproduced this both through the Camera Raw Filter in Photoshop and by opening the RAW file directly in Camera Raw.GPU acceleration was enabled and reported as supported. I also tested different GPU settings and restarted Photoshop.The effect only became visible after I cleared the Camera Raw cache and increased the cache size from 5 GB to 10 GB.This suggests a possible preview/cache/rendering issue in Camera Raw 18.6.System: MacBook with Apple M5 ProCamera Raw: 18.6.0.2698File type: Sony ARWPhotoshop 2026

Subject: Bug Report & Feature Requests: ACR Crop Auto-Fit Behavior Regression & iPhone 17 Pro Panorama Exposure Blending IssuesFeedback Summary & Key Requests Crop Tool Behavior Regression: Post-v18.3.2 releases no longer auto-fit/re-center the canvas after cropping. Need a toggle setting or bug fix to restore the classic auto-fit behavior. Panorama Exposure Blending Issue: Panorama stitching for individual shots taken on iPhone 17 Pro produces uneven, erratic exposure gradients (extreme highlight/shadow patches). Provided Environment: Windows 10 / AMD Ryzen 9 7900X3D / RTX 4070 Ti / 64GB RAM. Detailed Feedback Content1. Regression in Crop Tool Behavior (Post-v18.3.2) Up to Adobe Camera Raw v18.3.2, cropping an image would automatically adjust and fit the newly cropped frame to the view screen (Auto-Fit Canvas). In versions newer than v18.3.2, after applying or adjusting a crop, the canvas display remains frozen at its current zoom level/position instead of auto-adjus

My GPU is no longer being recognized by Adobe Camera Raw from versions 18.4.1 and beyond (18.4.0 has no issues). Both 18.4.1 and 18.5 are showing the issue for me. Upon upgrading to Adobe Camera Raw 18.4.1 I immediately had the "Camera Raw requires GPU acceleration to edit photos" error when launching ACR from (up to date ) Adobe Bridge. Same result with ACR used with Photoshop.  Both Photoshop and Lightroom themselves showed no GPU issues. No other editing program that recognizes my GPU is having an issue either.My system is as follows:  OS Version: Microsoft Windows 11 Pro (10.0.26200 Build 26200), Video Card: RTX 4070 12GB. Nvida Studio Driver 610.88, 64GB RAM. Since this occurred on July 20th I've installed a wide variety of versions of ACR. The error occurs only when ACR 18.4.1 or 18.5 are installed.  Downgrading to an earlier version of ACR fixes the problem, upgrading to 18.4.1 or beyond reintroduces it.I initially had this issue crop up with a year old version of the NVIDIA dri

Camera Raw 18.6 – Local Mask Sharpening/NR values become incorrectly shared between saved ISO presetsI believe I have found a reproducible bug in Adobe Camera Raw when used directly through Photoshop.Environment Photoshop 27.10 Adobe Camera Raw 18.6 Testing performed directly through Photoshop → Camera Raw, not through Bridge or Lightroom. Important troubleshooting already performedI purged the Camera Raw cache and deleted relevant .xmp files between tests as necessary, so I was starting each test from as clean a state as practical. The problem remained reproducible.Reproduction Create an ISO 1600 LNR+MASK preset with: Local Background Mask Sharpening = −10 Local Background Mask Noise Reduction = 40 Test the ISO 1600 preset on multiple different ISO 1600 photos. All photos correctly receive −10 / 40. Create a second ISO 3200 LNR+MASK preset with: Local Background Mask Sharpening = −20 Local Background Mask Noise Reduction = 60 Test the ISO 3200 preset on

Hello Adobe Team,I have found a reproducible issue with Camera Raw 18.x.System configuration:Windows 10 Pro 64-bit Adobe Photoshop 27.8 (official Creative Cloud version) Camera Raw  18.4.1 NVIDIA GeForce GTX 1050 Ti (latest Studio and Game Ready drivers tested) Intel Core i7-8700K 32 GB RAMIssue:Simply opening the Presets panel in Camera Raw causes the following error:"The graphics processor has encountered an unrecoverable error. Due to a run-time error, GPU acceleration has been disabled for the remainder of the session."After this message appears, Camera Raw becomes unstable and continues to display the same error until Photoshop is restarted.Important findings:Camera Raw 17.5 works perfectly on the same computer. Camera Raw 18.0, 18.3, 18.4, and 18.4.1 all reproduce the problem. Lightroom Classic works perfectly with the same RAW files and the same presets. The problem occurs only in Camera Raw Filter inside Photoshop. The error appears simply by opening the Presets panel. In many

camera raw 18.5 randomly freezes, doesn't crash very slow compared to past few releases

Since a few versions (18.x) DNG Converter started to not only convert my raw files, but accompanying JPEGs as well. That is not the described and expected behaviour and is somewhat annoying, because now I need to mv my raw files to a separate folder before converting and then move the results back.Since my JPEGs have a different pixel resolution than the raw files, and also from the file size, I can clearly see which DNGs derive from which source. Obviously, the JPEG is converted first and gets the basename from that. Then the raw files is converted—as expected—and gets an additional `_1` added to the basename.I have not found any setting to control this behaviour.I use Olympus cameras.DNG Converter 18.5.0.2673macOS 26.6.1, Apple silicon

I want to convert a folder full of HEIC files to JPEG and I was hoping Bridge could do this as a batch process.I am getting the following error message in Bridge (which spawns Photoshop CC in the process) when I try to open an HEIC image file:"Photoshop Camera Raw does not support HEIC files on windows". The Adobe Help page titled HEIC and HEVC media files support in Lightroom and Camera Raw says:"In the Camera Raw Preferences dialog box, ensure that the JPEG/HEIC field is set to either Automatically open JPEGs and HEICs with settings or Automatically open all supported JPEGs and HEICs. To access Camera Raw Preferences, click the Open Preferences Dialog button  in the Camera Raw dialog box." Whether from Bridge or PS I do not see the above text in my Camera Raw Preferences dialog box even though I just updated LR Classic CC, PS CC 2019 and Camera Raw this morning. Camera Raw Prefs ver 11.3.9.197Bridge ver 9.0.3.279 x64Adobe Photoshop Version: 20.0.4 20190227.r.76 2019/02/27: 1205

Error when creating in ACR 18.5.0.2673 a ‘Merge to Panorama’ with 6 NEF files, preview is OK, then saving the result to DNG : error. Lost the work, this error don’t appear with all previous version.Please advise, thanks. W11 Home 25H2 64GB RAM - Nvidia RTX-3070 8GB Studio driver 610.88PS 27.9.1 - ACR 18.5.0.2673Graphics Processor Compatibilty CheckPass:    DirectX availablePass:    DirectX feature level 12.2 available, feature level 12.0 requiredPass:    Above required VRAM (8018 MB of 1500 MB required)GPU Detected: NVIDIA GeForce RTX 3070 (NVIDIA)System infoAdobe Photoshop Version: 27.9.1 20260803.r.1 65900e1  x64 (final, Release)Number of Launches: 164Operating System: Windows 11 64-bitVersion: 11 or greater 10.0.26200.9168System architecture: Intel CPU Family:6, Model:7, Stepping:1, AVX2, AVX-512, HyperThreadingPhysical processor count: 8Logical processor count: 16Processor speed: 2496 MHzBuilt-in memory: 65408 MBFree memory: 41949 MBMemory available to Photoshop: 51302 MBMemory use

It seems like selection zoom has been removed entirely. I mean, seriously? Whose bright idea was this? I HATE scrubby zoom, and don't want to be forced to use it.

This is the kind of message I get from version 18.4.1 to version 18.5.0 when I launch the module from Photoshop. 

Xiaomi 17 Ultra Telephoto DNG is not correctly identified by Camera RawEnvironmentAdobe Camera Raw / Lightroom Classic 15.4.1 Xiaomi 17 Ultra Native DNG files captured directly by the phoneSummaryThe Telephoto camera of the Xiaomi 17 Ultra appears not to be identified correctly by Camera Raw.This causes two independent features to fail:Automatic Lens Profile matching. Automatic DCP camera profile matching.The Wide and Ultra Wide cameras of the same device work correctly.Steps to reproduceOpen a native DNG captured with the Wide camera. The correct Adobe Lens Profile is automatically selected. A custom DCP profile whose UniqueCameraModel matches the DNG is correctly listed and can be selected. Open a native DNG captured with the Ultra Wide camera. Same correct behaviour. Open a native DNG captured with the Telephoto camera. No Lens Profile is automatically selected, although the correct profile exists and can be selected manually. A custom DCP profile with the matching UniqueCameraM

Every time I try to edit raw NEF files from my Nikon camera, camera raw feels unusable. It is so slow and feels like it is going crash or freeze.Looking at other users, these issues are continuous, going back 6 years plus.I was getting so frustrated that I spent a lot of money on a new PC. and its no better.Processor    Intel(R) Core(TM) i7-14700 (2.10 GHz)Installed RAM    32.0 GB (31.8 GB usable)Graphics card    AMD Radeon RX 9060 XT (16 GB)Storage    277 GB of 2.73 TB usedSystem type    64-bit operating system, x64-based processor Camera Raw 18 what is going on? 

I have a 100 year old photo that was oil painted and framed in an oval with bowed glass. I tried very hard to light it without having a reflection of the light in the photo, but because the glass is bowed, I still had some reflections. The distraction remove tool, even at Best quality, doesn’t seem to do much. Honestly, I can’t see any significant different between before and after. Before distraction removalAfter distraction removal at BestYes, I realize the image is dark, but I thought I would brighten it after removing the glare. Any ideas? Is this tool not going to work on bowed glass? 

In the latest Camera Raw update, it stopped accessing graphics acceleration, and I can't activate it.My setup:Windows 11NVidia RTX 5070 Ti 16 GBI've tried absolutely everything: cleaning the card driver and reinstalling it, adding .old to the folders, resetting the graphics card, etc., and finally contacting Adobe technical support... who started by saying that the card was "old" and not suitable for Camera Raw... Adobe, if that's the case, please indicate it on your website, because supposedly my card is suitable (and if it isn't, few people will be able to continue using Adobe products). Lightroom handles everything without a problem, and the other programs that require GPU resources do too (Da Vinci, Topaz, etc.). After saying this, the card is suitable; the problem is with Windows. I honestly don't think so; it seems like a bug in Camera Raw. That's the only thing that has problems. I don't know, maybe it's a credentials issue or something.I'm mentioning this because I think it's a

It seems the “guidelines” warning is back in Camera Raw after having been absent for quite a while. Today, simply trying to remove the edge of a wall in an image generated the “this doesn’t fit in the guidelines” warning message that I haven’t seen in Camera for over a year now. I realize that perhsp I hadn’t conisdered the wall’s feelings about being removed from the final image, but in all seriousness, removing things like softbox edges and other minor background intrusions seems to be exactly what these sort of tools can make short work of. Please have a look and see if the guidelines can be adjusted to be more useful. I can easily go fix this in PS and will, but something simple like this shouldn’t require a trip to PS.