Hippius Media Offloader lets you migrate your WordPress media library to Hippius \u2014 a distributed cloud storage platform where every file is encrypted, replicated across an independent network, and verifiable on-chain.<\/p>\n\n
Files are stored on Arion, Hippius's own distributed storage engine. Your media is split into 30 shards (10 data + 20 parity) using Reed-Solomon erasure coding, then placed across the network with the CRUSH algorithm. Up to 20 nodes can fail simultaneously and your files still rebuild perfectly.<\/p>\n\n
The plugin communicates with Hippius through the S3-compatible API \u2014 the same API you'd use to talk to AWS S3. No code changes, no proprietary SDK, no IPFS configuration.<\/p>\n\n
What this plugin does<\/strong><\/p>\n\n What this plugin does not do<\/strong><\/p>\n\n System requirements<\/strong><\/p>\n\n What you'll need from Hippius<\/strong><\/p>\n\n Important.<\/strong> Keep your Secret Access Key<\/strong> safe. It is shown only once at creation and cannot be retrieved later. If you lose it, you'll need to generate a new key pair.<\/p>\n\n Before configuring the plugin, you need to create your Hippius account and generate your S3 credentials. This takes about 2 minutes.<\/p>\n\n Step 1 \u2014 Create your Hippius account<\/strong><\/p>\n\n Note.<\/strong> No wallet, no seed phrase, no browser extension required. Just OAuth.<\/p>\n\n Step 2 \u2014 Add credits<\/strong><\/p>\n\n Credits are consumed as the plugin stores and serves your media. 1 credit = $1 USD.<\/p>\n\n Step 3 \u2014 Create your S3 credentials<\/strong><\/p>\n\n Critical.<\/strong> Your Secret Key is shown only once. Copy it immediately to a password manager. It cannot be recovered if lost.<\/p>\n\n Step 4 \u2014 Create the bucket (manual)<\/strong><\/p>\n\n The plugin does not automatically create buckets. You need to create your media bucket manually before configuring the plugin.<\/p>\n\n Step 5 \u2014 (Optional) Generate an API token<\/strong><\/p>\n\n If you want the plugin to display your remaining credit balance inside the WordPress dashboard, generate an API token:<\/p>\n\n This is optional \u2014 the plugin works fully without it. The token is used only to display balance information in your admin dashboard.<\/p>\n\n Go to Hippius Media in your WordPress admin sidebar. The configuration page has several fields.<\/p>\n\n Configuration fields<\/strong><\/p>\n\n Paste the Access Key ID you generated above. It starts with hip_.<\/p>\n\n Paste your Secret Access Key. This field is masked in the UI for security.\nLeave blank to keep an existing Secret Access Key \u2014 useful when updating other settings.<\/p>\n\n Paste your API token if you generated one. This is used only to display your account credit balance inside the WordPress dashboard.<\/p>\n\n The Hippius S3 endpoint URL. Default: For better latency, you can use a regional endpoint instead:<\/p>\n\n All regions serve the same data \u2014 pick whichever is closest to your WordPress server.<\/p>\n\n The name of the bucket you created in the Hippius console. Default: Important.<\/strong> The bucket must already exist in the Hippius console before you set it here. The plugin will not auto-create buckets.<\/p>\n\n Migration options<\/strong><\/p>\n\n When checked, original media files stay on your WordPress server after migration. When unchecked, local files are deleted after successful upload to Hippius, freeing up disk space.<\/p>\n\n Recommendation.<\/strong> Keep this checked when you first start migrating. Once you've verified everything works and your media is correctly served from Hippius, you can disable it to save server disk space.<\/p>\n\n When enabled, any new media file uploaded to WordPress is automatically migrated to Hippius in the background. Recommended once initial setup is verified.<\/p>\n\n Before migrating any files, test that the plugin can reach Hippius with your credentials.<\/p>\n\n Possible results<\/strong><\/p>\n\n You have two migration modes: bulk (for existing files) and auto (for new uploads). You can use either or both.<\/p>\n\n Bulk migration \u2014 for existing files<\/strong><\/p>\n\n If your WordPress site already has media files in the library, use bulk migration to move them all to Hippius in one operation.<\/p>\n\n Note.<\/strong> Bulk migration runs in the background. You can leave the page or close the tab \u2014 migration continues. Come back later to check progress.<\/p>\n\n What happens during migration<\/strong><\/p>\n\n Auto migration \u2014 for new uploads<\/strong><\/p>\n\n Once auto-migration is enabled, you don't need to do anything else. Every new file you (or any author on your site) uploads to the WordPress Media Library is automatically offloaded to Hippius in the background.<\/p>\n\n To enable it:<\/p>\n\n The plugin dashboard gives you a live overview of what's been migrated and your storage usage.<\/p>\n\n Statistics<\/strong><\/p>\n\n Usage<\/strong><\/p>\n\n Verify a file is really on Hippius<\/strong><\/p>\n\n To check that a specific file is actually stored on Hippius:<\/p>\n\n If something doesn't work, check the Error Log<\/strong> and Debug Log<\/strong> at the bottom of the plugin page first \u2014 they usually pinpoint the exact issue.<\/p>\n\n \"Test Connection\" fails with 403 \/ Access Denied<\/strong><\/p>\n\n Possible causes:<\/p>\n\n \"Test Connection\" fails with timeout or DNS error<\/strong><\/p>\n\n Some files fail to migrate<\/strong><\/p>\n\n Check the Error Log for the specific error per file. Common causes:<\/p>\n\n Migrated media doesn't appear on the front-end<\/strong><\/p>\n\n Credit balance shows 0 or doesn't update<\/strong><\/p>\n\n How to read the Debug Log<\/strong><\/p>\n\n The Debug Log shows every URL override decision made by the plugin. Useful entries:<\/p>\n\n Plugin support<\/strong><\/p>\n\n Hippius documentation<\/strong><\/p>\n\n Hippius console<\/strong><\/p>\n\n Community<\/strong><\/p>\n\n You can install Hippius Media Offloader in two ways.<\/p>\n\n Option A \u2014 From the WordPress plugin directory (recommended)<\/strong><\/p>\n\n Option B \u2014 Manual upload<\/strong><\/p>\n\n After activation<\/strong><\/p>\n\n A new menu item Hippius Media<\/strong> will appear in your WordPress admin sidebar. That's the plugin's home base.<\/p>\n\n\n Hippius is a distributed cloud storage platform. Your files are split, encrypted, spread across an independent network of nodes, and verifiable on-chain. It's the simplicity of mainstream cloud \u2014 without having to trust a single provider.<\/p><\/dd>\n Arion is Hippius's own distributed storage engine. It uses Reed-Solomon erasure coding (10 data shards + 20 parity shards = 30 total) and the CRUSH placement algorithm. Your files reconstruct perfectly even if up to 20 nodes fail simultaneously.<\/p><\/dd>\n Communication between WordPress and Hippius uses HTTPS. Once on Hippius, files are encrypted server-side using NaCl envelope encryption \u2014 miners only see encrypted bytes, never your content. For true end-to-end client-side encryption on media, use the Hippius Desktop App in parallel.<\/p><\/dd>\n Your Access Key ID, Secret Access Key, and API token are stored in WordPress's standard options API, with admin-only access. The Secret Access Key field is masked in the UI and never exposed via JavaScript or to the front-end.<\/p><\/dd>\n In most cases it improves performance. Hippius serves files through a distributed network of nodes, reducing load on your origin server and freeing up your hosting bandwidth. For global audiences, you can also put a CDN in front of Hippius.<\/p><\/dd>\n Existing files remain untouched until you actively migrate them. You can bulk-migrate everything, or only enable auto-migration for new uploads and leave the legacy files local.<\/p><\/dd>\n If you kept local copies during migration, deactivating the plugin restores WordPress's default behavior of serving from wp-content\/uploads. There's no automated reverse-migration that downloads files back from Hippius \u2014 keep local copies if you want safe reversibility.<\/p><\/dd>\n The plugin logs each failure with a clear reason. You can retry failed migrations manually from the dashboard.<\/p><\/dd>\n Yes \u2014 images, videos, audio, documents (PDF, DOC, XLS, etc.), archives, and any other WordPress-supported media type. Custom file types can be added through WordPress filters.<\/p><\/dd>\n The plugin uses one bucket per site. If you need multiple buckets (e.g. for different content types), you can run multiple WordPress sites each pointing at a different bucket.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
Before You Start<\/h3>\n\n
\n
\n
hip_<\/code>)<\/li>\nGet Your Hippius Credentials<\/h3>\n\n
\n
console.hippius.com<\/code><\/li>\n\n
\n
hip_<\/code>) and Secret Key<\/strong> somewhere safe.<\/li>\n<\/ol>\n\n\n
wp-media<\/code> or your-site-name).<\/li>\n\n
Configure the Plugin<\/h3>\n\n
Access Key ID<\/h4>\n\n
Secret Access Key<\/h4>\n\n
API Token (optional)<\/h4>\n\n
S3 Endpoint<\/h4>\n\n
https:\/\/s3.hippius.com<\/code><\/p>\n\n\n
https:\/\/eu-central-1.hippius.com<\/code><\/li>\nhttps:\/\/us-east-1.hippius.com<\/code><\/li>\n<\/ul>\n\nBucket Name<\/h4>\n\n
WP-Media<\/code><\/p>\n\nKeep Local Files<\/h4>\n\n
Auto-Migrate New Uploads<\/h4>\n\n
Test the Connection<\/h3>\n\n
\n
\n
Migrate Your Media<\/h3>\n\n
\n
\n
\n
Verify Migration & Monitor Usage<\/h3>\n\n
\n
\n
\n
Troubleshooting<\/h3>\n\n
\n
\n
\n
\n
\n
\n
Support & Resources<\/h3>\n\n
\n
wordpress.org\/support\/plugin\/hippius-media-offloader\/<\/code><\/li>\n<\/ul>\n\n\n
docs.hippius.com<\/code><\/li>\ndocs.hippius.com\/storage\/s3\/integration<\/code><\/li>\ndocs.hippius.com\/learn\/storage-systems<\/code><\/li>\n<\/ul>\n\n\n
console.hippius.com<\/code><\/li>\n<\/ul>\n\n\n
community.hippius.com<\/code><\/li>\n<\/ul>\n\n\n\n
\n
wordpress.org\/plugins\/hippius-media-offloader\/<\/code>.<\/li>\n\n
What is Hippius?<\/h3><\/dt>\n
What is Arion?<\/h3><\/dt>\n
Do my files leave WordPress encrypted?<\/h3><\/dt>\n
Where are my credentials stored?<\/h3><\/dt>\n
Will this affect my website performance?<\/h3><\/dt>\n
What happens to my existing media files?<\/h3><\/dt>\n
Can I revert back to local storage?<\/h3><\/dt>\n
What if migration fails for some files?<\/h3><\/dt>\n
Does the plugin support all WordPress file types?<\/h3><\/dt>\n
Can I use multiple buckets?<\/h3><\/dt>\n
1.0.1<\/h4>\n\n
\n