Skip to content

Safe Media Offload: what it doesn't do, and FAQ

  • It doesn’t purge your CDN. A replaced file keeps its URL, so purge it there.
  • Page-builder data kept outside post content, such as Elementor’s generated CSS and JSON, isn’t rewritten.
  • It doesn’t store files in non-S3 services such as Google Drive, or use Cloudflare Images.
  • With a private bucket, Easy Digital Downloads files are copied there but still served from your server.
  • On multisite, each sub-site’s files go under sites/<id>/ in the bucket, as they do on disk; the main site’s keys are unchanged. There’s nothing beyond that.
  • If you move your site to a new domain, deleting media offloaded before the move leaves its files in the bucket. Delete them there.

I replaced an image and still see the old one

Section titled “I replaced an image and still see the old one”

Files keep their names, so a replaced image or a regenerated thumbnail goes to the same URL. Browsers check again after a day. Your CDN keeps files much longer, so purge the URL there (in Cloudflare: Caching › Configuration › Purge by URL).

While every file still has a local copy, nothing: your site serves them from its own server again. If you turned on Delete local copies after offloading, the bucket is the only copy of those files, so they stop loading until the plugin is active again. The Plugins screen says how many and asks first. Run Restore local copies before removing the plugin for good.

Never from the bucket. Uninstalling removes the settings and credentials, but keeps the records of files that exist only in the bucket, so reinstalling serves them again.

Not on PHP-FPM and LiteSpeed hosts: the copy starts once WordPress has answered.

Yes. Each file remembers where it went, so earlier uploads keep working from their bucket. A new delivery domain for the same bucket applies to earlier uploads too.

Under Settings › Safe Media Offload, in the License card at the bottom.

Checked against ZealDen Safe Media Offload 1.0.3 on main, 19 October 2026.