Bug Reports
Recently active
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文件?春节拍的,到现在无法打开
Bridge 16.0.4 fails to launch on Windows 10 with "EnumResourceNamesA" entry point errorWindows 10 Pro 22H2 (Build 19045.6466)Bridge 16.0.3.21 works correctly.Updating to Bridge 16.0.4 causes Bridge to fail immediately on launch with:"The procedure entry point EnumResourceNamesA could not be located..."Photoshop 2026 works normally. Downgrading Bridge back to 16.0.3.21 resolves the issue immediately.
Windows 11, RTX 5080, AMD 9950X3D, three displays. Two 3840×2160 displays at 150% scaling and one 1920×1080 at 100%. Photoshop 27.9.1.When Photoshop is already running, opening JPEG/RAW files from Bridge works normally.When Photoshop is completely closed and Bridge opens a file, Bridge launches Photoshop and the Photoshop canvas develops a visual corruption/stretch along the bottom and right edges when zooming.The problem occurs with OpenCL enabled and disabled.Launching Photoshop directly and then opening the same files produces no corruption.Changing either 4K monitor from 150% to 100% also eliminates the problem. Photoshop already running → Bridge sends JPEG → Photoshop: no stretchingPhotoshop closed → Bridge sends JPEG → Photoshop launches → stretching occursOnce Photoshop is already running, subsequent Bridge → Photoshop opens are normal. Also the latest version of Camera RAW (18.5) disables GPU acceleration and seems to behave as though it can no longer see my GPU, i get the mess
Hi,Under the AI Act, creators are required to identify images created or retouched using AI and to specify this information within the file—likely in the XMP data. I work with open-source software but use Adobe to manage my rights. With the AVIF and WebP files I have been trying to publish online, I am unable to specify this information in the IPTC Extension field. I would also like to point out that the XMP data generated by Bridge for more traditional digital creations references obsolete URLs, such as: https://cv.iptc.org/newscodes/digitalsourcetype/softwareImage It would be appreciated if you could update Bridge so that I can work properly and remain legally compliant. Resources for your services: https://cv.iptc.org/newscodes/digitalsourcetype/ Regards.
100% reproducible
OutputOutput SettingsNew Custom ProfileHeader/Footers - Will allow me to change the header font colour. But not the divider or footer colours. Will allow me to open the colour picker, and input the new RGB and/or the HEX Value. But will not save the change. I hit ok. But it just reverts back to the same colour.
M1 Macbook Pro. Having screen flickering for 50% of raw images. Was happening on 14, 15 and now 16 version of bridge. This is making me furious! Have 3tb of photography to work through. This is one of the most basic key functions of being able to view images.Aside from not correctly showing 100% previews which has also been for years. The flickering (as if repeated reloading and switching color profiles) when space bar viewing images is just shocking. There are posts on this going back to 2020.I've done restarting. Fresh installs. Clearing caches. Turning off generating, turning off keeping color profiles, tried generating previews for entire folders. There is not any combination that works to stop this happening.This was happening on Sonoma and is still there in Tahoe.
When editing capture time there is no way to specify time in 24h or specify AM/PM, so for change time to 22:00:00 I have to set 10:00:00, and then verify if it asumed 10am or 10pm, if it asumed 10am I have to edit the hour individually and raise the value 12 times, and verify again.
Products: Photoshop 27.8.0, Bridge 16.0.5, Adobe Camera Raw 18.4.1.2647Hardware: Mac Mini M4 Pro with 24 GB, Apple Studio Display XDROS: macOS “Tahoe” 26.5.2Symptoms: Bridge deletes the sidecar (.xmp) file associated with a raw file, when a another file (with similar name, but different type) is deleted.Steps to reproduce:1) Double-click a thumbnail icon in Bridge to open a raw file (example: myFile.nef) in ACR.2) Make a simple edit with ACR, for example: changing exposure or contrast.3) Click "Done" to save the change and close the ACR window. Bridge should now show a small graphic superimposed on the thumbnail icon, to indicate that a sidecar file (myFile.xmp) has been created. In Finder, you should see the sidecar file in the same folder as the raw file.4) Use Bridge to re-open the same raw file in ACR.5) Click the "Convert and Save" icon (upper right of ACR window) to bring up the "Save Options" dialog.6) Select a different format (jpg, avif, etc.) to create a new file from the con
I hate Bridge's behavior since the last updates. When I open Bridge, it doesn't remember the folder I'm working in; it alternates between the current folder and the previous folder each time I open it! It's annoying!
操作系统:Windows11 24H2软件版本:Adobe Bridge 15.0.4.534HEIC照片名字或者存放目录带有中文名称,BR中就无法进行预览。
i cant label the photos exported by Magimir (.jpg) and i cant drag&drop from Filezilla to Bridge. Pls label thumnail pts on .psd to prevent confuse .jpg and .psd on the same photos
Summary: Drag-drop a new folder of images to Bridge and about 30 images in it starts making previews on demand.Steps:It is common for Photographers to quickly divide photos of a shoot into topics. Quick glance at Thumbnails (Windows or Bridge) and move them into folders. Folders contain 100 or more photos When done going through a folder of photos, rating the good ones, Photographer drags the next folder to the Bridge Preview Panel to start rating the next topic. About 30 photos into rating the photos Bridge starts creating Previews one at a time. On demand. This is very annoying. Theory: A Thread making the previews has suddenly died. HIGHLY REPEATABLE. For years. It can happen the first time a new folder is drag-dropped to Bridge. It can happen the 3rd time the next folder is drag-dropped. IT WILL HAPPEN. My experience: DAILY. Every single day I reach this time consuming problem.Workaround: Restart Bridge. Sometime repeatedly on days when there are a dozen of topics to cull or rate
Mac mini m2 pro os Macos Tahoe problem is ever time try open Bridge not openI do update new version still same problem
Product: Adobe Bridge 16.0.5.19Platform: WindowsSummary:Bridge does not retain the size and desktop position of its main window when it is closed in the normal (restored/non-maximized) state.Steps to reproduce:1. Open Bridge.2. Restore the window so it is not maximized.3. Resize it to occupy approximately the left two-thirds of the screen and position it at the left edge.4. Exit Bridge normally.5. Launch Bridge again.Actual result:Bridge opens with a different normal-window size, shape, and/or desktop position.Expected result:Bridge should reopen using the same normal-window dimensions and screen position it had when it was closed.Additional information:- The maximized state is remembered correctly. If Bridge is closed maximized, it reopens maximized.- The problem specifically affects the saved coordinates and dimensions of the restored window.- Saving or changing a Bridge workspace does not solve the problem; workspaces control the internal panel layout.- The behavior persists after r
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.