Design the future of fashion, win Firefly Pro 👗✨
Connect with our global Camera Raw Community.
Recently active
Camera Raw v18.7 brings a range of workflow enhancements and quality improvements designed to help you move through your editing process more efficiently. From faster photo browsing and more consistent exposure across images to greater workspace flexibility, refined editing results, and expanded camera and lens support, this update focuses on making everyday photo editing smoother and more intuitive. What’s NewThe September 2026 release of Adobe Camera Raw brings new ways to speed up photo selection, create consistency across large shoots, and refine your editing workspace. The new Grid view makes it easier to browse and compare large groups of photos in a thumbnail-based layout, helping you quickly identify your best shots, apply ratings, and select multiple images at once. For photographers working with batches of images, Match Exposure can now automatically normalize exposure using capture metadata, with an advanced option that also compensates for changes in light conditions across
Lens Profiles apply to Camera Raw, Lightroom Classic, and the Lightroom Ecosystem products (Desktop, Mobile, and Web). Lens Profiles are available for a wide array of lenses. Not every lens is currently profiled, and of those profiled, not all are profiled for all camera and file types. For example, there may be a profile for a particular lens and camera mount for the raw file but not for the JPEG. Normally, profiles for JPEG are not supplied unless the camera does not apply a correction (e.g. iPhone, GoPro). A complete list of profiled lenses can be found here: https://helpx.adobe.com/camera-raw/kb/supported-lenses.html other helpful info: https://helpx.adobe.com/x-productkb/multi/lens-profile-support.html#Supported_lenses Lens correction for all Micro 4/3 (MFT) lenses and many newer cameras, including Panasonic and Olympus cameras, and other cameras (including Fuji X, Leica Q, and Nikon Z series)plus many point-and-shoot models from Ca
For a complete overview of camera support in Photoshop and Lightroom, visit the following article:Why doesn't my version of Photoshop or Lightroom support my camera? Make sure your version of Photoshop or Lightroom is updated for the latest camera support. If you own an older version of Photoshop or Lightroom, Adobe provides backward compatibility for the latest cameras through the FREE Adobe DNG Converter. Note: ETAs for specific cameras are not available.
Camera-matching Profiles are applicable to Camera Raw, Lightroom Classic, and the Lightroom Ecosystem products (Desktop, Mobile, and Web).Note: Not all cameras will receive camera-matching profiles. This thread is a place to request missing camera-matching profiles for specific models. Please include a complete camera model designation and a list of the specific camera-matching profiles you are requesting in your request. If your camera is already listed in this thread, please reply to the specific camera’s post rather than just posting in-line. Camera-matching profiles are provided for some camera manufacturers and models. As raw support is added for individual camera models, camera-matching profiles for some cameras may be added when raw support is initially offered. Other cameras may see camera-matching profiles added at a later date. It is also possible that a specific camera may see a long delay or perhaps not ever receive a specific camera-matching p
When presented with a New Post screen in the Adobe Community, you are given three options for Conversation Type: Discussion, Bug, and Idea. If you were searching in Discussions, the New Post window will default to Discussions. If you are searching in Bugs, the New Post window will default to Bugs and likewise for Ideas. Many customers instinctually report problems they are experiencing as “Bugs”. It is natural to think that a problem you are having might be a bug. A bug is defined, for our purposes, as “something in the software that is not functioning as it was designed to function”. Interpreting whether a behavior is a bug or not is not always easy, however. Here are some reasons why you might want to consider posting first to Discussions rather than jumping straight to reporting in Bugs: Most items reported as Bugs are not actual bugs. In a typical group of reported bugs, only about 3 out of 25* bugs reported turn out to be actual bugs. Of those, typically 2 ou
Adobe is excited to receive requests for additional features you need to enhance your workflow. What can you do to increase the chances of being heard? Don't use the words "Feature Request" in your post's title. Search for and add to existing feature requests rather than creating duplicates. There is no advantage to creating a second request for any existing feature request. One request per thread!When creating an Idea or Feature Request thread, please keep requests for features to ONE request per thread. Doing this will allow others to vote on a single, specific feature and not confuse Upvotes amongst a list of feature requests. If an Idea thread has multiple requests in it, a moderator may ask you to split the multiple requests up into multiple threads so others can vote. In the event there remain multiple requests on a thread, the first item requested will be the arbiter of where the thread will be cross-referenced or merged. Describe how the featu
Bugs should only be reported for the latest or current version of Camera Raw. If you believe you have a bug it must be verified on the latest version of Camera Raw. New bug reports will not be accepted for older versions of the software. If you believe you have encountered a bug, it is important to first search the existing bugs to see if your issue and a possible solution or workaround have already been reported. If so, please add to that thread. If not, it may be prudent to start a new thread.Greater than 90% of the bugs reported are not actually bugs. Before starting a new thread, please read:P: Do I post in Discussions or Bugs? When logging a new bug report, it's required by the Camera Raw team for the information in the report to include steps to reproduce the bug experience. Once we can reproduce an issue, then we can start to investigate a fix. Bug reports without reproduction steps will be moved to discussions.If, after some troubleshooting, we find
Issue: Camera Raw 18.6 on Windows gets stuck in the Zoom tool. When I select Masking and create a new Brush mask, the Brush cursor does not become active over the image. The Zoom tool remains active and prevents me from painting the mask.Camera Raw version: 18.6Operating system: WindowsGPU: NVIDIA GeForce GTX 1650, 4 GBSteps to reproduce:1. Open an image in Camera Raw 18.6.2. Select Masking.3. Create a new Brush mask.4. Move the cursor over the image.Expected result:The Brush cursor should appear over the image and allow me to paint the mask.Actual result:The Zoom tool remains active and appears to "capture" the cursor. The Brush cursor sometimes appears intermittently while moving the mouse, but disappears as soon as the cursor reaches the image. I cannot paint or create the mask normally.Troubleshooting already performed:- Restarted Photoshop.- Reset GPU compatibility.- Tested the GPU settings in both Automatic and Custom modes.- GPU is detected as NVIDIA GeForce GTX 1650 (4 GB).- Ca
And while we’re at it, please also fix the crop tool.Even when 16:9 is already selected as the crop ratio, Camera Raw very often still opens the Custom Aspect Ratio dialog and asks me to enter the ratio manually again.If 16:9 is selected, it should simply crop at 16:9. There is no reason to interrupt the workflow with another dialog asking for values that are already defined.This is exactly the kind of basic workflow issue that should be fixed before adding even more AI features.
This post applies to Camera Raw.Post Lightroom Feedback here This thread is now closed. Please update to Camera Raw 17.x. If you wish to provide feedback, please go to the new article. The Photography team is sharing an early look at Generative Remove, which makes it easier to remove unwanted objects and distractions, even on complex backgrounds, with a simple brush stroke. Generative Remove is powered by Firefly AI. How to use Generative Remove on a desktop: You can find Generative Remove under the newly renamed Remove panel (aka “Heal”). Make sure the “generative AI” checkbox is enabled before you start brushing (note: when unchecked, Lightroom will use Content-Aware Remove to fill your brushed spots). By default, you will be given a moment to refine your selection with an add or subtract brush. Remember to include shadows for a more accurate result! You can also skip this step by holding down ‘CTRL’ on windows or ‘CMD’ on mac as you finish your bru
Dall'aggiornamento di Camera Raw di giugno/luglio 2026, la Riduzione rumore IA sul mio Mac Studio è diventata più lenta. Un NEF da 45 MP della Nikon Z9 prima richiedeva circa 9 secondi, ora ne richiede stabilmente circa 15.Sistema:Mac Studio M2 Ultra, GPU [60/76] core, Neural Engine 32 core, 64 GB di RAM macOS [versione macOS] Camera Raw 18.7.0.2743 (sia da Bridge 2026 sia da Photoshop 2026, stesso risultato)Cosa ho già escluso:Riavvio pulito: swap a zero, pressione della memoria bassa, ANECompilerService terminato Stesso tempo con Bridge inattivo e aprendo il file da Photoshop Accelerazione GPU attiva nelle preferenze di Camera Raw Cache GPU di Camera Raw azzerataIl rallentamento sembra coincidere con l'aggiornamento che ha spostato la Riduzione rumore dalla GPU al Neural Engine di Apple. Sui portatili con GPU più piccole è un grande miglioramento, ma su un chip Ultra con una GPU molto grande il percorso GPU precedente sembra fosse più veloce.Potete confermare se sui Mac M1/M2 Ultra v
Okay… so I know I’ve gotten on to Adobe in the past… but I’m gonna do it again. Why? Why did the latest update remove the ability to sort via marked for deletion in Camera Raw? What did it streamline? What? This destroyed my entire normal editing flow. Thanks for that. To add to it, do ya’ll have a room full of people that look at Adobe software with a dartboard labeled with ways to make your users' lives harder? Its like every time I update anything (which is needed cause stuff starts crashing which is also not great for my workflow), something is moved, or gone entirely or replaced with a system that makes so much less sense its not even funny (looking at you premeire color panel). So please for the love of god, stop changing something thats working, you aren’t making it better, and return the sorting via marked for deletion because it makes absolutley no sense for that to be removed. Now there is a whole extra sorting step to do batch processes like denoises. As always, I wish I had
Announcing a new feature now in Adobe Camera Raw (17.2) – Removal of Distracting PeopleUnder the Remove dialog, under Distraction Removal, we have added an item called “People”. This feature supports faster and easier detection and removal of distracting people in an image. It is offered as a Tech Preview in the Adobe Camera Raw Plugin-only and is available now. Please try it out and let us know what works well, what doesn’t work well, and anything that might improve the experience. Thank you! Peter Baust - Dir, Product Management Posted by Rikk Flohr
Description of IssueAdobe Camera Raw repeatedly encounters a GPU out-of-memory error during normal GPU-accelerated image editing, particularly when working with masks.The error displayed is:“The graphics processor has encountered an out-of-memory error. Due to a run-time error, GPU acceleration has been reverted to Limited for the remainder of the session.”This occurs on a very high-end workstation with an NVIDIA RTX PRO 6000 Blackwell Workstation Edition with approximately 96 GB of dedicated VRAM.Importantly, the Camera Raw diagnostic log shows that GPU initialization completes successfully and that approximately 100 GB of GPU memory budget is detected. The actual failure occurs later when Camera Raw attempts to allocate/render an image mask texture.The relevant Camera Raw log entries are:Determined GPU3 hard status: success*** GL Error: E_OUTOFMEMORY (hr=0x8007000e): imageMaskTex ****** GL Error: imageMaskTex ****** Error: dng_exception (200025) in cr_gpu_tile_render_task ***TrimFoot
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.
And another issue with masks / radial filters:If I set a value to -100, it should actually mean -100.For example, setting Saturation to -100 inside a mask should make that masked area completely black and white. But in the current versions, it feels more like -50. There is still clearly visible color left.This used to behave differently a few versions ago, and the current behavior is incredibly frustrating. A value of -100 should represent the full effect, not some reduced version of it.Please stop changing basic adjustment behavior like this. It makes precise and repeatable editing much harder for no good reason.
Hello, I have hundreds of headshots to edit in Photoshop. I really like the Camera Raw Remove Blemishes feature and want to make an Action out of it. The problem is that when create an action using “photo A” and then try to use the action on another photo “photo B”, the mask of blemishes are copied from Photo A and it just puts blemishes from Photo A onto Photo B. So, instead of the Remove Blemishes Action re-processing the Blemish filter, it just applies the processing that it created when I made the action. I love the actions and have made many for all kinds of purposes that help me move through my edits faster. I can’t seem to figure this one out.If you need clarification I can try and do that.Thanks,Will
In the latest version of Camera Raw, some keyboard shortcuts have changed. Previously, you could rotate an image simply by pressing L.Now, however, they’ve switched to the combinations Ctrl + ] and Ctrl + [.I can no longer rotate the image because, to type square brackets on my Italian keyboard layout, I have to press Alt + è or Alt + +. Alternatively, Ctrl + Alt + è or Ctrl + Alt + +. The rotation doesn’t respond to the command. What should I do? It seems it’s also impossible to change the Camera Raw shortcuts. thanks
I often work with RAW files that contain GPS coordinates, but for privacy and wildlife protection reasons I must ensure that exported files (TIFF/JPEG, etc.) do not contain any location data.Right now, I have to export from Camera Raw and then run a separate step with external tools to strip all GPS tags from the output files. This adds friction to the workflow and introduces the risk of accidentally sharing images that still contain GPS metadata.I would love to see a simple checkbox in Adobe Camera Raw, for example:“Remove GPS metadata from output files” (or “Include GPS metadata in output files: On/Off”).When enabled, Camera Raw would strip all GPS tags when writing the exported file, so no GPS data from the RAW source is carried over into the output image.This would make it much easier to produce privacy‑safe files directly from Camera Raw, and would be especially valuable for professional users in wildlife photography, journalism, and other sensitive fields where publishing exact l
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!
All day since I updated PS, Camera Raw (which last updated 7 days ago) is running probably the slowest I have ever experienced. It’s unmanageable. I tried dialing back to the version of PS that was working just fine yesterday (PS 27.10) and there was no improvement. Then I tried reverting ACR and the last available installer before 18.7 was 18.4 but then my images were jacked up because they have been edited on a newer version so I just re-updated everything. I am SO TIRED of constant issues. AI features are super cool and all but I really REALLY just want the normal stuff to work at speeds that don’t make galleries take 14 business months.Just to be clear and so no one thinks I am confused - it is CameraRaw that is lagging - I haven't even tried to use PhotoShop today but the only thing different since yesterday is the PS update to 27.11. CameraRaw is on version 18.7.MacBook Air - 15 inch, M3, 2024, 16GBRunning OS Golden Gate 27.0.1** I purged my cache, deleted the old GPU and Logs fo
When I crop an image and finish with it the new crop does not fill the screen. Its stays the same size and just removes all the pixels outside the crop. In previous versions when I would confirm the crop with the enter key it with bring the new images to fit in view. Its is frustrating that I have one more button to click now every time I crop and every time and slightly adjust the crop.Im using ACR 18.4 on a 2024 M4 Mac Mini
Please Bring Back the “Constrain Crop” Option in Adobe Camera RawPlease bring back the “Constrain Crop” option that was available in previous versions of Adobe Camera Raw.This feature automatically adjusted the crop boundary when an image was rotated, preventing empty or transparent areas from appearing around the edges. It was extremely useful for photographers who need to straighten and crop large numbers of images quickly.In the latest version, this option is no longer available, which makes the cropping workflow much slower and less convenient. Users now have to manually adjust the crop after every rotation, even though the previous feature handled this automatically with a single checkbox.Removing this option feels like a significant step backward, especially for professional photographers who process hundreds or thousands of images at a time. Please restore the original “Constrain Crop” checkbox, or provide an equivalent option that users can enable or disable depending on their
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.