Discover, trust, install: FAIR 1.0 is here

Move your WordPress media to Oracle Cloud Infrastructure (OCI) Object Storage and serve it directly from there—reducing disk usage, speeding up delivery, and keeping your uploads organized.

Key features
– ✅ Offload new uploads to OCI Object Storage (S3-compatible, path-style).
– 🔁 Backfill existing media in batches, with progress notice and stop button.
– 🔐 Supports private and public buckets.
– 🔗 Rewrites media URLs to load from your bucket (or your CDN in front of it).
– 🩺 One-click Health Check to validate credentials, bucket, and endpoint.
– ⚙️ Non-destructive option to keep a local copy of files.
– 🧩 Works with common media workflows and doesn’t lock you in.

How it works (quick start)
1) Go to Media → OCI Offload and enter your Region, Namespace, Access Key, Secret Key, and Bucket.
2) Click Save, then enable Offload new uploads (and optionally Keep local copy).
3) Use Backfill to move existing media (optional).
4) Optionally put a CDN in front of your bucket for global performance.

Who is it for?
– Sites that want to save disk space on the web server.
– Publishers that prefer serving media from OCI directly or behind a CDN.
– Teams needing simple, reliable S3-compatible offloading with minimal setup.

Privacy

No telemetry. Only your configured requests to OCI are made.

External services

This plugin connects to Oracle Cloud Infrastructure (OCI) Object Storage in order to upload and read media files.

• What service is used and why: Oracle Cloud Object Storage (domains under *.oraclecloud.com, for example {namespace}.compat.objectstorage.{region}.oraclecloud.com) is used to store (PUT) and retrieve (GET) your media files and to run an optional health check.
• What data is sent and when:
  • When you enable “Offload new uploads”, each uploaded attachment (file contents, filename/path) is sent via HTTPS PUT to your configured bucket and namespace.
  • The admin Health Check uploads a small text file and immediately reads it back to verify connectivity.
  • Standard request metadata such as your server’s IP and user agent are visible to Oracle as with any HTTPS request.
• Authentication: All requests are signed client-side with AWS Signature V4 using the Access Key ID and Secret Key you provide in the plugin settings. Keys are stored in your WordPress database (options) and are never sent anywhere except as part of the standard signature headers to OCI.
• Privacy and terms: See Oracle’s Terms of Use and Privacy Policy.
• Opt-out: Disable “Offload new uploads” or deactivate the plugin. The plugin does not contact any external service when offloading is disabled., keep description exactly same

1. Install and activate the plugin.
2. Go to Media → OCI Offload (or Settings → OCI Offload) and fill in Region, Namespace, Access Key, Secret Key, Bucket.
3. Enable Offload new uploads and optionally Keep local copy.
4. (Optional) Run Backfill to move existing media.
5. (Optional) Place a CDN in front of your bucket for faster delivery.

1. 

   Explainer: how media offloading works with OCI Object Storage.

1.3.3

• Fix Bugs
• UX improvement
• Admin JS moved from inline to enqueued file to comply with wp.org guidelines.

1.3.2

• Backfill UX: show “Backfill in progress…” while running and add a Stop button to cancel remaining batches.

1.3.1

• S3 signing aligned with mc: removed extra region headers and always send explicit Content-Length to avoid 403/SignatureDoesNotMatch on OCI.