Jono Alderson

Edge Images automatically uses your edge transformation service (e.g., Cloudflare, Accelerated Domains, Imgix, etc.) to apply performance optimizations to <code><img></code> markup.
⚠️ Important: This plugin requires a supported edge provider with image transformation features enabled (e.g., Cloudflare Pro, BunnyCDN, etc). See the Requirements section for details.
<h4>🚀 Why should I use Edge Images?</h4>
<ul>
<li>Instant Performance Boost: Automatically optimize and serve images in modern formats (WebP/AVIF) through your existing CDN</li>
<li>Zero Configuration: Works out of the box with your existing images and themes</li>
<li>No Local Processing: All transformations happen at the edge – no server load or storage overhead</li>
<li>Perfectly Sized Images: Automatically generates the exact image dimensions needed for every device and viewport</li>
<li>Cost Effective: No need for expensive image optimization services or additional storage</li>
</ul>
<h4>🎯 Perfect For</h4>
<ul>
<li>Sites with lots of images that need optimization</li>
<li>Performance-focused developers and site owners</li>
<li>Anyone using Cloudflare, BunnyCDN, or similar services</li>
<li>Sites that want modern image formats without the complexity</li>
<li>Developers tired of managing multiple image sizes</li>
</ul>
<h4>💡 How It Works</h4>
WordPress typically creates multiple copies of each uploaded image in different sizes. This approach is inefficient and often results in:
<ul>
<li>Images that are too large or small for their display size</li>
<li>Unnecessary storage usage</li>
<li>Missing sizes for modern responsive designs</li>
<li>Lack of modern format support (WebP/AVIF)</li>
</ul>
Edge Images solves these problems by:
<ol>
<li>Intercepting image requests</li>
<li>Determining the optimal size and format needed</li>
<li>Using your CDN to transform the image on-demand</li>
<li>Caching the result for future requests</li>
</ol>
<h4>⚡️ Features</h4>
Core Features
<ul>
<li>Automatic WebP/AVIF conversion</li>
<li>Intelligent responsive image handling</li>
<li>Smart <code>srcset</code> generation</li>
<li>Automatic image optimization</li>
<li>Optional <code><picture></code> element wrapping</li>
<li>Zero local processing</li>
<li>Maintains original images</li>
</ul>
Advanced Features
<ul>
<li>Fine-grained transformation control</li>
<li>Multiple CDN provider support</li>
<li>Developer-friendly filters</li>
<li>Yoast SEO & Rank Math integrations</li>
<li>Bricks integration</li>
<li>Gutenberg compatibility</li>
</ul>
<h4>🔌 Supported Providers</h4>
<ul>
<li>Cloudflare (Pro plan or higher)</li>
<li>Accelerated Domains</li>
<li>BunnyCDN</li>
<li>Imgix</li>
</ul>
<h4>🛠️ Technical Example</h4>
Your Code
<pre><code>echo wp_get_attachment_image(1, [640,400], false, ['fit' => 'contain']);
</code></pre>
What WordPress Usually Outputs
<pre><code><img width="380" height="400" 
 src="/uploads/2024/11/1.jpg" 
 class="attachment-640x400 size-640x400 wp-image-123" 
 srcset="/uploads/2024/11/1.jpg 400w, /uploads/2024/11/1-285x300.jpg 285w" 
 sizes="(max-width: 640px) 100vw, 640px">
</code></pre>
That’s multiple different images files, none of which are the right size!
What Edge Images Outputs
<pre><code><picture class="edge-images-container" style="--max-width: 640px;">
 <img 
 class="attachment-1140x600 size-640x400 wp-image-123 edge-images-processed"
 width="640" height="400" 
 src="/cdn-cgi/image/f=auto,fit=contain,w=640,h=400/uploads/2024/11/1.jpg" 
 srcset="/cdn-cgi/image/f=auto,w=320,h=188/uploads/2024/11/1.jpg 320w,
 /cdn-cgi/image/f=auto,w=640,h=400/uploads/2024/11/1.jpg 640w,
 /cdn-cgi/image/f=auto,w=1280,h=800/uploads/2024/11/1.jpg 1280w"
 sizes="(max-width: 640px) 100vw, 640px">
</picture>
</code></pre>
That’s a range of perfectly sized options for different devices and viewports, automatically optimized images in modern formats, served from your CDN, futureproofed for supporting next-generation capabilities, and with no storage overheads.
<h4>🎨 Customization</h4>
Transform Parameters 
Control every aspect of image transformation with attributes like: 
* <code>width</code>/<code>height</code>: Exact dimensions 
* <code>fit</code>: Resizing behavior (contain, cover, crop) 
* <code>quality</code>: Compression level 
* <code>format</code>: Output format (auto, webp, avif)
Filtering 
Disable transformations globally or selectively:
<pre><code>// Disable all transformations
add_filter('edge_images_disable', '__return_true');

// Disable for specific images
add_filter('edge_images_disable_transform', function($should_disable, $html) {
 if (strpos($html, 'example.jpg') !== false) {
 return true;
 }
 return $should_disable;
}, 10, 2);

// Override max width for constrained content
add_filter('edge_images_max_width', function($max_width) {
 // Example: Use a different max width for single posts
 if (is_single()) {
 return 800;
 }
 return $max_width;
});

// Customize srcset width multipliers
add_filter('edge_images_width_multipliers', function($multipliers) {
 // Add more granular steps between sizes
 return [0.25, 0.5, 0.75, 1, 1.25, 1.5, 2];
});
</code></pre>
<h4>🔧 Requirements</h4>
Essential
<ul>
<li>A supported edge provider with image transformation features enabled:
<ul>
<li>Cloudflare Pro plan or higher with Image Resizing enabled</li>
<li>Accelerated Domains with Image Resizing enabled</li>
<li>BunnyCDN with Image Processing enabled</li>
<li>Imgix with a configured source</li>
</ul>
</li>
</ul>
Technical
<ul>
<li>PHP 7.4 or higher</li>
<li>WordPress 5.9 or higher</li>
</ul>
<h4>✅ Getting Started</h4>
<ol>
<li>Install and activate the plugin</li>
<li>Go to Settings > Edge Images</li>
<li>Select your CDN provider</li>
<li>That’s it! Your images will now be automatically optimized</li>
</ol>
<h4>🤝 Integrations</h4>
Yoast SEO 
Automatically optimizes images in:
<ul>
<li>Meta tags (og:image, etc.)</li>
<li>Schema.org output</li>
<li>XML sitemaps</li>
</ul>
<h4>🔒 Privacy</h4>
Edge Images processes images through third-party edge providers. Here’s what you need to know about privacy:
Data Processing
<ul>
<li>Images are processed through your chosen edge provider (Cloudflare, Accelerated Domains, etc.)</li>
<li>No personal data is collected or stored by the plugin itself</li>
<li>Image URLs are passed to the edge provider for transformation</li>
<li>Original images remain on your server; only public URLs are processed</li>
</ul>
Edge Provider Privacy 
Different providers have different privacy implications:
<ul>
<li>Cloudflare: Images are processed according to <a href="https://www.cloudflare.com/privacypolicy/" rel="nofollow ugc">Cloudflare’s Privacy Policy</a></li>
<li>Accelerated Domains: Images are processed according to <a href="https://accelerateddomains.com/privacy/" rel="nofollow ugc">Accelerated Domains’ Privacy Policy</a></li>
<li>BunnyCDN: Images are processed according to <a href="https://bunny.net/privacy/" rel="nofollow ugc">BunnyCDN’s Privacy Policy</a></li>
</ul>
Data Storage
<ul>
<li>The plugin stores your selected settings in your WordPress database</li>
<li>No user data is collected or stored</li>
<li>No analytics or tracking is performed</li>
<li>Cache files may be created in your uploads directory for optimization</li>
</ul>
GDPR Compliance
<ul>
<li>The plugin is GDPR-compliant as it does not collect, store, or process personal data</li>
<li>Users should review their chosen edge provider’s privacy policy and data processing terms</li>
<li>Site owners should update their privacy policy to reflect their use of third-party image processing services</li>
</ul>
<h3>Development</h3>
<ul>
<li><a href="https://github.com/jonoalderson/edge-images" rel="nofollow ugc">GitHub Repository</a></li>
<li><a href="https://github.com/jonoalderson/edge-images/issues" rel="nofollow ugc">Report Issues</a></li>
</ul>

Edge Images


Kinda amazing how simply this just works with Cloudflare.  Definitely use this if you have a pro plan.  


Just worked


Although this is a new plugin, it's been developed and tested over several years and it shows. Dead simple user interface and does exactly what it needs to do with no fuss.


Smashing


I've tried this out with Accelerated Domains and it works like a charm.  Under the hood the code is really easy to understand and well written.  Recommended. 


Works great with Accelerated Domains

Turbocharge your WordPress images by using an edge provider (like Cloudflare or Accelerated Domains) and optimizing your HTML markup.

Freemius

Wrenio

Move your WordPress media library to Cloudflare R2 — and serve every attachment from R2 (or a custom domain mapped to your bucket) without changing how WordPress works elsewhere.
What it does
<ul>
<li>Uploads new media to R2 as attachments are added (via scheduled background sync).</li>
<li>Uploads existing media in batches via the Bulk Sync page.</li>
<li>Rewrites attachment, <code>srcset</code>, and in-content image URLs to the R2 (or CDN) origin.</li>
<li>Optionally deletes the local file after a successful upload to save disk inodes.</li>
<li>Fills in thumbnail metadata for attachments whose local file has been deleted.</li>
<li>Reconciles R2 object keys with local paths if they have drifted.</li>
<li>Repairs filename-level mismatches between WordPress and R2.</li>
<li>Identifies orphan R2 objects that are no longer referenced by any attachment.</li>
</ul>
Credentials
Credentials can be stored in the database via the settings page, or — recommended — defined as constants in <code>wp-config.php</code>:
<pre><code>define( 'WRENIO_R2_ACCOUNT_ID', 'your-account-id' );
define( 'WRENIO_R2_ACCESS_KEY_ID', 'your-access-key' );
define( 'WRENIO_R2_SECRET_ACCESS_KEY', 'your-secret-key' );
define( 'WRENIO_R2_BUCKET_NAME', 'your-bucket-name' );
define( 'WRENIO_R2_PUBLIC_URL', 'https://media.example.com' );
</code></pre>
Constants take priority over values stored in the database.
The reconciliation tool
R2 object keys are derived from the stable <code>_wp_attached_file</code> meta. If keys drift away from an attachment’s physical file path — for example, due to external tooling or imported content — the Reconcile page detects the drift and previews the realignment plan.
Run Wrenio Media Offload → R2 Reconcile → “Start Dry Run” to scan and preview a fix plan. (Live realignment that moves R2 objects to their correct keys is available in the Pro version — see below.)
Cleanup tools
<ul>
<li>Filename Cleanup detects attachments where the filename portion of <code>_wp_attached_file</code> differs from the R2 key (typically caused by double-dot or similar normalization mismatches) and repairs the WordPress meta to align with R2.</li>
<li>Orphan Cleanup walks the bucket via ListObjectsV2, builds the set of keys referenced in post meta, and offers a reviewable list of R2 objects that aren’t referenced anywhere. Deletion is opt-in per batch.</li>
</ul>
Pro version
A Pro version is available at https://wrenio.studio/ for users who need the destructive operations: live R2 reconciliation (moving drifted objects to their correct keys), orphan deletion (removing unreferenced R2 objects), and retry counter resets.
<h3>External Services</h3>
This plugin connects to the following external services. They are listed here so you know what data leaves your site and when.
Cloudflare R2 — required for the plugin to function.
You configure your own Cloudflare R2 credentials. The plugin uses them to upload, download, list, and delete objects in your bucket — only the bucket(s) you specify. No request is ever made to Cloudflare without your credentials, and the credentials never leave your server.
<ul>
<li>What is sent: the media files you upload to WordPress, plus the API requests needed to manage those files in R2.</li>
<li>When: on attachment upload, during bulk sync, and during reconciliation or orphan-cleanup runs you initiate.</li>
<li>Cloudflare terms of service: https://www.cloudflare.com/terms/</li>
<li>Cloudflare privacy policy: https://www.cloudflare.com/privacypolicy/</li>
</ul>
Freemius — used for plugin updates and Pro licensing.
This plugin uses the Freemius SDK to deliver plugin updates and (if you purchase a Pro license) to validate that license. By default, Freemius collects nothing from your site without your explicit opt-in. If you opt in at activation, anonymous usage statistics are shared to help improve the plugin; you can opt out at any time from the plugin’s Account page.
<ul>
<li>What is sent: only what you opt into when you first activate the plugin (or nothing at all if you skip the opt-in). When activating a Pro license, the license key is sent to Freemius for verification.</li>
<li>When: at activation (one-time prompt), when a Pro license is activated or deactivated, and during update checks.</li>
<li>Freemius terms of service: https://freemius.com/terms/</li>
<li>Freemius privacy policy: https://freemius.com/privacy/</li>
</ul>

Wrenio Media Offload

Offload WordPress media to Cloudflare R2 with URL rewriting, bulk sync, reconciliation, filename repair, and orphan cleanup.

Edge Images vs Wrenio Media Offload