KAZCODE Universal Storage

KAZCODE Universal Storage moves your Media Library’s binary files — originals and every generated image size — to S3 or S3-compatible storage, and can serve them from your bucket or a CDN. WordPress stays the source of truth: attachment posts, titles, alt text, and metadata never leave your database.

• Auto-offload new uploads and generated sizes (per-object inventory and partial/retry-safe uploads)
• A storage profile with admin CRUD and profile-scoped delivery URLs
• Dashboard, Media, Storage, Migration, Health, and Logs admin screens
• Migrate, verify, restore, adopt-existing, health scan, and repair tools
• Provider presets (AWS, Cloudflare R2, DigitalOcean Spaces, MinIO, Wasabi, Backblaze B2)
• WP-CLI, REST batch APIs, and resumable background jobs
• Optional Pro add-on for multiple storage profiles, cross-provider migration wizard, orphan scan, and advanced health tools — a separate plugin, not a trial or license key on this one

Theme and plugin static assets are never rewritten — only Media Library attachments.

External Services

KAZCODE Universal Storage connects only to object-storage services explicitly selected and configured by the site administrator. It does not send media, credentials, telemetry, or site data to any KAZCODE-owned service, and KAZCODE does not proxy your media through its own servers.

The plugin can connect to Amazon S3, Cloudflare R2, DigitalOcean Spaces, Wasabi, Backblaze B2 through its S3-compatible API, MinIO, or another administrator-supplied S3-compatible endpoint. An account with the selected storage provider may be required. Connections occur only when the administrator configures or tests storage, or uses storage operations such as upload/offload, download/restore, HEAD/verification, migration/adoption of existing objects, or remote delete when that behavior is configured.

Media files and storage API requests move directly between this WordPress site and the administrator-selected storage provider. Credentials are used only to authenticate to the configured storage provider and are not sent to KAZCODE servers. Data sent to the configured provider can include media/object binary data, object keys and paths, and metadata or protocol fields required by the S3-compatible API.

Amazon S3 — https://aws.amazon.com/s3/
Customer Agreement: https://aws.amazon.com/agreement/ — Privacy: https://aws.amazon.com/privacy/

Cloudflare R2 — https://developers.cloudflare.com/r2/
Terms: https://www.cloudflare.com/legal/terms/ — Privacy: https://www.cloudflare.com/privacypolicy/

DigitalOcean Spaces — https://www.digitalocean.com/products/spaces
Terms: https://www.digitalocean.com/legal/terms-of-service-agreement — Privacy: https://www.digitalocean.com/legal/privacy-policy

Wasabi Object Storage — https://wasabi.com/product-terms
Legal: https://wasabi.com/legal — Privacy: https://wasabi.com/legal/privacy-policy

Backblaze B2 Cloud Storage — https://www.backblaze.com/cloud-storage
Terms: https://www.backblaze.com/company/policy/terms-of-service — Privacy: https://www.backblaze.com/company/policy/privacy

MinIO and other self-hosted or generic S3-compatible endpoints — the plugin talks directly to the administrator-configured endpoint; applicable terms and privacy depend on whoever operates it, not on KAZCODE. (https://min.io/)

Development

The human-readable development source and release build tools for KAZCODE Universal Storage are maintained at:

https://github.com/kazmij/kazcode-universal-storage-free

Release builds use Composer and PHP-Scoper (third-party dependencies are namespace-prefixed to avoid collisions with other plugins). Build instructions are in that repository’s BUILD.md.