Lightroom ecosystem (Cloud-based)

Classic error when trying to apply Lens Blur > Estimating Depth> Something went wrong. Please try again .Multiple O/s(Mac, Chromebook), multiple browsers (Chrome, Safari) , Android app v 11.2.3 .Tried clearing cache on browsers , apps, restarted Mac/chromebook. Same error Raw Image was imported into Lr previously and was working until 4/19

Hello, I’m encountering a weird one here. I have Lightroom installed on my (work) laptop and was able to edit my photos until recently.I don’t know what changed but I can no longer edit photos, the settings are not loading and stay disabled.Here’s what I tried so far.Check Lightroom on my Mac Mini and iPad - no issues Signed out of Creative Cloud on my work laptop and signed back in - didn’t resolve the issue Uninstall and re-install Lightroom - didn’t resolve the issue Uninstall again, clear some of the stuff that remains on the disk (e.g. Library\Preferences\Adobe, removed the photo library etc..) and then re-install - didn’t resolve the issueHas anyone encountered the same issue?Thanks! Here’s the technical details from Lightroom on this laptop:Lightroom version: 9.5.1 arm64 [ 20260815-1945-84a45bf ] (Aug 15 2026)NGL Version: 1.43.0.5WF Version: 8.5 20b9f90VF Version: 1.0.164HIL Version: 40501CAI Version: adobe_api/1.66.1PH Version: 6.1.1Adobe GSDK Version: 1.4.0.213CR Version: 29.5

Getting the "Something went wrong" + "Please try again later" error message when trying to apply blur (without any blur previously applied) on an image in Lightroom. I usually encounter this when my internet connection is slow. I usually resolve this by waiting till my connection improves, and sometimes just be restarting the app. Now neither of those is true, and the last stage is gets to when applying the blue is "Detecting depth using AI..." before the error is displayed. Was working fine about ~12 hours ago as of posting this. I'm thinking this is a server issue rather than a local one, but if there's anything I could do to resolve it on my end, let me know, thanks.

Llevo disfrutando de Adobe, tanto PS como LIGHTROOM desde aproximadamente año 2015, con pago mensual de cuota. En el mes de Junio por recomendación de Adobe pasé a realizar pago anual y desde este momento no he podido acceder a mis cuentas de PS y LIGHTROOM, teniendo que volver a descargas las aplicaciones nuevamente, pero no soy capaz de localizar las mas de 60.ooo fotos. Agradezco ayuda a como recuperarlas. 

It is not yet clear whether the data entry issue in the "Masks" section has been fixed, as a new problem has already appeared. It causes even more inconvenience, because it cannot be solved by switching from photo to photo and back.It is impossible to manually enter values in the "Exposure" field. Both on the main panel in general settings and in the "Masks" section. Using the mouse cursor or the up/down arrows on the keyboard, everything works correctly. But doing it manually is impossible. For example, when you need to enter exact values, such as +0.05 and the like. And this wouldn't be a big problem and could be done with the slider using the mouse, BUT there is an important catch. In the "Masks" section, when moving the slider with the mouse, it jumps only and immediately by 4 points, not by 1, as required for fine-tuning. For example, its values can only be 4, 8, 12 (and not 1, 2, 3), and so on. When I want to enter +0.06, an error message appears and the value increases straight

I have been experiencing an issue when importing MP4 (and possible other types) of video files into LR, the actual capture time (verified in the actual metadata at the import source, such as a SD Card) is being advanced by 6 hours (I am in the West Coast US LA/Seattle zone). I intially suspected something wrong with the camera capturing the video, but upon further investigation this seems not to be the case, it occurs across multiple camers (DJI Drone, GoPro, Nikon DLSR). Still pics taken at the same times come across just fine. There are no presets that I know of being applied, I checked both my desktop installation (I dont even see an option for that) and the Mobile app (which has an option for RAW files - set to "use camera setings"). I am using the most current version (7.2 20240214-0910-27200e9 build) on desktop and V 9.2.0 in Android) although this problem has been happening for a while.  It happens on both WIN10 and WIN 11 OS machines. I have attached several files: a coupl

Hi,     Idon't know if you can help me here but I got a strange behavior. I wanted to try out your Android App (Version 9.0.1) created an account and now everytime I load up a picture it shows totally blue. I can edit it and export it then everything is fine. Same if I try to take a screenshot. In the screenshot all fine. I don't know what's happening. Is it possible that's a feature of the free version?  Can you help? 😊   Thanks. Mike

Is it possible to export / save photos (Jpegs as well as raw files) to my external drive without any settings joining in on the export? I more or less just want to get the original file down to my computer, without it being affected by any changes. I’ll write a short explanation of my desired workflow / setup to hopefully further explain what I’m looking for. I want to use Lightroom cloud-based only, without involving Lightroom Classic. I start by importing my photo files into Lightroom (synced to cloud). I then cull the photos, deleting anything I don’t want. The remaining photos I rename, using a name structure which I like. Those photos are automatically saved to a local backup, sure, but I want more manual control over the folder structure etc. So basically all I want to do is save / export / download those remaining, renamed files, to my external hard drive. Is export using Original + Settings the only way to do this? Or can you name another way which doesn’t include sidecar files

Device: Samsung Galaxy A25 5GApp: Adobe Lightroom Mobile (latest version downloaded from the Google Play Store)Subscription: Adobe Lightroom PremiumIssue: Lens Blur opens and works normally. I can adjust the blur amount, bokeh shape, and all other settings. The preview is displayed correctly.However, when I adjust the Focus Range (depth range) and tap Apply, Lightroom always displays the following error:"A refinement error occurred. Please try again."The effect is visible in the preview, but it cannot be applied because the refinement process fails.I have already reinstalled the application, and the issue persists.

A question was raised on a Japanese forum stating that Exif data is not included when exporting from the iPhone version of Lightroom.I have reproduced this issue using the same environment. Is this intended behavior?----- Description of IssueWhen exporting photos as JPG from Lightroom for iPhone, the exported file does not retain camera/lens EXIF information if Content Credentials are turned off, even when Include metadata is enabled.If Content Credentials are turned on, the same export settings preserve the camera information correctly.Lightroom Desktop Version Number (Help>System Info…)Lightroom for iPhone v11.5.21If your version was purchased from the Mac App Store, please indicate that as well.Not applicable.OS Version NumberiOS 26.6.1Camera Model (sometimes necessary)Not specified.The issue occurs regardless of camera manufacturer in my tests.Step-by-step Reproduction Instructions (in precise terms, please)1.        Open Lightroom for iPhone.2.        Select a photo that shows

My lightroom isn’t responding when I want to move or delete a remove section. It keeps freezing. When I want to change the opacity, it has no problem doing that, but pauses or lags at other tasks. It has been doing that in the edit section too. For example, just clicking on the edit section to change from the remove tool will take a while. Has anyone else experienced this or know what to do?

Lorsque je télécharge mes photos sur LrC (Lightroom Classic) puis créer une collection sous LrC, la synchronisation avec Lr (Lightroom) présente un bug. Ma collection ne se range pas correctement dans le répertoire ciblé (2026 avec mon classement par année) mais reste à la racine de l’arborescence de mes albums.   

I have a DNG from a scanner that fails to allow editing in Lightroom web. Other DNGs from the same scanning session work fine.I have edited previously the picture both in Lightroom app (Android tablet) and web (Chrome 150.0.7871.128 (Build oficial) (64 bits)). No problem switching from one version to another until now.I know that the edits are updated because if I edit in my tablet (I can still use it) I see the edits in web. But if I try to open cropping tool (or any other), the spinner keeps spinning but never opens the file. I’ve checked it in Chrome and Firefox with same result. In console I see: VM15 assets:2 ERROR: The JSX attribute "showUpgrade" was passed to a component declaring a property of the same name. Ignoring the JSX attribute.nrWrapper @ VM15 assets:2VM15 assets:2 preset: getMetadata returned no info, skipping /v2/catalogs/d87293a6359541dbb8c57a7da0eae33d/assets/9510c4c65d0e4c2f840a1dfeedca618c/revisions/1b2873bbdbf04cc29e3d001bcd343ba9/masternrWrapper @ VM15 assets:2a

In Lightroom once you apply AI denoise to an image, the program becomes nearly unresponsive so editing is impossible.  For that reason I always have to apply AI denoise last, and I do it in a batch.  However, if I should want to go back and edit my images further, I now have to remove AI denoise from each one individually in order to edit them without Lightroom hanging constantly and taking ~20 seconds to apply any changes I make.  Please make it possible to remove AI denoise from multiple images at once so that they can be edited.  At the moment if I try and copy the Detail category from an image with no AI denoise applied and then paste to other images, it does not remove denoise.

no option to add photos images..

I want to edit in Topaz, so I click on Edit In and select Topaz. Topaz begins to load, but stalls after about an eighth of an inch of progress. 

I am a teacher and when I launch or when my students try to launch lightroom it immediately starts closing. We are using verison 9.5.1. It doesn’t happen on Lightroom classic. it is a school account and happens on my log in and with theirs as well. The macbooks are Airs and mine is a Pro, all M1 running Tahoe 26.2. I have tried so many things to fix this. Uninstall, reinstall lightroom, uninstall reinstall creative cloud, update all software on mac, etc. On my pro I have tried opening with rosetta, nothing.  I got it to work one time when I made a new user on my laptop and opened it and edited but now it is closing on that new user too.

Title: GPS metadata is lost when exporting multiple photos to Apple Photos on iOSProduct: Adobe Lightroom Mobile for iOSDevice: iPhone 15iOS version: iOS 26.6.1Lightroom version: latest available version as of September 2026Problem descriptionWhen exporting multiple photos from Lightroom Mobile to Apple Photos using Save Copy to Device, GPS/location metadata is not included in the exported JPEG files, even though:the original RAW files contain valid GPS/location data, the location is correctly displayed inside Lightroom, “Include Metadata” is enabled, “Location Info” is enabled in the export settings.The issue occurs specifically with batch/multiple-photo export.When I export the same photos individually using Save Copy to Device, the GPS coordinates are correctly retained and appear in Apple Photos.Steps to reproduceOpen Lightroom Mobile on iPhone. Select two or more RAW photos that contain valid GPS/location information. Verify that their locations are visible inside Lightroom. Selec

Severe lag, CPU spikes, and sustained heavy disk writes while editing (Lightroom 9.5.1, macOS, Apple Silicon)App version: Adobe Lightroom (cloud) 9.5.1OS: macOS 26.6.2 (Build 25G83)Hardware: MacBook Pro, Mac15,6, 18 GB RAM, Apple SiliconSymptoms:After just a few minutes of ordinary RAW editing (Leica DNG files), Lightroom becomes severely laggy. Sliders stop responding smoothly, preset previews don't render, and the system heats up with fans at full speed. This isn't tied to any heavy feature like Denoise or masking, it happens on basic actions.Measured evidence:- Lightroom's own CPU usage has been observed as high as 341% and 574% (Activity Monitor), with GPU usage spiking to 40%+ during simple actions like dragging one slider or switching to a new photo.- macOS generated an automatic disk-writes resource-violation report during one editing session: Lightroom dirtied 2,147.67 MB of file-backed memory over 2,123 seconds, an average of 1,011.51 KB/sec, against the system's expected limi

devo sempre riavviare lightroom se scelgo di modificare in firefly

Bonjour, je traite de la retouche de photos, l’application rame et se bloque de manière intempestive sur IMAC. Je suis obligée de quitter l’appli entre chaque traitement de photos. Avez vous le même problème s’il vous plait 

Key word search in relevance order gives the most relevant hits last.How to reproduce:1) Search for any known key word added in Light Room Classic.2) Choose search order "Relevance". Expected result: The most relevant search hits (images with the specified key word) should be first.Actual result: The least relevant search hits come first (even totally irrelevant images). There is no option to reverse the order.

After first launching Lightroom, we can enter Crop mode by pressing "C" key. Then we can do our cropping, then confirm it (as we confirm everything on a computer) by pressing Enter. But after using LIghtroom for a while (sorry that's fuzzy), Enter stops working to confirm the crop. We can stil confirm the crop by pressing the "C" key again, but for some reason Enter stops working until Lightroom is quit and restarted.  The amount of time LR has to run before Enter stops working for crop confirmation is not known - sometimes it's day, other times (like this evening) it seems to stop working minutes after launch. Something must be triggering the failure but I don't know what.  I know this sounds minor, but Enter is so ingrained as the "do it now" key since the beginning of computing that this one always throws me.  This bug has existed for the five years I've been using LR, and has persisted across all of the updates in that time. Just getting around to repo