bromate

Bromate Remote Media Bridge helps WordPress installations share the same database across multiple environments without requiring a full copy of the uploads directory.
Instead of synchronizing gigabytes of media files between environments, the plugin allows WordPress to use a remote uploads directory while keeping the local media library structure intact.
The plugin can:
<ul>
<li>Rewrite attachment URLs generated by WordPress.</li>
<li>Rewrite responsive image URLs in srcset attributes.</li>
<li>Redirect media requests to a remote uploads directory.</li>
<li>Progressively cache remote media files locally while visitors browse your site.</li>
<li>Reduce deployment complexity for large media libraries.</li>
</ul>
This is particularly useful for:
<ul>
<li>Local development environments using a production database.</li>
<li>Staging and pre-production environments.</li>
<li>WordPress redesign and migration projects.</li>
<li>Large sites where synchronizing the entire uploads directory is impractical.</li>
<li>Long-running projects where the production media library changes frequently.</li>
</ul>
<h3>Example</h3>
A local site generates:
<pre><code>https://local.example.test/wp-content/uploads/2026/05/image.jpg
</code></pre>
Bromate Remote Media Bridge rewrites it to:
<pre><code>https://production.example.com/wp-content/uploads/2026/05/image.jpg
</code></pre>
When “Download while navigating” is enabled, the file may also be downloaded automatically and stored locally the first time it is requested.
This creates a progressively warmed local media cache containing only the files that have actually been viewed.
<h3>Features</h3>
<ul>
<li>Rewrite WordPress attachment URLs.</li>
<li>Rewrite responsive image URLs (srcset).</li>
<li>Redirect direct media requests.</li>
<li>Progressive local media caching while browsing.</li>
<li>Automatic local storage of viewed remote media files.</li>
<li>Excluded URL support.</li>
<li>Environment-specific configuration through constants.</li>
<li>Optional debug logging.</li>
<li>No custom database tables.</li>
<li>No front-end assets.</li>
<li>Works with shared databases across development, staging and production environments.</li>
</ul>
<h3>Configuration</h3>
The remote uploads URL should point directly to the uploads directory of the environment containing the media files.
Example:
<pre><code>https://www.example.com/wp-content/uploads
</code></pre>
You may also configure the plugin using constants in wp-config.php:
<pre><code>define( 'BROMATE_REMOTE_MEDIA_BRIDGE_ENABLED', true );

define( 'BROMATE_REMOTE_MEDIA_BRIDGE_BASE_URL', 'https://www.example.com/wp-content/uploads' );

define( 'BROMATE_REMOTE_MEDIA_BRIDGE_DOWNLOAD_WHILE_NAVIGATING', true );

define( 'BROMATE_REMOTE_MEDIA_BRIDGE_DEBUG', false );
</code></pre>
Constants take precedence over saved settings.

Bromate Remote Media Bridge

Use a remote WordPress uploads directory without copying your entire media library. Optionally cache media files locally as visitors browse your site.

Bill Erickson

CultivateWP

When spinning up a staging or local development environment, you might not need the full uploads directory, but you also don’t want to see broken images throughout the site.
This plugin lets you use the production server for missing media. Define the production URL using a wp-config.php constant BE_MEDIA_FROM_PRODUCTION_URL or filter be_media_from_production_url.
In all cases, if a local file exists, it will be used in preference to the remote file.

BE Media from Production

We are using the plugin from GitHub for quite some time. Now it will be even easier, great work!

Awesome!

Sites that heavily rely on media were painfully to maintain. Not only did I have to get the local database in sync on my development machine, but also the media to get a good picture of how the site will look after a new feature I added. With this plugin this becomes a breeze as I do not have to download all media to my local machine anymore. This saves time and diskspace. Thank you Bill for this awesome plugin.

Makes maintaining sites a breeze

Just a really great complement to localhost development, especially since pretty much every backup/export utility allows excluding certain directories, like wp-content/uploads

Many thanks!

So glad I found this

Incredibly useful plugin when doing local development work on sites with huge media libraries, when you don't want to fill up your local hard drive with or spend time syncing with your remote site.

Very useful, works perfectly

For developers - Uses local media when available, and uses the production server for the rest.

Bromate Remote Media Bridge vs BE Media from Production