How to Offload WordPress Media Library to Cloudflare R2 / AWS S3 (Zero Egress)

As a WordPress website expands, the single largest consumer of server disk space is never the MariaDB database or core PHP application code—it is the /wp-content/uploads/ media directory. High-resolution product images, PDF catalogs, podcast audio, and banner graphics quickly accumulate into tens or hundreds of gigabytes of storage on your Linux VPS.

This storage bloat creates severe operational hazards: nightly server backups take hours to archive and transfer, disk capacity fills up unexpectedly, and migrating to larger virtual servers becomes an agonizing ordeal. Furthermore, serving heavy static media files directly from your application server consumes valuable web server worker processes that should be reserved for dynamic PHP execution.

By offloading your media library to Cloudflare R2 or AWS S3, you eliminate storage constraints entirely. Cloudflare R2 provides an S3-compatible object storage API with one game-changing advantage: zero egress bandwidth fees. In this guide, you will learn how to configure Cloudflare R2 buckets, link custom CDN domains, synchronize historical uploads, and serve media globally at edge speeds.

1. Why Cloudflare R2 Beats Traditional AWS S3 for WordPress

Comparison Feature	Cloudflare R2	Standard AWS S3
Egress Bandwidth Cost	$0.00 / GB (100% Free Egress)	$0.09 / GB (Costly at scale)
Storage Pricing	$0.015 / GB per month	$0.023 / GB per month
Free Monthly Tier	10 GB storage free every month	5 GB free for first 12 months
API Compatibility	100% S3 API Compatible	Native S3

2. Creating the Cloudflare R2 Bucket & Generating API Credentials

1. Log in to your Cloudflare Dashboard and navigate to R2 > Create bucket.
2. Name your bucket (e.g., my-site-media-prod) and choose Automatic location hints.
3. Under Settings > Public Access, connect a custom domain (such as https://media.yourdomain.com). Cloudflare provisions a free SSL certificate automatically.
4. In the R2 overview page, click Manage R2 API Tokens > Create API Token.
5. Select Object Read & Write permissions and restrict the scope to your newly created media bucket.
6. Record the Access Key ID, Secret Access Key, and the S3 Endpoint URL (e.g., https://<account_id>.r2.cloudflarestorage.com).

3. Configuring Media Offloading in WordPress

Install and activate the open-source Media Cloud or WP Offload Media Lite plugin via WP-CLI:

wp plugin install media-cloud --activate --allow-root

Navigate to Media Cloud > Storage Settings in your WordPress admin:

• Storage Provider: Select Amazon S3 Compatible.
• Access Key: Your Cloudflare R2 Access Key ID.
• Secret Key: Your Cloudflare R2 Secret Access Key.
• Bucket Name: my-site-media-prod
• Custom Endpoint: https://<account_id>.r2.cloudflarestorage.com
• Path Style URLs: Enabled.
• Custom Domain (CDN): https://media.yourdomain.com

4. Synchronizing Historical Media Uploads

To offload existing historical media files without timing out your web browser, execute the batch migration command directly via the terminal using the AWS CLI tool:

# Install AWS CLI
sudo apt install -y awscli

# Configure temporary R2 credentials
export AWS_ACCESS_KEY_ID="YOUR_R2_ACCESS_KEY"
export AWS_SECRET_ACCESS_KEY="YOUR_R2_SECRET_KEY"
export AWS_DEFAULT_REGION="auto"

# Sync local /uploads folder to Cloudflare R2 bucket
aws s3 sync /var/www/my-site/wp-content/uploads/ s3://my-site-media-prod/uploads/   --endpoint-url https://<account_id>.r2.cloudflarestorage.com   --cache-control "max-age=31536000,public"

Once all historical assets have uploaded, run the database media replacement tool inside Media Cloud to update image references in wp_posts from local paths to your new https://media.yourdomain.com CDN URL.

5. Purging Local Uploads & Slashing Backup Sizes

Once you verify that all media files load cleanly from your R2 CDN domain, enable the “Delete Local Media After Upload” setting in Media Cloud. Now, whenever an editor uploads an image, WordPress generates thumbnail sizes, pushes all files to R2, and deletes the local copies from your server.

Your server’s daily backup archive shrinks from 50GB down to a lightweight 150MB database and code package that takes only 10 seconds to back up and transfer offsite!

Cloudflare R2 Media Offloading: Caching Rules & SEO Image Optimization

Maximizing the benefits of offloading WordPress media to Cloudflare R2 requires configuring intelligent edge caching and image delivery rules:

• Configuring Cloudflare Edge Cache Rules for Media: By default, Cloudflare caches media files according to origin response headers. To ensure maximum global cache hit ratios, create a Cache Rule in the Cloudflare Dashboard matching your custom media subdomain (media.yourdomain.com/*):
  • Edge TTL: Respect origin or set to 1 Year (31,536,000 seconds).
  • Browser TTL: Set to 1 Month.
  • Cache Everything: Ensures all images, PDFs, and assets are permanently cached at the nearest edge PoP.
• Automating WebP and AVIF Image Delivery: Pair your Cloudflare R2 media subdomain with Cloudflare Polish or an automated image converter. This dynamically delivers next-generation AVIF and WebP image formats to supported browsers, shrinking image payloads by an additional 50–70% without altering origin files.
• Securing S3 API Credentials in WordPress: Never store your Cloudflare R2 Access Key ID and Secret Access Key in the WordPress database where rogue administrators or malicious plugins could read them. Instead, define them as immutable constants in wp-config.php:

  define('CLOUDFLARE_R2_ACCESS_KEY', 'your_r2_access_key_here');
  define('CLOUDFLARE_R2_SECRET_KEY', 'your_r2_secret_key_here');