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.

benlumley

Enable, set a user and PW via WP admin and users will be prompted via HTTP AUTH for a user/pw before being able to view the frontend.
Aim of the plugin is to protect staging sites from the prying eyes of search engine robots, and to keep out anyone who might stumble across it accidentally.
This isn’t particularly secure – password is in the database.

Password Protect Staging

So yeah - this does just what I needed, unsurprisingly seeing as I wrote it to do just what I need....



I made the plugin... it does what I need

Quickly and easily password protect a site to keep it from the prying eyes of google.

Bromate Remote Media Bridge vs Password Protect Staging