Requirements
Check these requirements before you install WP Media Cloud. Most modern WordPress hosts meet them. The usual problems are an old PHP version, blocked outbound connections and blocked loopback requests.
Software versions#
| Software | Minimum |
|---|---|
| WordPress | 7.1 |
| PHP | 8.3 |
WordPress will not activate the plugin on older versions. If an existing install is updated on an older server, the plugin pauses itself and shows an admin notice.
While paused, media URLs are not rewritten to your CDN. See Installation.
PHP extensions#
| Extension | Needed for | If it is missing |
|---|---|---|
curl | Streaming uploads to your provider straight from disk | Uploads fall back to the WordPress HTTP API, which reads each file into memory. Large files can then hit the PHP memory limit. |
simplexml (part of PHP’s XML support) | Reading replies from S3-type providers: bucket lists, error messages and uploads in parts | Bucket listing, error reporting and uploads over 64 MB fail with S3-type providers. |
openssl | HTTPS connections to your provider, CDN and licence server | Connections to providers fail. |
Every provider except Bunny.net is S3-type. Most hosts enable all three extensions by default. To check, look at the output of phpinfo() or ask your host.
On the Health tab, Download Log in the Diagnostic Log card saves a report that lists which common PHP extensions are loaded.
Outbound connections#
Your server sends files to your provider on every upload, so it must be able to make outbound HTTPS connections on port 443. Depending on your setup, it connects to:
- Your storage provider’s endpoint, for example your R2, S3 or Bunny Storage address.
- Provider and CDN APIs for zone lists, bucket lists and Dashboard stats:
api.bunny.net,api.cloudflare.com,api.keycdn.com,api.cdn77.comandoptimize.exactlywww.comfor EWWW Easy IO. api.surecart.comfor licence activation and updates.
If uploads to your provider are blocked, the file stays on your server. The Media Library row shows Offload failed with the reason, and the item appears in the failed list on the Dashboard tab.
Loopback requests and WP-Cron#

The Offload All Media button on the Dashboard tab runs in the background. It uses a loopback request, a call from your server to its own site. WP-Cron checks on the queue every 5 minutes as a backup and uploads a batch itself if the run has stopped.
WP Media Cloud also uses WP-Cron for:
- A safety check about 5 minutes after each upload, which offloads anything that was missed.
- A daily licence check.
If your host blocks loopback requests, bulk offload still moves forward one batch each time WP-Cron runs, so it is slower. This needs WP Media Cloud 1.1.9 or newer. If you turned off WP-Cron with define( 'DISABLE_WP_CRON', true );, set up a real cron job that calls wp-cron.php. Run it at least every 5 minutes so bulk offloads keep moving.
The Health tab in Media Cloud checks both. WP-Cron and Loopback Request should show a pass. WordPress Tools > Site Health also reports loopback problems.
Memory and execution time#
WP Media Cloud does not set its own minimum for memory or execution time.
- Uploads stream from disk when
curlis available. Restores stream back to disk. File size is not limited by the PHP memory limit. - The background bulk offload works in short batches. Each batch stops before it uses 90 percent of the PHP memory limit, then the next batch continues.
For large libraries, use WP-CLI. wp wpmc offload does not depend on loopback requests or WP-Cron and is faster.
WP-CLI (optional)#
The wp wpmc commands need WP-CLI on your server. They are optional, but recommended for large libraries and multisite networks. The WP-CLI tab in Media Cloud lists every command.
Browser#
The Media Cloud admin screens run in any current version of Chrome, Firefox, Safari or Edge.
Other offload plugins#
Do not let two offload plugins handle new uploads at the same time. Both would upload files and rewrite URLs.
If you are moving from WP Offload Media, Advanced Media Offloader or Media Cloud by ILAB, set up WP Media Cloud first. Then import your records on the Migration tab, deactivate the old plugin and check that Rewrite URLs is on.
Multisite#
WP Media Cloud supports multisite networks. Subsites can share one bucket with the path prefix sites/%site_id%, or each use its own bucket. See How WP Media Cloud works.