Leopard

Leopard moves files out of the WordPress Media Library and serves them from remote storage instead. Its core job is URL rewriting: once media is offloaded, references to those files point to the selected storage provider or to CloudFront as a delivery layer. That gives the plugin a clear operational purpose for sites where locally stored images and other uploads are putting pressure on the hosting account.

A remote media layer

The plugin is built around automatic offloading of new media uploads. Rather than treating the WordPress server as the permanent home for every file, Leopard sends media to an external storage service and keeps the public URL aligned with that location. The vendor positions this as a way to reduce server load and improve site speed, while retaining WordPress as the place where the media library is managed.

This is a useful separation of responsibilities. WordPress continues to provide the media-management interface, while object storage handles the files. URL rewriting is important here because it connects the existing WordPress media workflow with the remote destination instead of requiring each page or post to be edited manually.

Storage choices

Leopard covers a broad set of storage providers rather than tying the site to one ecosystem. The listed destinations are:

• Amazon S3 for established object-storage workflows.
• Wasabi as another cloud storage destination.
• Google Cloud Storage for sites already using Google’s infrastructure.
• DigitalOcean Spaces and Bunny Storage for alternative object-storage setups.
• Cloudflare R2, with CloudFront available as the named CDN option in the product summary.

This range is useful when hosting, storage and content delivery are already split across different services. It also gives a site owner room to choose a provider based on an existing account or infrastructure plan, rather than moving all of the site to one vendor.

Useful controls

File retention is one of the more important settings. Leopard lets administrators keep offloaded files on the WordPress server or delete the local copies after transfer. That choice affects how much storage is reclaimed and how easily the site can fall back to its original files, so it belongs in the media-management policy rather than being treated as a minor toggle.

WebP support adds a modern image format to the plugin’s media handling. Detailed logs and reports provide a record of offloaded media, which is valuable when checking whether files have been processed or investigating a missing asset. The interface is described as easy to use, and the stated compatibility with popular WordPress themes and plugins makes Leopard a practical fit for an existing site rather than a separate media system.

What to weigh

Offloading introduces a dependency on an external storage service. If that provider, its access configuration or the connection between WordPress and the storage location has a problem, the site’s media delivery is no longer confined to the hosting account. That is the ordinary trade-off for reducing local storage, and it makes logs and a clear retention policy important.

The retention setting creates a second trade-off. Keeping local copies consumes more server space and reduces the storage benefit; deleting them frees space but leaves the remote provider as the primary copy. The range of supported services is helpful, but it also means the administrator still has to choose and maintain the storage arrangement. Cloud storage and CDN delivery are not a single self-contained feature: the final setup depends on the selected provider and the way its URLs are used.

Who it suits

Leopard is aimed at WordPress sites with a substantial or steadily growing media library, especially where hosting storage is limited or media delivery needs to sit outside the main web server. It suits administrators who want automatic handling for new uploads, a choice of object-storage destinations and reports they can consult after offloading.

It is less compelling for a small site whose media library comfortably fits on its existing hosting and has no reason to introduce another service. For larger media-heavy installations, though, the combination of remote storage, URL rewriting, optional local retention, WebP support and offload reporting gives the plugin a focused role: keeping WordPress in charge of the library while moving the files elsewhere.