swiftplugins

Swift Offload is a powerful WordPress plugin that offloads your media library to cloud storage and delivers content through a CDN for improved performance and reduced server load.
<h4>Why Use Swift Offload?</h4>
<ul>
<li>Reduce Server Storage – Free up disk space by storing media in the cloud</li>
<li>Faster Page Loads – Serve media through CloudFront CDN</li>
<li>Scalable – Handle unlimited media without server constraints</li>
<li>Cost Effective – Use affordable storage providers like Wasabi</li>
</ul>
<h4>Key Features</h4>
<ul>
<li>Multiple Storage Providers – Amazon S3, Wasabi, DigitalOcean Spaces, MinIO</li>
<li>CloudFront CDN – Integrated CDN support with signed URLs for private content</li>
<li>Bulk Offload – Background processing to offload existing media</li>
<li>Auto Offload – Automatically offload new uploads</li>
<li>URL Rewriting – Seamlessly rewrite media URLs in your content</li>
<li>Image Optimization – WebP conversion and compression</li>
<li>Local File Removal – Option to delete local copies after offload</li>
<li>WP-CLI Support – Automate operations via command line</li>
<li>Modern Admin UI – Clean, intuitive React-based interface</li>
</ul>
<h4>Supported Storage Providers</h4>
<ul>
<li>Amazon S3 – The industry standard for cloud storage</li>
<li>Wasabi – S3-compatible with no egress fees</li>
<li>DigitalOcean Spaces – Simple, affordable object storage</li>
<li>MinIO – Self-hosted S3-compatible storage</li>
</ul>
<h4>Privacy & Data</h4>
Swift Offload respects your privacy:
<ul>
<li>Does NOT collect any user data without consent</li>
<li>Does NOT send data to external servers (except your configured cloud storage)</li>
<li>Does NOT track users or collect analytics</li>
<li>Stores cloud storage credentials securely in your WordPress database</li>
<li>All media operations happen on your server</li>
</ul>
<h4>Third-Party Libraries</h4>
This plugin uses the following open-source libraries:
<ul>
<li>React – MIT License</li>
<li>Tailwind CSS – MIT License</li>
<li>Radix UI – MIT License</li>
<li>TanStack Query – MIT License</li>
<li>Lucide Icons – ISC License</li>
<li>Shadcn/ui – MIT License</li>
</ul>
<h4>Source Code</h4>
The original source code for all compiled assets is included in this plugin:
<ul>
<li>React Admin App: <code>app/src/</code> directory</li>
<li>SCSS Styles: <code>dev/scss/</code> directory</li>
<li>JavaScript: <code>dev/js/</code> directory</li>
</ul>
Build tools used: Vite, TypeScript, PostCSS, Sass
To build from source: 
 cd app && npm install && npm run build
<h3>External Services</h3>
This plugin connects to external services only when explicitly configured by you:
<h4>Cloud Storage Providers (User Configured)</h4>
When you configure cloud storage, the plugin connects to your chosen provider to upload and manage media files.
<ul>
<li>Supported Providers: Amazon S3, Wasabi, DigitalOcean Spaces, MinIO, CloudFront</li>
<li>Data Sent: Your media files (only when you initiate offload operations)</li>
<li>When: Only when you configure storage and perform offload/sync operations</li>
<li>Your Responsibility: You must review and agree to the terms of service of your chosen storage provider:
<ul>
<li>Amazon S3: <a href="https://aws.amazon.com/service-terms/" rel="nofollow ugc">AWS Terms</a></li>
<li>Wasabi: <a href="https://wasabi.com/legal/" rel="nofollow ugc">Wasabi Terms</a></li>
<li>DigitalOcean: <a href="https://www.digitalocean.com/legal/terms-of-service-agreement" rel="nofollow ugc">DO Terms</a></li>
</ul>
</li>
</ul>
<h4>Deactivation Feedback (Optional)</h4>
When deactivating, you may optionally provide feedback to help us improve.
<ul>
<li>Service Provider: Swift Plugins</li>
<li>Data Sent: Feedback reason, comments (only if you choose to submit)</li>
<li>When: Only when you voluntarily submit the feedback form</li>
<li>Terms of Use: <a href="https://swiftplugins.pro/terms-of-service/" rel="nofollow ugc">Terms</a></li>
<li>Privacy Policy: <a href="https://swiftplugins.pro/privacy-policy/" rel="nofollow ugc">Privacy</a></li>
</ul>

Swift Offload

Offload WordPress media to Amazon S3, Wasabi, DigitalOcean Spaces, or MinIO. Serve files via CloudFront CDN for faster delivery.

Gerald Drißner

Voffload for Cloudflare Stream moves the heavy lifting of video hosting and playback off your own server and onto Cloudflare Stream. You pick existing video attachments in your WordPress Media Library, the plugin uploads them to Cloudflare Stream, and your visitors then watch them through Cloudflare’s adaptive‑bitrate player instead of downloading large files from your origin.
This is useful if self‑hosted videos are slowing your site down, eating bandwidth, or stressing your host. Cloudflare Stream handles transcoding, multiple quality levels, and global delivery for you.
This plugin is an independent project. It is not affiliated with, endorsed by, or sponsored by Cloudflare, Inc. “Cloudflare” and “Cloudflare Stream” are trademarks of Cloudflare, Inc., used here only to describe compatibility.
<h4>What it does</h4>
<ul>
<li>Lists the video attachments already in your Media Library and shows their Cloudflare Stream status (Not uploaded / Processing / Ready / Error).</li>
<li>Uploads selected videos to Cloudflare Stream. It first asks Cloudflare to fetch the public file URL (“URL copy”). If Cloudflare cannot reach that URL (for example because of hotlink protection, a firewall rule, or Automatic Platform Optimization), it automatically falls back to a direct upload from your server for files under 200 MB.</li>
<li>Stores each video’s Cloudflare Stream UID and processing status on the attachment.</li>
<li>Can non-destructively sync existing Cloudflare Stream videos back to matching WordPress video attachments when metadata or a unique exact title/filename match identifies the local attachment.</li>
<li>Can delete selected Cloudflare Stream videos from the plugin dashboard, individually or in bulk, while keeping the original WordPress media attachments.</li>
<li>Tracks “processing” videos with a background check (WP‑Cron) that runs every 10 minutes — but only while at least one video is still processing. When everything is ready, the background check stops on its own, so the plugin does not make unnecessary calls.</li>
<li>Automatically replaces your local video output on the frontend with the Cloudflare Stream player once the matching Stream video is ready (this is optional and can be turned off — see “Automatic replacement” below).</li>
<li>Provides a shortcode for manual placement of the player (see the “Shortcode” section below for the exact tag and options).</li>
<li>Includes a non‑destructive Connection test that checks your token, account access, and playback settings without uploading anything.</li>
<li>Uses a structured dashboard with setup status, workflow descriptions, action guidance, and a small version/copyright/license footer.</li>
<li>Never deletes your local video files. Deleting a Stream copy from Cloudflare only clears the plugin’s local Stream metadata; removing local files is intentionally left to you.</li>
</ul>
<h4>Do I need a paid Cloudflare account?</h4>
You need a Cloudflare account and an active Cloudflare Stream subscription. A few clarifications, because this is a common point of confusion:
<ul>
<li>Cloudflare Stream is a separate, usage‑based product. As of 2026 it is billed at roughly $5 per 1,000 minutes of video stored per month and $1 per 1,000 minutes delivered. Encoding and ingest are free, and there are no per‑GB egress fees.</li>
<li>You do not need a Cloudflare Pro plan specifically, and Stream does not require the Workers Paid plan. A free Cloudflare account works, as long as you have added a Stream subscription to it.</li>
<li>If you are on a Pro or Business plan, Cloudflare includes a small monthly allowance (around 100 minutes of storage and 10,000 minutes of delivery) on top.</li>
</ul>
Always confirm current pricing on Cloudflare’s own pricing page, as it can change.
<h3>Dashboard guide</h3>
The plugin dashboard is available under Media → Cloudflare Stream.
<ul>
<li>The top overview explains the three-step workflow: configure Cloudflare, upload or reconnect videos, then serve and maintain the Stream copies.</li>
<li>The setup status pills show whether the Account ID, API token, and Customer Code are present before you run actions that need them.</li>
<li>The Video Library table lists WordPress video attachments and shows their local file link, Stream status, Stream UID, and shortcode.</li>
<li>Upload selected creates a Cloudflare Stream copy for selected local WordPress videos. The WordPress attachment remains in the Media Library.</li>
<li>Refresh selected status reads the current processing state from Cloudflare. If no local UID is saved, the plugin first attempts a safe reconnect.</li>
<li>Reconnect selected from Cloudflare finds existing Stream videos for selected local attachments by stored metadata first and then by exact unique title/filename matches.</li>
<li>Delete from Cloudflare deletes the remote Stream asset after confirmation and clears only local Stream metadata. It does not delete the WordPress attachment.</li>
<li>The manual UID fallback is for rare cases where automatic matching is unsafe because Cloudflare metadata is missing or multiple possible matches exist.</li>
</ul>
<h3>Compatibility</h3>
<ul>
<li>Requires WordPress 6.5 or newer.</li>
<li>Tested up to WordPress 7.0.</li>
<li>Requires PHP 8.1 or newer. PHP 8.3 or newer is recommended for current WordPress installations.</li>
<li>Tested with modern PHP 8.x environments, including PHP 8.5.</li>
</ul>
<h3>Getting your Cloudflare details</h3>
You need three pieces of information from your Cloudflare account.
1. Account ID 
Log in to the Cloudflare dashboard at https://dash.cloudflare.com/ and open the Stream product (or any account page). Your Account ID is shown in the URL and on the account/overview pages. It is a 32‑character hexadecimal string.
2. API Token (with Stream permission) 
Create a scoped token so the plugin can upload and check status. Do not use the Global API Key.
<ol>
<li>In the Cloudflare dashboard, go to Manage Account → API Tokens or My Profile → API Tokens and choose Create Token → Create Custom Token. Direct link: https://dash.cloudflare.com/profile/api-tokens</li>
<li>Under Permissions, add Account → Stream → Edit. Some Cloudflare screens use the newer label Account → Stream → Write; that is the equivalent write permission. Uploads, status updates, sync/reconnect, and remote deletion require Edit/Write. Read-only tokens can verify access but cannot upload or delete videos.</li>
<li>Under Account Resources, scope the token to the specific Cloudflare account that owns the Stream library.</li>
<li>Do not add unnecessary permissions. This plugin does not need DNS, Zone, Workers, Cache Purge, or Global API Key permissions.</li>
<li>(Recommended) Set an expiration and, if your server has a static IP, restrict the token to that IP.</li>
<li>Click Continue to summary → Create Token. Copy the token immediately — Cloudflare shows it only once and you cannot retrieve it later.</li>
</ol>
For better security you can define the token in your <code>wp-config.php</code> instead of saving it in the database:
<pre><code>define( 'VOFFLOADCFS_API_TOKEN', 'xxx' );
</code></pre>
When this constant is set, the plugin uses it and never stores the token in the WordPress database (so it stays out of database backups).
3. Customer Code 
This is the code in your Stream playback URLs, of the form <code>customer-CODE.cloudflarestream.com</code>. The plugin needs it to build the official Cloudflare Stream iframe URL. To find it, open Cloudflare Dashboard → Stream → Videos, open any uploaded video, and copy the embed/iframe code. The iframe <code>src</code> contains <code>customer-CODE.cloudflarestream.com</code>. You may paste the bare code, the full customer subdomain, the iframe URL, or the full iframe snippet; the plugin extracts and stores only the code.
<h3>Automatic replacement (serve from Cloudflare Stream when available)</h3>
In Media → Cloudflare Stream → Settings you control when ready videos are automatically served from Cloudflare instead of from your server. There are independent checkboxes so you can enable exactly what you want:
<ul>
<li>Automatically replace Gutenberg video blocks — replaces the core/video block on the frontend when the linked attachment has a Stream UID.</li>
<li>Automatically replace WordPress [video] shortcodes — replaces the built‑in <code>[video]</code> shortcode output.</li>
<li>Automatically replace local video HTML and video‑file links — also catches classic‑editor <code><video></code> tags, video blocks that have no attachment ID, and direct links to local video files.</li>
</ul>
Automatic replacement happens only for videos that already have a saved Cloudflare Stream UID and are marked ready. While Cloudflare is still processing a video, the local WordPress video output remains in place. If you turn every automatic option off, nothing on your frontend changes until you place a shortcode yourself.
<h3>Shortcode</h3>
Use the shortcode to place a Cloudflare Stream player manually, for example inside a post, page, or widget.
By WordPress attachment ID (the ID shown in the Media → Cloudflare Stream table):
<pre><code>[voffloadcfs_video id="123"]
</code></pre>
By Cloudflare Stream UID directly:
<pre><code>[voffloadcfs_video uid="VIDEO_UID"]
</code></pre>
Optional attributes:
<ul>
<li><code>title</code> — accessible title for the player iframe.</li>
<li><code>aspect</code> — aspect ratio as <code>width/height</code> (default <code>16/9</code>). Example: <code>aspect="4/3"</code>.</li>
</ul>
Example with options:
<pre><code>[voffloadcfs_video id="123" title="My talk" aspect="16/9"]
</code></pre>
The shortcode requires the Customer Code setting to be filled in, because that is what builds the official Cloudflare Stream iframe URL. If a logged‑in editor views a shortcode that cannot render (missing UID, wrong ID, missing Customer Code), the plugin shows a short admin‑only notice explaining why; normal visitors simply see nothing.
<h3>External services</h3>
This plugin connects to Cloudflare Stream, a third‑party service operated by Cloudflare, Inc., because that is the service it exists to integrate with.
What is sent, and when:
<ul>
<li>When you upload a video: the plugin sends the video (or the public URL of the video so Cloudflare can fetch it), the attachment title, the attachment ID, and your site URL to the Cloudflare API. This happens only when you choose to upload a video.</li>
<li>When you check status, run the connection test, reconnect selected videos, or sync existing Stream videos: the plugin sends your Account ID and API token (as an authorization header) to the Cloudflare API to read video status, verify the token, list Stream video metadata, search Stream videos by name for a selected local attachment, or verify a manually entered Stream UID. The connection test, reconnect, and sync do not upload any video.</li>
<li>When you delete a Stream video from the plugin dashboard: the plugin sends your Account ID, API token, and the selected Cloudflare Stream video UID to the Cloudflare API. Cloudflare deletes the remote Stream video and its copies. The original WordPress media attachment is not deleted.</li>
<li>On the frontend: when a video is served from Stream, the visitor’s browser loads the Cloudflare Stream player iframe from <code>customer-CODE.cloudflarestream.com</code>, so the visitor’s browser communicates directly with Cloudflare.</li>
</ul>
Cloudflare API endpoint: https://api.cloudflare.com/ 
Cloudflare terms of service: https://www.cloudflare.com/terms/ 
Cloudflare privacy policy: https://www.cloudflare.com/privacypolicy/
No data is sent anywhere else, and the plugin does not send analytics about your site to the plugin author.

Voffload for Cloudflare Stream

Upload your WordPress video attachments to Cloudflare Stream and serve them through the fast Cloudflare Stream player from the Media Library.

Swift Offload vs Voffload for Cloudflare Stream