by
Pablo Di Loreto
1 (0 reviews)
DiluxOne Offload – Media Storage
Move your media to cloud object storage and serve it from there. Replaces /uploads/ transparently, with no URL rewriting.
DiluxOne Offload ranks #59,759 among WordPress.org plugins with 1+ active installations, is #4,762 of 6,651 in the Media category, a 1/5 rating from 0 reviews, and was last updated Oct 8, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v2.1.0
Current Version v2.1.0
Updated 4 weeks ago
Last Update on 08 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
#4,762 of 6,651 in Media
Actively maintained
Rank
#59,759
—
No change
Active Installs
1+
—
No change
KW Avg Position
130
0.3 worse
Downloads
316
+3 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
46,822
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 7 more installs to reach 10+
Rank Changes
Current
#59,759
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 2.1.0
- Last Updated
- Oct 08, 2026
- Requires WP
- 5.1+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- Pablo Di Loreto
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
Jetpack – AI Agents & MCP, Security, Backup & Analytics
3M+ installs
#17
Advanced Custom Fields (ACF®)
2M+ installs
#28
Image Optimizer – Compress Images and Convert to WebP or AVIF
1M+ installs
#58
EWWW Image Optimizer
1M+ installs
#60
Regenerate Thumbnails
1M+ installs
#64
Smush – Image Optimization, Compression, Lazy Load, WebP & CDN
1M+ installs
#65
Imagify Image Optimization: Optimize Images | Compress & Convert to WebP/AVIF
900K+ installs
#68
Smart Slider 3
800K+ installs
#78
Frequently Asked Questions
Common questions about DiluxOne Offload – Media Storage
No. The stream wrapper intercepts filesystem calls transparently — your post content, the wp_posts table, and the wp_postmeta table are never rewritten.
The plugin monitors connection health. While the cloud is unreachable, a new upload fails with WordPress's own "could not be moved" error and nothing is saved anywhere, so you never end up with a file that looks uploaded but isn't. A banner on the plugin's admin pages explains the failure. Files already in the cloud keep being served from the storage account URL. The plugin re-checks the connection at most every five minutes and uploads resume on their own once it is back.
Not for itself: it has no cache, log or data files on disk; everything it needs lives in the WordPress options table and its own database table. Your media is written by WordPress core through the plugin's stream wrapper to the cloud, passing through a temporary file in the PHP temp directory that is deleted right after the upload. The one operation that writes to the server is Sync & Offloading → Disconnect from Cloud. It copies your media back from the container to the exact uploads-directory paths WordPress has on record (resolved at runtime with wp_upload_dir()), so the Media Library works again without the plugin. It restores only what sits under the uploads/ prefix of your own container, never a script or executable file name (PHP, JavaScript, HTML, shell or Windows executables) whatever put it there, and it runs only when you click it.
Before the first sync, Sync & Offloading › Sync looks under this site's folder in it (uploads/, or uploads/sites/<id>/ for a site of a network). If something is there, from an earlier install or a staging copy, it says how many files and how much, and lets you continue with them, empty that folder (you type the container's or bucket's name to confirm) or connect another one. Emptying deletes only this site's folder, never anything else in the container or bucket, and only before the first sync.
Yes, including from Azure to an S3-compatible service or back. Remove the current provider configuration from the admin, enter the new account, container or bucket, run a full resync, and the plugin starts serving from the new location. No URL rewriting required.
Yes. Because the stream wrapper operates at the filesystem layer, any plugin that reads or writes files under /uploads/ using standard PHP functions works unchanged.
Only if you explicitly opt in. After a successful sync you can click Delete Local Files in Sync & Offloading › Offloading. Until you do that, files are kept in both locations. A file that is empty (0 bytes) when the sync scans it is skipped: it is neither uploaded nor tracked, so Delete Local Files leaves it alone.
Yes, while offloading is active: the stream wrapper turns the deletion into a delete on your container, thumbnails included. If you have synced but not yet enabled offloading, WordPress deletes only the local copy; the copy already in your container is not removed automatically.
Deleting the plugin from the Plugins screen removes everything it created in your database: its options (all prefixed diluxone_offload_), its transients and its file-tracking table (diluxone_offload_files, with your table prefix) — on every site of a network. Deactivating alone keeps all of that, so you can deactivate and reactivate without losing your configuration. Your media files are never touched by uninstalling: whatever is in /wp-content/uploads/ stays there, and whatever is in your container stays in your container. The only thing uninstalling cancels in the storage is an S3 multipart upload the sync left unfinished, which could no longer be completed and would keep being billed. If offloading was active and local copies had been deleted, download them first with Sync & Offloading → Disconnect from Cloud, otherwise WordPress will be pointing at files that are no longer on the server.
Go to DiluxOne Offload → Settings → Enable detailed debug logging. Logs are written to the standard PHP error_log destination. Disable it in production unless you are actively troubleshooting — it may impact performance. With that setting off and WP_DEBUG off, the plugin writes nothing to the PHP error log at all, at any level. With WP_DEBUG on it writes errors and warnings; the setting adds the rest.
