Description
Adoovy Media Offload moves your WordPress media files to S3-compatible cloud storage and serves them from there, so your server stays light and your images load fast, wherever your visitors are.
Running out of disk space? Paying for a large hosting plan just to store images? Want to deliver media through a CDN? Adoovy Media Offload uploads new files automatically, moves your existing library in bulk, and rewrites media URLs on the fly, so your posts, pages and page builders keep working without any content changes.
Why use it?
- Free up server space and cut hosting storage costs
- Reduce server load by letting your storage provider or CDN deliver media
- Faster global delivery when combined with a CDN or a provider like Cloudflare R2
- No content edits needed – media URLs are rewritten automatically
- Works with the standard WordPress media library – uploads, editing, thumbnails and deletions behave as usual
Supported storage providers
- Amazon S3
- Cloudflare R2 – S3-compatible storage with no egress fees
- DigitalOcean Spaces
- Backblaze B2
- Wasabi
- Any S3-compatible storage – MinIO, OVHcloud Object Storage, Scaleway, Linode, Vultr, IBM Cloud Object Storage and more, using a custom endpoint
Features
- Automatic offloading – new uploads (including all generated image sizes) are sent to your cloud storage
- Bulk offload – move existing media from the plugin’s Media Overview page, with a live progress bar and a downloadable CSV of any files that failed
- WP-CLI support – offload large libraries with
wp smof offload, with--limitand--skip-failedoptions - Smart URL rewriting – media URLs are served from your bucket or custom CDN domain
- Local file retention policies – keep local copies, clean up local copies but keep the originals as a backup, or fully migrate to the cloud
- Mirror deletion – optionally delete files from cloud storage when you delete them in WordPress
- Custom path prefix – organise files inside your bucket
- File versioning – add a unique version to media paths to avoid stale CDN and browser caches
- Media Library tools – see each file’s offload status in the Media Library list, filter by offload status, and offload individual files with one click
- Thumbnail regeneration compatible – works with
wp media regenerateand the Regenerate Thumbnails plugin (not compatible with the Full Cloud Migration retention policy) - Image optimizer compatibility – works with the Modern Image Formats plugin, Imagify and EWWW Image Optimizer; optimized WebP and AVIF files are offloaded alongside the originals
- Credentials in
wp-config.php– define your storage details as constants instead of saving them in the database; the provider is detected automatically - Setup reminders – a clear admin notice tells administrators which details are still missing
- Clean, modern admin interface with connection testing
- Developer friendly – actions and filters to customise what gets offloaded and when
For developers
The plugin provides filters such as smof_should_offload_attachment, smof_local_deletion_rule and smof_object_acl, and actions such as smof_before_upload_to_cloud and smof_after_upload_to_cloud.
Example – skip offloading files larger than 5 MB:
add_filter( 'smof_should_offload_attachment', function ( $should_offload, $attachment_id ) {
$file = get_attached_file( $attachment_id );
if ( $file && filesize( $file ) > 5 * 1024 * 1024 ) {
return false;
}
return $should_offload;
}, 10, 2 );
Third-party library
Adoovy Media Offload uses the AWS SDK for PHP to interact with S3-compatible cloud storage. This powerful SDK provides an easy-to-use API for managing your cloud storage operations, including file uploads, downloads, and more. The SDK is maintained by Amazon Web Services, ensuring high compatibility and performance with S3 services.
For more information about the AWS SDK for PHP, visit:
https://aws.amazon.com/sdk-for-php/
Configuration
You can enter your cloud storage details on the plugin’s settings page, or define them as constants in wp-config.php (recommended for security). Constants always take priority over saved settings, and the matching fields are locked on the settings page.
Note: Domain and endpoint URLs will automatically be prefixed with https:// if you don’t include it, but we recommend always including the full URL for clarity.
Cloudflare R2 Configuration
define('SMOF_CLOUDFLARE_R2_KEY', 'your-access-key');
define('SMOF_CLOUDFLARE_R2_SECRET', 'your-secret-key');
define('SMOF_CLOUDFLARE_R2_BUCKET', 'your-bucket-name');
define('SMOF_CLOUDFLARE_R2_DOMAIN', 'your-domain-url');
define('SMOF_CLOUDFLARE_R2_ENDPOINT', 'your-endpoint-url');
DigitalOcean Spaces Configuration
define('SMOF_DOS_KEY', 'your-access-key');
define('SMOF_DOS_SECRET', 'your-secret-key');
define('SMOF_DOS_BUCKET', 'your-bucket-name');
define('SMOF_DOS_DOMAIN', 'your-domain-url');
define('SMOF_DOS_ENDPOINT', 'your-endpoint-url');
MinIO Configuration
Use this for any storage that supports the S3 API via a custom endpoint (e.g., MinIO, OVHcloud Object Storage, Scaleway, Linode, Vultr, IBM COS). Select this if your provider isn’t listed separately.
define('SMOF_MINIO_KEY', 'your-access-key');
define('SMOF_MINIO_SECRET', 'your-secret-key');
define('SMOF_MINIO_BUCKET', 'your-bucket-name');
define('SMOF_MINIO_DOMAIN', 'your-domain-url');
define('SMOF_MINIO_ENDPOINT', 'your-endpoint-url');
define('SMOF_MINIO_PATH_STYLE_ENDPOINT', false); // Optional. Set to true if your MinIO server requires path-style URLs (most self-hosted MinIO setups). Default is false.
define('SMOF_MINIO_REGION', 'your-bucket-region'); // Optional. Set your MinIO bucket region if needed. Default is 'us-east-1'.
Amazon S3 Configuration
define('SMOF_AWS_KEY', 'your-access-key');
define('SMOF_AWS_SECRET', 'your-secret-key');
define('SMOF_AWS_BUCKET', 'your-bucket-name');
define('SMOF_AWS_REGION', 'your-bucket-region');
define('SMOF_AWS_DOMAIN', 'your-domain-url');
Backblaze B2 Configuration
define('SMOF_BACKBLAZE_B2_KEY', 'your-application-key-id');
define('SMOF_BACKBLAZE_B2_SECRET', 'your-application-key');
define('SMOF_BACKBLAZE_B2_BUCKET', 'your-bucket-name');
define('SMOF_BACKBLAZE_B2_REGION', 'your-bucket-region');
define('SMOF_BACKBLAZE_B2_DOMAIN', 'your-domain-url');
define('SMOF_BACKBLAZE_B2_ENDPOINT', 'your-endpoint-url');
Wasabi Configuration
define('SMOF_WASABI_KEY', 'your-access-key');
define('SMOF_WASABI_SECRET', 'your-secret-key');
define('SMOF_WASABI_BUCKET', 'your-bucket-name');
define('SMOF_WASABI_REGION', 'your-bucket-region');
define('SMOF_WASABI_DOMAIN', 'your-domain-url');
Using wp-config.php
Storage details can be defined as constants instead of being saved in the database. Constants take priority over the settings page, and the provider is detected automatically when KEY, SECRET and BUCKET are defined. Name format: SMOF_<PROVIDER>_<FIELD>.
Provider names used in constants: AWS, CLOUDFLARE_R2, BACKBLAZE_B2, DOS (DigitalOcean Spaces), WASABI, MINIO. Fields: KEY, SECRET, BUCKET, ENDPOINT, REGION, DOMAIN.
Example (Cloudflare R2):
define('SMOF_CLOUDFLARE_R2_KEY', '...');
define('SMOF_CLOUDFLARE_R2_SECRET', '...');
define('SMOF_CLOUDFLARE_R2_ENDPOINT', 'https://<account>.r2.cloudflarestorage.com');
define('SMOF_CLOUDFLARE_R2_BUCKET', 'my-bucket');
define('SMOF_CLOUDFLARE_R2_DOMAIN', 'https://cdn.example.com');
Optional: define('SMOF_CLOUD_PROVIDER', 'cloudflare_r2'); to force a provider. Constants named ADVMO_* from the original plugin are mapped automatically. If required details are missing, an admin notice asks an administrator to complete them.
External Services
This plugin connects to the cloud storage service that you choose and configure. It sends your media files and related requests (upload, delete, list, connection test) directly from your server to that service, using the credentials you provide. No data is sent to the plugin author, and nothing is sent until you set up a provider.
Depending on your selection, data is exchanged with one of the following services:
- Amazon S3 – Terms | Privacy
- Cloudflare R2 – Terms | Privacy
- DigitalOcean Spaces – Terms | Privacy
- Backblaze B2 – Terms | Privacy
- Wasabi – Terms | Privacy
- Other S3-compatible services (MinIO, OVHcloud, Scaleway, Linode, Vultr, IBM COS, etc.) – the terms and privacy policy of the provider you configure.
Credits & License
Adoovy Media Offload, developed by Adoovy, is a GPL-licensed fork of “Advanced Media Offloader” by WP Fitter. It keeps the same features and behaviour, but all PHP namespaces, the bundled AWS SDK prefix, functions, constants, options, hooks, AJAX actions, script handles, CSS classes and the WP-CLI command use their own unique smof prefix, so it can run next to other plugins and themes (including the original plugin) without conflicts.
Licensed under GPL v2 or later: https://www.gnu.org/licenses/gpl-2.0.html
Installation
- Upload the plugin folder to
/wp-content/plugins/adoovy-media-offload/, or install it from the WordPress Plugins screen. - Activate the plugin through the Plugins menu.
- Open Adoovy Offload in the admin menu.
- Choose your cloud provider and enter your credentials on the settings page, or define them in
wp-config.php(see Configuration below). - Click Test Connection, then save your settings.
- Use the Media Overview page (or WP-CLI) to offload your existing media.
FAQ
-
Does this plugin support other cloud storage platforms?
-
Currently supports Amazon S3, Backblaze B2, Cloudflare R2, DigitalOcean Spaces, MinIO & Wasabi. Additional providers are on the roadmap based on user demand.
-
What happens to the media files already uploaded on my server?
-
Existing files remain untouched until you explicitly use the bulk offload feature. New uploads are automatically processed based on your settings.
-
How exactly does URL rewriting work?
-
The plugin hooks into WordPress core media functions using
wp_get_attachment_urland related filters. This ensures compatibility with themes, plugins, and core functions without modifying database URLs. -
Can I rollback if needed?
-
Files offloaded with “Retain Local Files” can be served locally by deactivating the plugin. For full cloud migrations, you’ll need to re-download media files if you want to revert.
-
How are image sizes and thumbnails handled?
-
All generated image sizes are offloaded alongside the original. URL rewriting works for all sizes and srcset attributes.
-
Will this work with page builders and media-heavy plugins?
-
Yes, since the plugin uses WordPress core hooks for URL rewriting, it’s compatible with Elementor, Beaver Builder, WooCommerce, and most other plugins that use standard WordPress media functions.
-
Does it support private files with access control?
-
The free version only supports publicly accessible files. Private files with authenticated access may be added in a future premium version.
-
What happens if I remove a media file from the WordPress Media Library?
-
With “Mirror Delete” enabled, corresponding cloud files are automatically removed. Otherwise, files remain in cloud storage, potentially creating orphaned objects.
-
How can I debug issues with file offloading?
-
The plugin logs errors to attachment metadata. Check the Media Overview page for detailed error reporting or enable WordPress debug logging for more information.
-
What’s the recommended bucket configuration?
-
For optimal performance:
1. Enable CORS configuration
2. Set appropriate public read permissions
3. Configure proper region (closest to your audience)
4. Consider using a CDN for global distributions -
How do I configure public access for my bucket?
-
By default, the plugin sets
public-readACL on uploaded objects. However, some providers don’t support ACLs, and AWS S3 has ACLs disabled by default on new buckets since April 2023. You should configure bucket-level public access using your provider’s bucket policies.If you encounter
AccessControlListNotSupportederrors or need to disable ACLs, add the following code to your theme’sfunctions.phpor a custom plugin:add_filter('smof_object_acl', '__return_false');
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Adoovy Media Offload” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “Adoovy Media Offload” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
4.5.0
- Fix: text domain now matches the plugin slug (adoovy-media-offload); output escaping, prepared SQL, translator comments, input sanitization and date handling updated to meet WordPress.org plugin guidelines.
-
New: footer shows version and a link to the developer (Adoovy).
-
New: complete admin redesign by Adoovy — new brand, logo and menu icon, hero header with provider status, pill navigation, card layout, toggle switches and refined buttons. All functionality unchanged.
4.4.2
- Added: provider auto-detection from wp-config.php constants and an admin notice asking for missing storage details.
- Added: one-time import of settings, per-attachment offload data and wp-config constants (ADVMO_*) from the original Advanced Media Offloader, so previously offloaded media keeps loading from the bucket.
4.4.1
- Fixed: Custom/intermediate image sizes in src attribute being replaced with the full-size URL when using page builders like Elementor
4.4.0
- Added: Imagify compatibility for WebP/AVIF offloading
- Added: EWWW Image Optimizer compatibility
4.3.2
- Fixed: Visual Composer compatibility – resolved PHP TypeError caused by strict type hints on admin_enqueue_scripts callbacks
4.3.1
- Added:
smof_object_aclfilter to customize or disable object-level ACL permissions
4.3.0
- Added: New visual badges in Media Library show offload status at a glance. Cloud icon for offloaded files, warning icon for failed uploads.
- Added: Visual “Deleting…” loading indicator with spinner in Media Library attachment modal when deleting offloaded media
- Added: Offload status filter dropdown in Media Library for quick filtering by offload state.
- Improved: Optimized cloud deletion performance using batched deleteObjects API (up to 1000 keys per request) for faster deletion of attachments with multiple sizes
- Fixed: MinIO “Use Path-Style Endpoint” now correctly respects boolean
wp-config.phpconstants (e.g.define('SMOF_MINIO_PATH_STYLE_ENDPOINT', true);).
4.2.3
- Fixed: TypeError when uploading non-image files (SVG, ZIP, PDF)
4.2.2
- Added: Compatibility with WordPress 6.9
- Added: Full Compatibility with Modern Image Formats
- Fixed: Minor changes and improvements
4.2.1
- Fix: Checkbox states for credential fields now properly persist when unchecked
- Fix: Deletion failure when WordPress year/month folders are disabled
4.2.0
- New: Added compatibility for thumbnail regeneration with WP-CLI
wp media regeneratecommand and the Regenerate Thumbnails plugin. Regenerated thumbnails now automatically offload to cloud storage. Note: This feature does not work with Full Cloud Migration retention policy. - New: Added the ability to configure cloud provider credentials through the WordPress admin settings page while maintaining backward compatibility with wp-config.php constants. Constants take priority and disable corresponding fields when defined.
- New: Added setting to toggle automatic cloud offloading for new uploads
- New: Added customizable Name field S3-compatible providers to identify specific storage services (e.g., MinIO, OVHcloud, Scaleway). Default is “MinIO” with backward compatibility for existing installations.
- Fix: Minor changes and improvements
4.1.1
- New: Added Backblaze B2 support – affordable S3-compatible cloud storage with predictable pricing
- Improved: Automatic URL normalization – Domain and endpoint URLs are now automatically prefixed with
https://if missing, eliminating common configuration errors
4.1.0
- New: Added
smof_cloud_providersfilter to allow adding, removing, or customizing the list of available cloud providers - New: Added Unique Filename Protection – UniqueFilenameObserver automatically prevents file overwrites when full cloud migration is enabled
- New: Added domain filters for developers to programmatically modify CDN/custom domains for each provider (
smof_aws_domain,smof_cloudflare_r2_domain,smof_dos_domain,smof_minio_domain,smof_wasabi_domain) - New: Added
smof_should_upload_original_imagefilter to control whether original images should be uploaded to cloud (default: true) - Fix: Original images are now correctly uploaded to and deleted from cloud storage alongside scaled versions
- Fix: Background processes that could get stuck now have proper recovery mechanisms
- Fix: Disabled
use_aws_shared_config_filesoption across all S3-compatible providers to prevent potential conflicts and security issues
4.0.3
- Fixed memory exhaustion and fatal errors when handling offloaded SVG files.
4.0.2
- Improved SVG support and fixed issues with Elementor SVG icons after offloading.
4.0.1
- feat: add smof_should_offload_attachment filter to conditionally skip offloading
4.0.0
- Added: WP CLI command
wp smof offloadfor bulk operations and automation - Added: Individual “Offload Now” button in attachment edit screen for on-demand offloading
- Added: Retry functionality for failed offloads with dedicated “Retry Offload” button
- Fixed: Admin notices from other plugins now properly disabled on Media Overview page
- Improved: Enhanced admin interface consistency across all plugin pages
3.3.5
- Fixed: Minor improvements and bug fixes
3.3.4
- Fixed: Minor improvements and bug fixes
- Updated: WordPress compatibility improvements
3.3.3
- Fixed: Use original file’s directory for sized image deletion, resolving an issue where thumbnails in older uploads weren’t being deleted properly
- Fixed: Corrected a bug in the mirror delete functionality ensuring cloud files are properly removed when local files are deleted
- Added: HTTPS protocol requirement notices for domain and endpoint URLs for improved security
- Refactored: Standardized plugin settings approach for better code maintainability
- Optimized: Improved bulk processing with direct SQL queries for better performance
- Fixed: Added proper nonce verification and capability checks to all AJAX endpoints for enhanced security
- Fixed: Preserved checkbox values during settings sanitization to prevent settings from being inadvertently reset
3.3.2
- Improved accessibility and consistency in admin interface
- Added RTL stylesheet and conditional loading for better localization support
- Fixed minor bugs and made improvements.
3.3.1
- Fixed minor bugs and made improvements.
3.3.0
- Added service container and dependency injection architecture
- Improved connection testing with better error handling
- Fixed bulk offload process to prevent stuck operations
- Enhanced UI with clearer cloud provider selection
- Improved documentation with detailed provider setup instructions
3.2.0
- Added support for Wasabi cloud storage
- Enhanced plugin performance and stability
- Fix minor bugs
3.1.0
- Fixed and optimized connection test button functionality
- Fixed minor bugs and made improvements.
3.0.0
- Introduced a new user interface (UI) and improved user experience (UX) for the settings page.
- Added functionality to offload and sync edited images with cloud storage.
- Improved bulk offloading to cloud storage by fixing various bugs.
- Implemented error logging for bulk offload operations.
- Added ability to download a CSV file with detailed logs for attachments that encountered errors during offloading.
- Enhanced overall security of the plugin.
- Fixed various issues related to bulk offload JavaScript functionality.
- Improved error handling and notifications for media attachments in the library.
- Refactored attachment deletion methods for better performance and reliability.
2.1.0
- Implemented php-scoper to isolate AWS PHP SDK namespaces, preventing conflicts with other plugins using different versions of the same packages.
- Fixed minor bugs and made improvements.
2.0.3
- Fixed minor bugs and made improvements.
2.0.2
- Display offloaded version of images in post content when already offloaded to improve loading times and reduce bandwidth usage.
- Fixed the srcset attribute not displaying for images when object versioning is enabled.
2.0.1
- Fixed minor bugs and made improvements.
2.0.0
- Refactored the Adoovy Media Offload codebase.
- Added new action hooks for custom actions before and after critical operations.
- Fixed compatibility issue with the Performance Lab WordPress plugin.
- Fixed a bug in bulk offloading media files.
- Added support for MinIO path-style endpoint configuration using the SMOF_MINIO_PATH_STYLE_ENDPOINT constant.
- Fixed minor bugs and made improvements.
1.6.0
- Refactored the code base to improve maintainability and readability, resulting in enhanced performance across the plugin.
- Resolved an issue where the bulk offload process would become unresponsive
- Added a button to cancel the bulk offload process, providing users with greater control during file transfers.
1.5.2
- Fix a minor bug related to the path of existing media files when deleting local files.
1.5.1
- Fix minor bugs to improve bulk offload process
1.5.0
- Added support for Amazon S3 cloud storage
- Enhanced plugin performance and stability
- Fix minor bugs
1.4.5
- Fix minor bugs with Min.io
1.4.4
- New Feature: Custom Path Prefix for Cloud Storage
- Fix minor bugs
1.4.3
- Add Version to Bucket Path: Automatically add unique timestamps to your media file paths to ensure the latest versions are always delivered
- Add Mirror Delete: Automatically delete local files after successful upload to Cloud Storage.
- Improve Settings UI: Enhanced the user interface of the settings page.
1.4.2
- Added ‘Sync Local and Cloud Deletions’ feature to automatically remove media from cloud storage when deleted locally.
- Enhanced WooCommerce compatibility: Added support for WooCommerce-specific image sizes and optimized handling of product images.
1.4.1
- Fix minor bugs related to Bulk offloading the existing media files
1.4.0
- Added bulk offload feature for media files (50 per batch in free version)
- Fixed subdir path issue for non-image files
- UI Improvements
- Fixed minor bugs
1.3.0
- UI Improvements
- Fixed minor bugs
1.2.0
- Added MinIO as a new cloud storage provider
- Introduced an option to choose if local files should be deleted after offloading to cloud storage
- Implemented UI improvements for the plugin settings page
- Added Offload status to Attachment details section in Media Library
- Fixed minor bugs
1.1.0
- Improved the code base to fix some issues
- Added support for DigitalOcean Spaces
1.0.0
- Initial release.
