Bug Reports

Since updating to the latest version of Photoshop and Camera Raw, the "Image Processor" batch script initiated in Bridge stops working when processing TIFF files with previously applied parameters in ACR. Instead of smooth batch processing in the background, the process freezes, and Adobe Camera Raw either forces an interactive window or interprets specific layer metadata/color profile information in the TIFF files as a required edit prompt.This completely disrupts established, automated, professional workflows. The exact same TIFF files processed without any issues in previous versions of Photoshop/ACR, and reverting to the older version immediately resolves the issue. This indicates a regression in how the latest ACR engine handles raster files during batch operations.Product and Version: Photoshop 27.10 / Camera Raw (latest version)Operating System: Windows 11 ProExpected Result: The image processor should sequentially batch convert TIFF files in the background, without launching th

I tried launching Photodownloader first, then plugged my Iphone 17 into the computer, and when I try to download the photos, Downloader crashes. I had the same issue with my iPhone 13 mini.  I would share the entire crash report, but your system won’t let me as its too big.  

IMac 2017 27” 8GB RAM 4GB GPU i5 Quad Core running Ventura 13.7.8The latest Camera Raw update made my Denoise feature no longer work. I use Bridge/Camera Raw to sort, short-list and edit my performance show photography work. Since the update, Bridge doesn’t work properly - I can no longer preview NEF files, they begin to disappear to greyed out before my eyes. Any that were labeled and short-listed are no longer viewable nor able to be opened in PS. They are also not able to be previewed in FINDER as an image thumbnail like normal - it just has the white box with NEF and I cannot organise/view them there either - it’s like whatever file I try do something with in Bridge has now completely corrupted their appearance and labels etc on them. I have deadlines and have lost many precious hours since this stupid update that has now rendered my Bridge useless and having to revert down to Camera Raw V17.2 to be able to use Denoise in LR I’d rather not have to start this whole process again usi

I’m posting here out of frustration. I just purchased a new $1500 Microsoft Surface with the Snapdragon processor, and Adobe Bridge will not run properly on it.I’ve used Bridge since version 1, and I pay over $700 per year for my Creative Cloud license. On top of Bridge not working, several other CC apps still don’t run on Windows ARM, which makes the situation even worse.At this level of investment, core Adobe applications should be fully compatible with modern Windows ARM devices. This is a major issue for anyone relying on Adobe tools in a professional workflow. Please address this — it’s critical.

Weird jumping around of the screen when trying to move panels around in Br.Here’s a loom Here’s a screenshot in case you can’t view the loom.This happens when trying to drag a panel to a different spot in the application 

When using Camera Raw, Photoshop used to launch when you selected “Open Object”, and load the images you were working on so you could do additional editing in Photoshop. Now if you select more than one image in Camera Raw, select “Open Object”, Photoshop launches; however, it does not load the images you want to edit.  MacBook Pro M5, macOS Tahoe 26.6.2 (25G83) Adobe Bridge 16.0.8.10, Adobe Camera Raw 18.7.0.2743, Adobe Photoshop 27.11.0

Viewing swatches from an InDesign file in the metadata panel - the swatch types are cut off on the right side. Some other things are cut off as well - the second screenshot is from preferences. I’m on a Mac. I have tried changing the interface scaling but it doesn’t make a difference.   

EnvironmentWindows 11 25H2, OS Build 26200.9457 Adobe Bridge 16.0.8.10 Photoshop 27.9 Camera Raw 18.5 NVIDIA GeForce GTX 1050 Ti Eizo CS2420 wide-gamut monitor Current Windows display ICC profile: CS2420(45622097)05Eizo_100cd_ISO1246.iccProblemAdobe Bridge displays my photographs with significantly desaturated/muted colors compared with Photoshop.The same image looks correct in Photoshop but noticeably washed out in Bridge.Photoshop document profile is Adobe RGB (1998), 16 bit/channel, with the ICC profile embedded.Bridge Color Settings are synchronized with Photoshop and use Adobe RGB (1998) + Gamma 2.2.I also tested JPEG files:Adobe RGB JPEG → washed out in Bridge sRGB JPEG → also washed out, although slightly closer to PhotoshopI have also:Disabled Proof Colors in Photoshop Purged the Bridge cache for the affected files Set Bridge Preview Size to Standard Set Preview Generation to Always Generate Confirmed that the Windows display profile is the correct Eizo calibration profileNone

I am a professional Photoshop user, and this is a serious production issue.Problem:When I open or send an image from Adobe Bridge to Photoshop, the entire Image → Adjustments menu is disabled. This means that essential commands such as Levels (⌘L) are no longer available.The problem is reproducible: Select an image in Adobe Bridge. Open/send the image to Photoshop. In Photoshop, Image → Adjustments is greyed out and unavailable. Close the document. Open the exact same file directly from Photoshop using File → Open. Image → Adjustments is immediately available again, including Levels (⌘L). This clearly suggests a problem in the Bridge → Photoshop workflow, rather than a problem with the document itself or with the Levels adjustment.For professional users, this is not a minor interface issue. Levels and the other commands under Image → Adjustments are fundamental Photoshop tools that have been part of professional workflows for decades. Having these commands silently disabled d

Bridge fails to download unto new Surface Pro tablet

Hello,Adobe Bridge 16.0.7 removes AdobeXMPScript.dll, which is required for scripts to access metadata. Thus, this update has broken all scripts that access metadata.Adobe’s JavaScript Tools Guide specifically states to use this bit of code to load the XMP scripting API:if (ExternalObject.AdobeXMPScript == undefined) ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript');Running that code now produces this error:IOError: File or folder does not existVisiting C:\Program Files\Adobe\Adobe Bridge 2026 also shows that AdobeXMPScript.dll is gone.​Tested on Windows 11 25H2. I downgraded to 16.0.6, and AdobeXMPScript.dll reappeared and scripts started working again.

i mark all the files for keywords. i try to export to txt file. but it dont work. i use Adobe Bridge 16.0.7.36. in microsoft windows operating system.

As of version 16.0.6.9, images in Bridge are still flickering when viewing in Preview Mode or in Slideshow. This renders the program completely unusable - this needs to be fixed now!

Drag from Adobe Bridge 16.0.7.36 to an open message in Apple Mail 16.0 does not work.  Only a ? icon is put in the message.  I can drag to desktop, then drag to mail without a problem.  I am using macOS Golden Gate 27.0.  This worked before macOS 27 update.

Adobe Bridge 16.0.7.36 cannot reliably find files by filename, even when those files are plainly visible in the folder being searched.Example files visible in Bridge:G0005 HQ.jpgG0005.jpgG0005.psdG0005.tifI tested two different Bridge search methods: Quick Search for "g0005" Edit > Find, using: Filename contains "g0005" Current folder and all subfolders Both returned no results.Windows Explorer finds the same files immediately.I also purged the Bridge cache for the files in the folder and allowed Bridge to rebuild it completely. The files remained visible in Bridge, but both search methods still failed to find them.This is not a complex metadata query. It is a basic filename search for files that Bridge is already displaying.If an image browser cannot reliably find a file by its filename, that seriously undermines one of its most basic functions.For now, I have to use Windows Explorer for searches because Explorer finds the files correctly.

Adobe Bridge drastically reduces my Internet speed when it is open.With Bridge closed: approximately180 Mbps download / 250 Mbps upload.With Bridge open: approximately40 Mbps download / 80 Mbps upload.The problem occurs with bothBridge 16.0.3.21 and 15.1.7.I tested:Photoshop alone: no problem.Reset Bridge preferences: no improvement.Startup scripts disabled: no improvement.Windows proxy disabled.Blocking Bridge.exe in Windows Firewall: no improvement.No network drives or folders configured in Bridge.The problem is confirmed with both Ookla and Eolo Speed Test.Very unusual behavior:openingEdit > Preferences > Advancedtemporarily restores normal Internetspeed (around 200–300 Mbps). Closing Preferences immediately reduces the speed again.The problem is reproducible every time.OS:Windows 10 

I am running Windows 10 and currently using Adobe Bridge version 16.0.3, which works perfectly for my workflow. Because I have no plans to upgrade to Windows 11, v16.0.3 is the final compatible version for my operating system.Despite this, the Creative Cloud Desktop app is permanently stuck displaying a red notification badge and a "Not Compatible" warning forcing me to update to Bridge v16.0.6—an update my system cannot physically install.It is a massive oversight in user interface design that users cannot dismiss, hide, or ignore updates for applications that are hard-locked by operating system requirements. I want to receive update notifications for Photoshop and Lightroom, but I am forced to look at a permanent, un-dismissible warning for Bridge.I am demanding that the Creative Cloud Engineering team implement an "Ignore Update" or "Hide this Notification" switch.When an app reaches its final compatible version on an OS, the Creative Cloud app should:Recognize that the maximum comp

When using the Metadata panel in Bridge, using Tab to jump to the next field (standard behavior for decades in any UI with fields), the order is unpredictable. One day the tab order will behave one way, and another day another way. Sometimes they’ll even go in order!! Who knows, there is no rhyme or reason.This has happened for years in Bridge, back through Bridge 2024 at least. It seems to be only in MacOS, but I haven’t cross-checked in Windows enough to be sure. Immensely annoying as I daily am keying in metadata values, and being forced to use the mouse to swap fields is a big drag.Sometimes restarting the app fixes it, not always.Sometimes rebooting the Mac fixes it, not always. I haven’t found a reliable workaround.

Since the latest Bridge update (~1 week ago), I can't save changes in the editor. The Save button (usually bottom-right) and other bottom-of-screen options vanish, as if the window is cut off—even in full-screen. Using Windows.

Bridge does not safe edits in camera raw permanently.Open multiple pictures in camer raw, make edit, save with “Fertig”.Change filters in Bridge. Open pictures again. Some pictures have lost the edit. I gave camera raw and bridge plenty of time to safe. (CPU load was back to base) Is not usable like this!

Images often flicker obnoxiously in slidewshow mode.

Hi guys, question: Why does Adobe Bridge from version 2025 not show thumbnails/previews for the MP4 (maybe other rich media files with video content)? It was so a handy/useful function, and it really works well. I didn´t change anything in the production chain, taking video the same way as I did before, and it stops working and displays just an annoying icon of the player instead. I tried to clean up the cache (Purge cache for selection) as well as to reinstall HEVC codecs in Windows, but nothing helped. Is there any reason why this stops working? Thank you very much for the answer. Have a nice day 🙂Configuration: PC / Windows 10 fully updated / Adobe CC 2025 all apps / GPU Nvidia - drivers updated as well.

.rar compression in bridge has problem. When i compress a file to rar in bridge the original name of the file loose a part

Version 15.0.2.432 (but the issue is present in prior versions)I am using a very high-end machine, and Bridge performs well when connected to the internet. However, I am often offline for days at a time in the field while taking and processing photos. Bridge is effectively unusable when there is no internet connection. Once I'm back online, the issue disappears. To be specific, the issue involves extreme lag when adding/removing labels, ratings, navigating thumbnails, viewing "high quality preview" and opening images into Camera Raw. I would imagine that many other actions are impacted by the issue, but these are the actions I most often perform when culling images in the field while offline.I am 100% certain that Bridge is attempting web calls on nearly every single user action (presumably for Adobe's own internal user analytics), and it is doing so in a terribly inefficient manner that renders the software inoperable with repeated crashes and/or unnecessarily long wait times between

ADOBE怎样解码华为MATE80手机拍摄的DNG文件？春节拍的，到现在无法打开