FOR WOOCOMMERCE STORES & MEDIA-HEAVY WORDPRESS SITES

Cut cloud storage costs by 95% with Cloudflare R2

Zero egress fees. Connect to R2 in 5 minutes with a 1.5 MB plugin.

All 10 cloud providers free • No credit card required

TL;DR

The problem with cloud storage egress fees

Amazon S3 charges you every time someone views an image on your site. Cloudflare R2 doesn’t. That single difference (zero egress fees) changes the cost math for every media-heavy WordPress site.

If you run a WooCommerce store with thousands of product photos or a content site with image-rich posts, data transfer charges from S3 can quietly become your biggest cloud expense.

Here’s what that looks like in practice. A WooCommerce store serving 100 GB of product images pays $50+ per month just so visitors can look at those photos. Scale to 500K pageviews and that’s $600 per year in pure egress waste. Every time someone browses your catalog, every time Google’s crawler indexes your product pages, every time a social media preview loads your images, you’re paying data transfer fees. The busier your store gets, the worse it hurts.

A Cloudflare R2 WordPress plugin eliminates that line item entirely. You pay for storage and write operations. Reads and downloads cost nothing.

This guide covers how to set up Cloudflare R2 with CloudSync Master Pro, a lightweight WordPress media offload plugin that connects to R2 (and 9 other providers including Backblaze B2 and DigitalOcean Spaces) without the SDK bloat. We walk through bucket creation, API tokens, R2’s S3-compatible setup process, real cost comparisons with S3, and how to migrate if you’re already on another provider.

Cloudflare R2 vs S3: real cost comparison for WordPress

Let’s run the actual numbers for a mid-size WordPress site: 20 GB of media files, 50,000 monthly pageviews, averaging 6 images per page at 200 KB each.

Monthly cost breakdown

That’s roughly a 93% cost reduction based on current R2 pricing versus S3 pricing. And the gap widens as traffic grows.

At higher traffic

The pattern is clear: the more traffic you have, the more R2 saves you, because egress scales linearly with pageviews while R2 egress stays at zero.

If you’re currently on S3 and spending more than a few dollars a month on data transfer, switching to R2 pays for itself immediately. CloudSync Master Pro makes that migration straightforward. We cover the full process in the migration section below.

Cloudflare R2 WordPress plugin options compared

Most WordPress cloud storage plugins were built for S3 and never added R2 support. Here’s where each one stands:

WP Offload Media doesn’t support R2 at all. If you’re on WP Offload Media and want R2, you need to switch plugins. There’s no workaround. WP-Stateless is Google Cloud Storage only, so it doesn’t support S3-compatible providers either.

Media Cloud does support R2, but it weighs 87 MB. That’s 58× larger than CloudSync Master. Media Cloud bundles the full AWS SDK plus SDKs for multiple other services, most of which you’ll never use. All that code loads into PHP memory on every request.

CloudSync Master Pro is 1.5 MB because it uses a custom Signature V4 implementation instead of bundling SDKs. It sends the same authenticated requests to R2 that the SDK would, without the 15,000+ dependency files. Less code means less memory, faster autoloading, and fewer potential conflicts with your other plugins.

For a detailed feature-by-feature breakdown, see the full CloudSync Master vs WP Offload Media comparison.

Switch from S3 to R2 with zero downtime

The S3-to-R2 path is the most common migration we see. You’re already paying S3 egress, R2 eliminates it, and both use the same S3-compatible API. Cross-provider migration is available in both Free and Pro.

How cross-provider migration works

1. Add your R2 account in CloudSync Master settings.
2. Switch the active account to R2.
3. The plugin starts migrating files automatically in the background.
4. During migration, any files not yet transferred are served from your previous provider — zero downtime, no broken images.
5. Once all files are migrated, everything is served from R2 automatically.

There’s no manual “migrate from X to Y” step and no need to update your active provider after migration. The fallback mechanism means your site stays live with zero downtime throughout the entire process.

Coming from WP Offload Media or Media Cloud?

If you’re currently using another plugin with S3:

1. Install CloudSync Master Pro alongside your current plugin.
2. Use the Import feature to adopt existing cloud metadata from WP Offload Media, Media Cloud, WP-Stateless, or WP Media Folder Cloud.
3. Once imported, add your R2 account and switch to it as the active account.
4. The plugin migrates files from S3 to R2 automatically in the background, falling back to S3 for anything not yet transferred.
5. Once migration completes, deactivate and remove the old plugin.

Zero downtime throughout. Your site never goes down because the fallback mechanism serves files from S3 until they’ve been migrated to R2.

Free version includes full R2 support. 5-minute setup. No credit card required.

Who this is for

This plugin is built for:

• WooCommerce stores with 1,000+ product images paying S3 egress fees every month. If your cloud storage bill grows with every pageview, R2 eliminates that cost entirely.
• Content publishers with image-heavy posts and growing traffic. Blogs, news sites, and media outlets where every article adds more images to serve.
• Agencies managing multiple WordPress sites on cloud storage. Standardize on one lightweight plugin across all client sites instead of juggling different solutions.
• Anyone migrating away from WP Offload Media for R2 support. WP Offload Media doesn’t support R2, and CloudSync Master Pro can import its metadata directly.

This might not be for you if:

• You need archival or cold storage with lifecycle policies (R2 has a single storage tier, no equivalent to S3 Glacier).
• Your site has fewer than 100 images and minimal traffic. At that scale, media offloading adds complexity without meaningful savings.
• You need data residency in a specific country. R2 uses broad location hints, not country-specific regions.
• You’re happy with your current S3 costs and don’t need to reduce them.

R2 features that matter for WordPress

Global delivery in under 100ms — no CDN setup required

Your visitors get fast-loading images from 300+ Cloudflare edge locations worldwide, without configuring a separate CDN. When you attach a custom domain to an R2 bucket, Cloudflare’s CDN kicks in automatically. A visitor in Singapore gets images from a Singapore POP, not from wherever R2 stored the original. This is the equivalent of S3 + CloudFront, except you don’t set up a separate CloudFront distribution or pay for CloudFront data transfer.

Resize and transform images on the fly — without touching your server

Need on-the-fly image resizing, watermarking, or access control without touching your WordPress server? Cloudflare Workers can intercept requests to your R2 bucket and transform them at the edge. CloudSync Master doesn’t manage Workers directly, but if you’ve set up a Worker in front of your R2 bucket, the plugin works with it transparently since all requests go through the same custom domain.

Fine-tune caching to match your traffic patterns

Because R2 traffic flows through Cloudflare’s proxy, you can apply cache rules at the Cloudflare level. Set long TTLs for images (they rarely change), short TTLs for dynamic assets, and use cache purge when you update content. This level of caching control comes free with any Cloudflare plan.

S3-compatible — switch without relearning anything

R2 uses the same S3-compatible API protocol and Signature V4 authentication that Amazon S3 uses. For you, that means any tool or workflow you’ve built around S3 works with R2 after changing the endpoint URL and credentials. Your existing SDKs, authentication flows, and integrations all carry over unchanged.

WordPress Multisite support

CloudSync Master Pro is Multisite compatible, which means you can manage all your network’s media from one dashboard. Each subsite can have its own R2 bucket, or you can configure a shared bucket at the network level with per-site path prefixes. All subsites get the same zero-egress benefit.

Upload your full library while you sleep (Pro)

Offload your entire existing media library overnight with bulk upload. Pro supports 1-20 configurable concurrent connections, so your initial library upload finishes in under an hour instead of waiting for files to upload one at a time. Set it higher on beefy servers, lower on shared hosting. The free version auto-uploads new media with 5 parallel connections.

Two storage tiers, but no deep archive

R2 offers two storage classes: Standard ($0.015/GB/month) and Infrequent Access ($0.01/GB/month, launched 2024). There’s no equivalent to S3 Glacier or deep archive tiers. For most WordPress media use cases this doesn’t matter, since your images need to be instantly accessible. But if you need deep archival storage for old backups or rarely accessed files at Glacier-level pricing, S3’s broader range of storage classes is still an advantage.

Fewer regions than S3

S3 operates in 30+ specific regions worldwide. R2 uses broad location hints (North America, Europe, Asia-Pacific) with Cloudflare managing placement automatically. For WordPress media served through CDN, this is fine: the CDN cache is what determines latency for visitors, not the origin location. But if you have data residency requirements that mandate storage in a specific country, verify that R2’s location options meet your compliance needs.

Free vs Pro: which version do you need?

If you’re testing R2 or run a small personal site, start with the free version. For WooCommerce stores, sites with existing media libraries that need bulk upload, or anyone migrating from another cloud provider, Pro pays for itself in the first month through time saved alone.

R2 cost breakdown: what you’ll actually pay

Cloudflare R2 pricing has three components, and they’re straightforward.

R2 pricing (as of 2026)

Real-world monthly costs

The free tier is generous enough that many small WordPress sites will pay literally nothing for R2 storage and delivery.

Step-by-step setup tutorial

Cloudflare R2 with CloudSync Master — Full Setup Guide +

The setup takes about 5 minutes. R2’s credential system is simpler than AWS IAM, so there are fewer steps than an S3 setup.

1

Create your R2 bucket

1. Log into the Cloudflare Dashboard.
2. Select your account, then click R2 Object Storage in the left sidebar.
3. Click Create bucket.
4. Enter a bucket name. Use something descriptive like yoursite-wp-media. Bucket names must be lowercase with no spaces.
5. Select Automatic for the location hint, or pick a specific region if your visitors are concentrated in one area. R2’s location hints include North America, Europe, and Asia-Pacific.
6. Click Create bucket.

That’s it for the bucket. No public access toggles, no versioning decisions, no encryption configuration pages. R2 keeps it simple.

A note on R2 locations: Unlike S3, which has 30+ specific regions, R2 uses broad location hints. Cloudflare automatically places your data for optimal performance based on access patterns. If you set your bucket to “Automatic,” Cloudflare distributes data based on where requests come from. For most WordPress sites, Automatic is the right choice.

2

Generate an R2 API token

R2 uses Cloudflare API tokens instead of AWS-style IAM users. This is actually easier to manage.

1. In the Cloudflare Dashboard, go to R2 Object Storage → Overview.
2. Click Manage R2 API Tokens on the right side.
3. Click Create API token.
4. Give the token a name like CloudSync Master.
5. Under Permissions, select Object Read & Write for your specific bucket. Don’t grant Admin access unless you have a reason.
6. Optionally set a TTL (time to live) to auto-expire the token after a set period.
7. Click Create API Token.
8. Copy the Access Key ID, Secret Access Key, and note the Endpoint URL (it looks like https://<account-id>.r2.cloudflarestorage.com).

Save these somewhere secure. You won’t see the secret key again.

How R2 tokens differ from S3 IAM: With S3, you create an IAM user, attach a JSON policy document, generate access keys, and manage them through AWS’s identity system. R2 simplifies this to a single API token scoped to specific buckets and permissions. No JSON policies, no IAM groups, no permission boundaries. You pick the bucket, pick the access level, and you’re done.

3

Configure CloudSync Master Pro settings

1. Install and activate CloudSync Master Pro in your WordPress dashboard.
2. Go to CloudSync → Settings.
3. Select Cloudflare R2 as the cloud provider.
4. Enter your Access Key ID and Secret Access Key from Step 2.
5. Enter your Bucket Name.
6. The endpoint URL fills automatically for R2 (or paste it manually if needed).
7. Click Save Settings.

The plugin tests the connection immediately. A green confirmation means files will start flowing to R2.

4

Offload your existing media library

New uploads go to R2 automatically once connected. For your existing files:

1. Go to the Sync/Migrate tab in CloudSync Master.
2. Click Upload Local Media to Cloud.
3. The plugin queues your media library for background processing. It handles files asynchronously with parallel uploads (5 in free; Pro supports 1-20 concurrent connections), so you can close the tab and let it run.

Once files are in R2, the plugin rewrites all media URLs on your frontend. Your <img> tags, CSS background images, and download links point to R2 (or your custom CDN domain) instead of /wp-content/uploads/.

5

Set up a custom domain (optional but recommended)

R2 bucket URLs look like https://<account-id>.r2.cloudflarestorage.com/bucket/file.jpg. That’s functional but ugly. A custom domain gives you clean URLs like cdn.yoursite.com/file.jpg and routes everything through Cloudflare’s CDN.

1. In the Cloudflare Dashboard, go to your R2 bucket settings.
2. Click Custom Domains → Connect Domain.
3. Enter a subdomain like cdn.yoursite.com (the root domain must be on Cloudflare DNS).
4. Cloudflare creates the DNS record automatically.
5. In CloudSync Master settings, enter https://cdn.yoursite.com in the CDN URL field.

Now your media is served through Cloudflare’s CDN with your own domain, full caching, and zero egress fees. No separate CDN subscription required.

Why Cloudflare R2 is different

Most cloud storage providers follow Amazon’s pricing model: cheap storage, expensive egress. You pay a few cents per GB to store files, then $0.05–$0.09 per GB every time those files are downloaded. For a WordPress site, “downloaded” means every time a visitor loads a page and their browser fetches your images.

Cloudflare built R2 specifically to kill egress fees. The storage is S3-compatible at the API level, so any tool that works with S3 can talk to R2 with minor configuration changes. But the billing model is fundamentally different:

R2 charges for storage and operations only. There is no per-GB fee for data leaving R2. None. Whether you serve 1 GB or 1 TB of images per month, the egress cost is $0.00.

This matters because egress typically accounts for 70–90% of your total cloud storage bill on S3. Remove that, and your monthly cost drops dramatically.

R2 also sits on Cloudflare’s global network, not tied to a single AWS region. When you pair R2 with a custom domain through Cloudflare, your media gets served through Cloudflare’s CDN automatically. No separate CloudFront distribution to set up, no additional CDN subscription.

And R2 uses S3-compatible APIs. You don’t need a new SDK or a different authentication system. R2 speaks the same protocol as S3, which means CloudSync Master Pro connects to it using the same Signature V4 authentication it uses for Amazon. The only differences are the endpoint URL and how you generate credentials (API tokens instead of IAM users).

Scaling WordPress with Cloudflare R2

For agencies and multi-site setups, R2 offloading has the same architectural benefit as S3: it separates storage from compute.

Load-balanced environments

If you run WordPress behind a load balancer with multiple app servers, local media storage creates sync headaches. An image uploaded on Server A isn’t available on Server B. You end up building rsync scripts or NFS mounts.

With R2 as your media backend, every server reads from and writes to the same bucket. No file sync needed. Spin up a new server, install the plugin, and it works immediately because media state lives in the database (shared) and R2 (shared), not on local disk.

Cost predictability at scale

The zero-egress model makes R2 especially attractive for scaling. With S3, your costs grow with both storage and traffic. A viral blog post that drives 10× normal traffic creates a surprise egress bill. With R2, traffic spikes don’t affect your storage costs at all. You pay the same whether you serve 10 GB or 10 TB. That predictability is useful for budgeting.

Why store owners trust CloudSync Master

Built by 1TeamSoftware, developers of enterprise WordPress and WooCommerce solutions with over a decade of experience building plugins for store owners. CloudSync Master is listed on WordPress.org with 1,000+ active installations and has passed the official WordPress plugin review process. Tested up to WordPress 6.7.

Every paid license includes a 30-day money-back guarantee, priority support, and ongoing updates. The plugin works with WooCommerce, Multisite, and all major hosting providers including Cloudways, SiteGround, and WP Engine.

If it doesn’t work for your setup, you get your money back. No questions.