Download from a DAM and deliver to FTP or WordPress

Use the connection that matches the destination. Media Browser Pro DAM Bridge, BrowserPro Connect Bridge, and WordPress Bridge are optional plugins; Custom FTP is independently configured. Have the correct server URL, account permissions, and intended destination ready.

Browse Media Browser Pro

1. Enable the included Media Browser Pro DAM Bridge through Plugins and configure its server/account through the existing connection settings.
2. Open its search/browse workflow. Remote search starts empty instead of loading the whole catalog.
3. Search available metadata and load another page as needed. Inspect a preview to confirm the result.
4. Choose Download Copy or Download Selected before local editing. Set download destinations in Import & Export preferences.
5. Open the local result and verify file identity, count, and metadata. Remote permissions still govern what you may download.

Deliver finished work

1. Open the final local selection and choose Export.
2. For Custom FTP, configure FTP/FTPES/FTPS and the remote destination. Test credentials and the destination folder before sending a deadline batch.
3. For Media Browser Pro, choose the configured server/destination controls. Confirm the upload target and inspect per-file errors.
4. For CMS / WordPress, enable WordPress Bridge and configure the site's REST media connection. Upload the intended media, then inspect it in that site's media library.
5. Check the actual remote result before recording delivery as complete. Uploading media is not necessarily publication of an article.

BrowserPro Connect assignment handoff

When BrowserPro Connect Bridge is included and configured, save the local assignment and open the bridge with its assignment context. Confirm the assignment match by ID/title before a preview submission, correction, or notification. The separate service owns its own account and workflow rules; local assignment save does not imply server acceptance.

Data and troubleshooting

Downloaded originals, local exports, remote previews, and uploaded files are different objects. Keep originals until delivery is verified. If a connector is absent, check plugin inclusion, entitlement, and activation. If a request fails, check endpoint/account permissions and the displayed error; do not guess another customer's destination or repeatedly submit without checking partial success. See Plugins, Export, and Cloud Storage.