Adobe Bridge Beta 17.0 Adds More Control to Asset Intake
A new import dialog for incoming work
Asset intake is where a tidy client handoff can start to look less tidy. One card holds several shoots, filenames vary, and the metadata fields that should help identify the files are blank. Adobe Bridge Beta 17.0, announced October 16, adds a new Import Media dialog aimed at making that first step easier to organize.
The dialog imports photos and videos from memory cards and connected devices. Before import, teams can choose a destination folder, sort assets into subfolders, set file-renaming options, and apply metadata templates. It can also convert supported files to DNG, Adobe’s raw image format, and Adobe says the workflow supports CF Express cards.
That puts several common intake decisions together at the point where files arrive. A team could, for example, set a project folder as the destination, split incoming material into named subfolders, and apply a template with project information. Renaming options could help replace camera-generated names with a pattern that’s easier to scan later. The point isn’t to devise a perfect naming system during import. It’s to make the chosen system repeatable.
Adobe’s Bridge Beta 17.0 announcement also lists a manual option to re-sign assets from the Metadata panel or the right-click menu, provided Content Credentials is enabled in Preferences. That’s separate from intake, but worth noting for teams who manage credentials as part of their asset process.
Test the naming and folder rules before client work
A beta import dialog is a good place to test a process. It’s not yet a reason to change the way a live client job is handled. A small batch of sample images and videos can show whether the folder and filename rules work as expected before anyone starts importing a full card on a deadline.
Teams can start with a few questions. Does the chosen naming pattern keep important details visible, such as a project name, shoot date, or sequence number? Do the subfolders make sense to the people who’ll review and edit the files? Does the metadata template populate the right fields, and does it avoid adding details that don’t belong on every asset?
It also helps to test files from more than one camera or device. An import rule that behaves neatly with one set of names may produce a less useful result with another. Teams working with CF Express cards can check that part of the process, too. Supported-file DNG conversion deserves its own test batch, particularly if the team’s existing handoff expects the original files to remain untouched.
These checks turn a broad setup into a real workflow trial. After import, someone other than the person who configured it can inspect the folders and metadata. If that person can identify the assets without a separate explanation, the intake pattern is doing useful work. If not, it’s better to adjust the template with sample files than to tidy up a client delivery one folder at a time.
Consistent names, folders, and metadata can make incoming material easier to find and pass along. But they only help when they match how the team and client work. A useful test includes the people who receive the assets, not just the person who clicks through the dialog. Beta software can be a fine workshop bench. A deadline is a less relaxing place to discover a naming rule needs three more exceptions.
Plan for the Adobe Photo Downloader change
Adobe says Adobe Photo Downloader (APD) will stop working on macOS 28, which the company expects in fall 2027, as Apple phases out support for Rosetta 2 apps. In its October 16 announcement, Adobe presents the new in-product Import Media dialog as its replacement for media import.
That gives teams using APD time to look at their current process and see which steps need a counterpart in the new dialog. They can note how they choose destinations, name files, organize card contents, and apply metadata today, then test those same needs with sample assets in Bridge Beta 17.0.
The timing is Adobe’s expectation, not a confirmed release date for macOS 28. And the import dialog is in beta, so teams should treat it as something to evaluate rather than assume it’s ready for production. Before changing a client workflow, they’ll want to check Adobe’s latest compatibility guidance and make sure the version they’re using supports the steps they rely on.
Where to get the beta
Adobe’s installation path is the Creative Cloud desktop app, then Apps, then the Beta tab. From there, select install for Bridge (Beta). Adobe says the update is rolling out incrementally, so it may not appear for everyone at once. If it’s missing from the app, Adobe advises waiting a few days for the rollout to reach more users.
For agency teams, the useful next step is modest: install the beta when it’s available, try the dialog with sample files, and compare the output with the team’s intake conventions. That gives the people handling assets a chance to spot gaps before the new process meets a client’s card full of footage.