Originally published: September 14, 2021 · Last updated: August 17, 2026
“Cloud storage for WordPress” sounds like one feature, but it usually describes three different jobs: storing backups away from the web server, offloading the media library to object storage, or sending uploaded files to an external service. Choosing the wrong type of plugin can solve a problem you do not actually have.
1. Cloud backup
A backup plugin creates restorable copies of the site and sends them to remote storage. The objective is recovery. A good backup should include the database and the files required to reconstruct the site, and you should be able to restore it independently of the production server.
Simply copying the media library to a cloud bucket is not a full WordPress backup.
2. Media offload
Media-offload plugins move or copy WordPress uploads to object storage such as Amazon S3, Cloudflare R2, DigitalOcean Spaces or another S3-compatible service. They then rewrite media URLs so visitors receive those assets from the storage service or a CDN.
This can reduce local disk usage and improve scalability for sites with large media libraries. It also introduces a dependency: WordPress, the offload plugin, storage configuration and URL rewriting need to remain consistent.
3. Uploaded documents and form files
A third use case is storing files submitted through forms or portals in services such as Google Drive, Dropbox, OneDrive or S3-compatible storage. This is operational storage, not necessarily public media delivery.
For sensitive documents, check access permissions, retention, public URLs and who can retrieve the file. Do not assume that “in the cloud” means private.
Local copy or cloud-only?
Some media-offload systems can keep a local copy while others allow the server copy to be removed after successful transfer. Keeping both consumes more storage but makes reversal easier. Cloud-only media saves server space but increases dependence on the offload configuration.
Before deleting local files, test backups and confirm how you would migrate away from the storage provider.
What to evaluate in a plugin
Look at supported providers, URL rewriting, CDN support, migration tools, handling of image sizes, WooCommerce or custom-field compatibility if required, private-file support, logging and the process for returning files to local storage.
The current WordPress.org cloud-storage ecosystem includes plugins for S3-compatible media offload and integrations with R2, DigitalOcean Spaces and other object-storage platforms. That flexibility is useful, but provider support should not be your only criterion.
Do not confuse storage with performance
Offloading media can reduce work on the origin server, but it does not automatically optimize oversized images, poor formats or unnecessary assets. Image optimization, caching and sensible page design remain separate concerns.
Bottom line
First identify the job: recovery, media delivery or file workflow. Then choose the lightest WordPress integration that performs that job reliably. Cloud storage is useful when it simplifies architecture or removes a real capacity problem, not because every WordPress site needs another external dependency.
Source: WordPress.org cloud storage plugins.