bromate

<p>Bromate Remote Media Bridge helps WordPress installations share the same database across multiple environments without requiring a full copy of the uploads directory.</p>
<p>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.</p>
<p>The plugin can:</p>
<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>
<p>This is particularly useful for:</p>
<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>
<p>A local site generates:</p>
<pre><code>https://local.example.test/wp-content/uploads/2026/05/image.jpg
</code></pre>
<p>Bromate Remote Media Bridge rewrites it to:</p>
<pre><code>https://production.example.com/wp-content/uploads/2026/05/image.jpg
</code></pre>
<p>When “Download while navigating” is enabled, the file may also be downloaded automatically and stored locally the first time it is requested.</p>
<p>This creates a progressively warmed local media cache containing only the files that have actually been viewed.</p>
<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>
<p>The remote uploads URL should point directly to the uploads directory of the environment containing the media files.</p>
<p>Example:</p>
<pre><code>https://www.example.com/wp-content/uploads
</code></pre>
<p>You may also configure the plugin using constants in wp-config.php:</p>
<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>
<p>Constants take precedence over saved settings.</p>


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.

Bromate Remote Media Bridge vs WPvivid — Backup, Migration & Staging