Wrenio Media Offload

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

• Uploads new media to R2 as attachments are added (via scheduled background sync).

• Uploads existing media in batches via the Bulk Sync page.

• Rewrites attachment, srcset, and in-content image URLs to the R2 (or CDN) origin.

• Optionally deletes the local file after a successful upload to save disk inodes.

• Fills in thumbnail metadata for attachments whose local file has been deleted.

• Reconciles R2 object keys with local paths if they have drifted.

• Repairs filename-level mismatches between WordPress and R2.

• Identifies orphan R2 objects that are no longer referenced by any attachment.

Credentials

php:

com' );

Constants take priority over values stored in the database.

The reconciliation tool

R2 object keys are derived from the stable _wp_attached_file 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. )

Cleanup tools

• Filename Cleanup detects attachments where the filename portion of _wp_attached_file differs from the R2 key (typically caused by double-dot or similar normalization mismatches) and repairs the WordPress meta to align with R2.

• 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.

Pro version

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.

External Services

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.

• What is sent: the media files you upload to WordPress, plus the API requests needed to manage those files in R2.

• When: on attachment upload, during bulk sync, and during reconciliation or orphan-cleanup runs you initiate.

• Cloudflare terms of service: https://www.cloudflare.com/terms/

• Cloudflare privacy policy: https://www.cloudflare.com/privacypolicy/

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.

• 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.

• When: at activation (one-time prompt), when a Pro license is activated or deactivated, and during update checks.

• Freemius terms of service: https://freemius.com/terms/

• Freemius privacy policy: https://freemius.com/privacy/