內容簡介
OmniOffloader 是一款多雲端媒體卸載與 CDN 外掛，能有效提升網站速度並釋放伺服器空間。它將媒體檔案移至雲端儲存，並透過快速的 CDN 提供服務，讓網站載入更迅速，使用者體驗更佳。
【主要功能】
• 自動卸載新上傳的媒體檔案至雲端
• 支援多種雲端儲存服務，如 Amazon S3 和 Cloudflare R2
• 從 CDN 提供媒體檔案，減少伺服器負擔
• 可選擇保留伺服器上的檔案或全部移至雲端
• 提供「Bring Back」功能，輕鬆將媒體檔案下載回伺服器
• 媒體庫中顯示卸載狀態與操作按鈕
外掛標籤
開發者團隊
② 後台搜尋「OmniOffloader — Multi-Cloud Media Offload & CDN」→ 直接安裝（推薦）
原文外掛簡介
Is your site slow, or your hosting disk almost full? Your media library is usually the reason.
Images, videos and files take up most of a WordPress site’s disk space, and every image a visitor loads comes from your server. OmniOffloader moves your media to cloud storage like Amazon S3 or Cloudflare R2 and serves it from a fast CDN. Your pages load quicker, your server has less work to do, and you get your disk space back.
You don’t have to change anything in your posts. Your images keep working everywhere: in posts, pages, page builders and galleries. OmniOffloader simply loads them from the cloud instead of your server.
Changed your mind? Bring Back downloads your media to your server again, one file or the whole library, and everything loads from your server like before. Nothing is locked in.
Documentation: setup guides for every provider, every feature and WP-CLI at omnioffloader.vercel.app.
See it in action
OmniOffloader in 2 minutes:
The full walkthrough, step by step: install, connect a bucket, serve from your CDN, offload your library, the Media Library, Bring Back and more:
Make your site faster with a CDN
When your media lives on your server, every visitor downloads every image from that one server, however far away they are. With OmniOffloader, your images, videos and files load from a CDN instead:
Closer to your visitors. A CDN keeps copies of your media in data centers around the world, so each visitor gets them from a nearby location. Pages load faster, especially for visitors far from your server.
Less work for your server. Your server no longer sends every image, so it has more power left for your pages, your shop and your admin screens, even during traffic spikes.
Lower bandwidth costs. Media traffic goes through the CDN instead of your hosting plan’s bandwidth.
Better page speed scores. Faster-loading images help your Core Web Vitals, such as Largest Contentful Paint (LCP), which tools like Google PageSpeed Insights measure.
Fewer stale files. Turn on object versioning and every changed file gets a new address, so the CDN never shows an old copy.
Use your own domain (for example media.yoursite.com) with Cloudflare, Amazon CloudFront, BunnyCDN or your storage provider’s built-in CDN. Your visitors only see your brand.
Works with these cloud storage providers
Amazon S3
Cloudflare R2
DigitalOcean Spaces
Backblaze B2
Wasabi
Any other S3-compatible storage, such as MinIO, Storj, OVHcloud, Linode or Scaleway. You enter the address and region your provider gives you, and you can even give it your own name.
What you can do
Offload new uploads automatically. Every new image is copied to the cloud in the background, with all its sizes. You keep working; the upload screen never waits.
Offload the media you already have. Move your whole library, or just a part of it (10, 50, 100 items or any number), with a progress bar and a Cancel button.
Serve media from your CDN. Your images load from your own domain or CDN instead of your server. Not ready yet? Offload now, keep loading media from your server, and switch to the CDN later with one click.
Choose what stays on your server. Keep everything (safest), remove only the extra image sizes WordPress creates, or move everything to the cloud to free the most space.
Change your mind later. Picked a different option for what stays on your server? Apply it to media you already offloaded from the Tools screen. Every file is checked in the cloud before anything is deleted.
Bring Back. Download media from the cloud to your server again, one file or all of it. It first checks you have enough disk space. Your cloud copy is kept unless you choose to delete it.
See everything in the Media Library. A status column, badges, offload and Bring Back buttons, bulk actions, and filters for offloaded, local and failed media.
Fix problems in one place. The Tools screen lists any media that failed to offload or restore, with the reason, and a button to try the failed offloads again.
Keep the cloud tidy. When you delete media in WordPress, its cloud copy is deleted too (Mirror Delete, on by default for new sites).
Organize your bucket. Store your files in a folder of your choice, and add a version number to file names so your CDN never shows an old copy. Changed the folder? Move your existing media into the new one from the Tools screen.
Choose the transfer speed. Move 1, 3 or 6 files at the same time, or your own number up to 10. Pick a gentle speed on small hosting plans and a fast one on bigger servers.
Keep your keys out of the database. Put your access keys in wp-config.php instead, and the settings screen locks those fields.
Use WP-CLI if you like the terminal. Offload, restore, check and repair your media from the command line, much faster on a VPS. See the FAQ below.
Built for large sites
OmniOffloader works on big sites with tens of thousands of media items. The first offload of a large library takes a while, because every existing file has to be copied to the cloud once. After that, there’s nothing more to do: new uploads are offloaded automatically as you add them. To make that first run easy:
Runs for hours without you. Start a big offload from WP-CLI in the background, close your terminal, and check its progress, speed and time left anytime with wp omnioffloader status.
Up to 64 files at the same time. On a VPS or dedicated server, --concurrency moves many files at once, so big libraries finish much sooner.
Picks up where it stopped. Stop a job, or lose the connection, and run it again: media already done is skipped.
Checks the result. wp omnioffloader verify confirms every file is really in your cloud storage and fixes anything missing.
Failed items never hold up the rest. A broken file is reported and skipped, and you can retry all failed items later with one click.
Built for every kind of hosting
OmniOffloader runs just as well on a small shared hosting plan as on a big server.
Light on your server. Jobs run quietly in the background in small steps, and use little memory.
You choose the pace. Choose Low on a small shared plan, Balanced (the default) for most sites, or Fast on a VPS or dedicated server.
Large files are no problem. Videos and other files over 64 MB are uploaded in parts, so a dropped connection only costs one part. Files over 5 GB work too.
No stuck jobs. If one file can’t be moved, it is reported and the job carries on. If the connection to your storage breaks, the job stops and tells you why.
Works on strict hosts. Some hosts block the background requests WordPress uses. Then the open admin page keeps the job going instead.
Works with caching. Progress stays live with LiteSpeed Cache, Breeze, Redis and Memcached.
Safe by design
A file is only deleted from your server after its cloud copy is confirmed.
A file is only deleted from the cloud after Bring Back has confirmed it is back on your server, and only if you turned that option on.
Restored files never end up half-written, and never outside your uploads folder.
Only one big job runs at a time, so two jobs never work on the same files.
Only administrators can move media between your server and the cloud. Other users upload and delete their own media as usual.
Your access keys are never shown in the browser or written to logs.
Staging and local copies can’t touch your live site’s media. A copy of your site is recognised automatically and never uploads to or deletes from your cloud storage (Safe mode).
Several sites can share one bucket, each in its own folder. A site never touches a folder another site already uses.
Why move media to the cloud?
Free up disk space. Cloud storage costs much less than hosting disk space.
Smaller backups. A site without gigabytes of uploads is much quicker to back up and move.
Cheaper hosting. With media in the cloud, a smaller hosting plan is often enough.
No lock-in. Bring Back reverses everything whenever you want.
Who is it for?
Large sites with tens of thousands of images and files.
Bloggers and news sites with years of images in the Media Library.
WooCommerce stores with many product photos.
Photographers, portfolios and agencies with large, high-quality images.
Course, video and download sites that store big files.
Agencies and developers who manage many sites, including several sites sharing one bucket.
Anyone on shared hosting who is running out of disk space.
For developers
Hooks, a REST API (omnioffloader/v1) and WP-CLI (wp omnioffloader) are available.
Filters: omnioffloader_cloud_providers, omnioffloader_object_acl, omnioffloader_attachment_key, omnioffloader_attachment_delete_keys, omnioffloader_should_offload_attachment, omnioffloader_use_async_upload, omnioffloader_should_apply_retention, omnioffloader_media_block_names, omnioffloader_log_provider_errors, omnioffloader_multipart_threshold, omnioffloader_transfer_concurrency, omnioffloader_bulk_failure_limit, omnioffloader_free_disk_space, omnioffloader_cpanel_quota_file, omnioffloader_check_folder_claim.
Actions: omnioffloader_before_offload, omnioffloader_after_offload, omnioffloader_before_restore, omnioffloader_after_restore, omnioffloader_transfer_heartbeat.
Full reference with examples: Hooks and WP-CLI.
Licensing note
This plugin includes the AWS SDK for PHP (Apache-2.0). It is compatible with GPLv3, which this plugin’s “GPL-2.0-or-later” license covers.
External services
This plugin connects to the cloud storage provider you choose in its settings. Nothing is sent until you enter that provider’s details, and it only connects to that provider.
What is sent, and when:
Uploads: your media files (the original and every image size) and their file paths, when media is offloaded: automatically when you upload, or when you use Offload, the Media Library or WP-CLI.
Downloads: your files come back from the cloud when you use Bring Back, or switch to a retention policy that keeps more files on your server.
Deletes: files are deleted from your bucket when you delete media with Mirror Delete on, or bring media back with “delete from cloud” on.
Test Connection: one request to check your bucket can be reached.
Every request is signed with the access key you entered; your secret key itself is never sent. Visitors then load your offloaded files from the storage or CDN address you set.
Depending on the provider you choose:
Amazon S3 (Amazon Web Services): Service Terms, Privacy Notice
Cloudflare R2 (Cloudflare): Terms, Privacy Policy
DigitalOcean Spaces (DigitalOcean): Terms of Service, Privacy Policy
Backblaze B2 (Backblaze): Terms of Service, Privacy Policy
Wasabi (Wasabi Technologies): Customer Agreement, Privacy Policy
Any S3-compatible storage: the service at the address you enter; its own terms and privacy policy apply.
Usage insights (Appsero, only if you allow it): an admin notice asks an administrator whether to share usage data, using the Appsero SDK. Nothing is collected by default.
If you click “No thanks”: only an anonymous note that sharing was declined is sent (the project ID and a one-way hash of your site address).
If you click “Allow”: about once a week, a report is sent to api.appsero.com with your site address and name, the admin email, the first administrator’s first and last name, server and WordPress details (PHP, MySQL and WordPress versions, memory limit, language, multisite, theme), user counts, the number and list of active plugins, the server’s IP address and the plugin version. To find the server’s public IP address, the SDK first sends a request to icanhazip.com, which sees only that request (Privacy Policy).
Never sent: your media, file names or storage keys.
Stop anytime: click “Stop sharing usage data” under the plugin on the Plugins screen.
Deactivation feedback: when you deactivate the plugin, an optional form asks why. Submitting it sends the same details as the weekly report, plus your answer. “Skip & Deactivate” sends nothing.
Appsero Privacy Policy
