FOR WOOCOMMERCE STORES & MEDIA-HEAVY WORDPRESS SITES

Store WordPress media for $6/TB with Backblaze B2

The cheapest cloud storage for WordPress. 1.5 MB plugin, free egress through Cloudflare.

All 10 cloud providers free • No credit card required

TL;DR

Storage costs add up faster than you think

Most conversations about cloud storage focus on egress fees. That’s the right conversation for high-traffic sites. But for stores and publishers with large media libraries and moderate traffic, the storage bill is the bigger line item.

A WooCommerce store with 5,000 products and 10 images per product in multiple sizes easily racks up 200 GB of media. On Amazon S3, that’s $4.60/month just to store it. On Cloudflare R2, it’s $3.00/month. On Backblaze B2, it’s $1.20/month.

The difference compounds. Over a year, storing 200 GB costs $55.20 on S3, $36.00 on R2, and $14.40 on B2. For 500 GB, the annual costs become $138.00 (S3), $90.00 (R2), and $36.00 (B2).

Unlike egress, you can’t cache your way out of storage fees. Every GB stored costs money every month, forever.

B2 is built for people who pay attention to those numbers.

Save up to 96% compared to Amazon S3

Here’s what you actually pay across the three most popular S3-compatible providers, using a mid-size WordPress site: 50 GB of media, 100,000 monthly pageviews, 6 images per page at 200 KB average. Based on B2 pricing, S3 pricing, and R2 pricing.

Monthly cost comparison

The B2-only column includes B2’s standard egress rate of $0.01/GB (beyond the free allowance). The B2 + Cloudflare CDN column reflects the Bandwidth Alliance partnership where Cloudflare pulls from B2 at zero cost.

At different storage volumes

B2 + Cloudflare beats both S3 and R2 at every tier. The gap is most dramatic at higher storage volumes, where B2’s $0.006/GB rate stretches furthest.

Where R2 wins over B2: if you’re already on Cloudflare and want the simplest possible setup, R2 is native to the Cloudflare dashboard. No second vendor, no Bandwidth Alliance configuration. See the R2 landing page for that setup. Where S3 wins: if you need AWS ecosystem features like lifecycle policies, Glacier archival, or IAM-level access controls. See the S3 landing page for enterprise setups.

B2 wins when you want the lowest possible bill and don’t mind managing two services (Backblaze + Cloudflare).

Backblaze B2 WordPress plugin options

Not every WordPress cloud storage plugin supports B2. Here’s where each stands:

WP Offload Media does not support Backblaze B2 and hasn’t announced plans to add it. If B2 is your provider, WP Offload Media is not an option.

Media Cloud does support B2, both through the older native B2 API and the newer S3-compatible endpoint. But at 87 MB, it bundles SDKs for services you’ll never use. That’s 58× the size of CloudSync Master.

CloudSync Master connects to B2 through the S3-compatible API using a custom Signature V4 implementation. No bundled SDKs, no 15,000-file dependency trees. The same 1.5 MB plugin that connects to S3 and R2 connects to B2. For a detailed comparison, see CloudSync Master vs WP Offload Media.

How to migrate to B2 from other providers

Already storing media on S3, R2, DigitalOcean Spaces, or Google Cloud Storage? Just add your B2 account and switch to it. CloudSync Master migrates files in the background with zero downtime — available in both Free and Pro.

From another cloud provider

1. Add your B2 account in CloudSync Master settings.
2. Switch the active account to B2.
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 B2 automatically.

There’s no manual migration step and no need to update anything after migration completes. The fallback mechanism means your site stays live throughout the entire process.

From WP Offload Media or Media Cloud

1. Install CloudSync Master Pro alongside your existing plugin.
2. Use the Import feature to adopt cloud metadata from WP Offload Media, Media Cloud, WP-Stateless, or WP Media Folder Cloud.
3. Add your B2 account and switch to it as the active account.
4. The plugin migrates files from S3 to B2 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 B2.

From local storage (first-time offloading)

If you’ve never used cloud storage, the process is even simpler. Connect to B2, use the bulk upload tool to send your existing library to B2, and new uploads go there automatically from that point forward. The setup tutorial below covers this step by step.

30-day money-back guarantee included.

Who this is for

This plugin is built for:

• WooCommerce stores with large catalogs (500+ products) where storage volume drives the bill. B2’s $0.006/GB means 100 GB of product media costs $0.60/month, not $2.30.
• Budget-conscious site owners who want cloud storage benefits without AWS complexity or Cloudflare vendor lock-in. B2 has the simplest pricing model of any major provider.
• WordPress sites with video content or large downloadable files. A 2 GB product download on S3 costs $0.18 in egress per customer. On B2 + Cloudflare, it costs nothing.
• Developers and freelancers building client sites who need a reliable, cheap storage backend they can set up in minutes and forget about.

This might not be for you if:

• You need advanced lifecycle policies to automatically tier objects to cold storage. B2 doesn’t have storage classes comparable to S3 Glacier or Intelligent-Tiering.
• Your site has fewer than 100 images and minimal traffic. At that scale, the cost difference between providers is pennies, and offloading adds complexity that isn’t worth it.
• You need fine-grained access control policies on individual objects. B2 application keys are scoped to buckets, not individual files. S3’s IAM policies are more granular.
• You want everything in one vendor’s dashboard. B2 + Cloudflare means managing two services. Cloudflare R2 puts storage and CDN in one place.

B2 features that matter for WordPress

Free egress through Cloudflare — pay only for storage

This is B2’s killer advantage and the reason it competes with R2 on total cost despite having standard egress rates.

Backblaze is a member of the Cloudflare Bandwidth Alliance. When Cloudflare pulls content from a B2 bucket, the egress is free. Not discounted. Free. Unlimited. This applies to Cloudflare’s free plan too.

In practice, this means you set up Cloudflare as a CDN in front of your B2 bucket, and every image, video, and file served through Cloudflare costs zero in data transfer. Visitors hit Cloudflare’s cache first. Cache misses pull from B2 at no egress cost. Cache hits never touch B2 at all.

The same partnership exists with Fastly, bunny.net, and CacheFly. If you use any of those CDNs, B2 egress is free through them as well.

Works with every tool you already use

If your tools work with Amazon S3, they already work with Backblaze B2. B2’s S3-compatible API means CloudSync Master connects using the same Signature V4 authentication it uses for S3 and R2 — you just change the endpoint URL and credentials. No new SDKs to learn, no migration headaches for your existing workflows.

The S3-compatible endpoint looks like: s3.us-west-004.backblazeb2.com (the region segment varies based on your bucket’s location). You’ll get the exact URL when you create your bucket.

10 GB free forever

B2’s free tier includes 10 GB of storage with no time limit. Not a 12-month trial like AWS Free Tier. Not a limited promotional offer. The first 10 GB is always free. For small WordPress sites, portfolio sites, or development environments, you may never pay a storage bill at all.

The free tier also includes 2,500 free Class B and 2,500 free Class C API calls per day. For most small sites, that covers normal read operations.

Most sites pay zero egress — even without Cloudflare

Even without the Bandwidth Alliance, B2 includes free egress equal to 3× your average monthly storage. Store 100 GB and you get 300 GB of free outbound transfer per month. For many WordPress sites with moderate traffic, this alone eliminates egress costs entirely.

If you exceed the free allowance, egress is $0.01/GB, which is still 89% cheaper than S3’s $0.09/GB.

Ransomware can’t touch your backups

B2 supports Object Lock, which prevents files from being deleted or modified for a specified retention period. If your server gets compromised, locked backup files in B2 can’t be encrypted or deleted by ransomware — they’re immutable until the retention period expires. This is critical for WordPress backup files stored in B2. S3 has this feature too. R2 does not.

Upload your entire library in under an hour (Pro)

CloudSync Master uploads with 5 parallel connections in the free version. Pro lets you configure 1–20 concurrent upload connections, so your initial media library upload to B2 finishes in under an hour instead of file-by-file crawling. Set concurrency higher on dedicated servers, lower on shared hosting.

Free vs Pro: which version do you need?

If you’re testing B2 or run a small site within the 10 GB free tier, start with the free version. For WooCommerce stores, sites with existing libraries that need bulk upload, or anyone migrating from S3 or another provider, Pro pays for itself quickly.

B2 cost breakdown: what you’ll actually pay

B2’s pricing has fewer components than S3, and the free tier covers more ground than you’d expect.

B2 pricing (current as of 2026)

Upload operations (Class A) are free. You never pay to put files into B2. That’s unusual. S3 charges $0.005 per 1,000 PUT requests. R2 charges $4.50 per million writes. B2 charges nothing.

Real-world monthly costs with Cloudflare CDN

Without Cloudflare CDN, the large catalog site would pay $1.20 storage + API $0.48 = about $1.68/month. B2’s built-in free egress allowance (3× storage) means many sites pay zero egress even without a CDN partner.

Step-by-step setup tutorial

Backblaze B2 with CloudSync Master: Full Setup Guide +

The full setup takes about 10 minutes. Backblaze’s interface is straightforward compared to AWS, so most of that time is creating the account if you don’t have one.

1

Create a Backblaze B2 account and bucket

1. Go to backblaze.com and create a free account.
2. In the left sidebar, click Buckets under B2 Cloud Storage.
3. Click Create a Bucket.
4. Enter a bucket name. Use something descriptive like yoursite-wp-media. Names must be globally unique, at least 6 characters, and can include lowercase letters, numbers, and hyphens.
5. Set Files in Bucket are to Public. This allows CloudSync to generate public URLs for your media files. If you plan to use signed URLs exclusively (for private content), you can set this to Private instead.
6. Leave Default Encryption and Object Lock at their defaults unless you have specific security requirements.
7. Click Create a Bucket.

Note the Endpoint shown on the bucket details page. It will look something like s3.us-west-004.backblazeb2.com. You’ll need this for the S3-compatible API connection.

2

Create an application key

Application keys are B2’s equivalent of AWS access keys. They control what the plugin can do.

1. In the Backblaze dashboard, go to Application Keys under Account.
2. Click Add a New Application Key.
3. Give it a name like CloudSync WordPress.
4. Under Allow access to Bucket(s), select the bucket you just created. Don’t use “All” unless you have a reason to.
5. Leave Type of Access as Read and Write.
6. Leave File name prefix empty (the plugin manages its own paths).
7. Set the Duration if you want the key to auto-expire, or leave it blank for no expiration.
8. Click Create New Key.
9. Copy the keyID and applicationKey immediately. The application key is shown only once. If you lose it, you’ll need to create a new key.

B2’s key system is simpler than AWS IAM. No JSON policy documents, no IAM groups. You pick a bucket, pick read/write, and you’re done. Less granularity than S3, but bucket-level access is sufficient for WordPress media offloading.

3

Configure CloudSync Master

1. Install and activate CloudSync Master (free or Pro) in WordPress.
2. Go to CloudSync → Settings.
3. Select Backblaze B2 as the cloud provider.
4. Enter your Application Key ID (keyID) and Application Key.
5. Enter your Bucket Name.
6. The S3-compatible endpoint fills automatically, or paste it manually: s3.us-west-004.backblazeb2.com (use the endpoint from your bucket details).
7. Click Save Settings.

The plugin tests the connection immediately. Green means B2 is connected and ready.

4

Upload your existing media library

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

1. Go to the Sync/Migrate tab in CloudSync Master.
2. Click Upload Local Media to Cloud.
3. The plugin queues files for background processing with parallel uploads (5 in free; Pro supports 1–20 concurrent connections).
4. Close the tab and let it run. A 10,000-image library typically finishes in under an hour.

Once complete, the plugin rewrites all media URLs to point to B2 (or your CDN domain if configured).

5

Set up Cloudflare CDN for free egress (recommended)

This is the step that turns B2 from “cheap” into “absurdly cheap.” Without Cloudflare, you pay $0.01/GB for egress beyond the free allowance. With Cloudflare, egress is free and unlimited thanks to the Bandwidth Alliance partnership.

1. If you don’t already use Cloudflare, add your domain to Cloudflare (the free plan works).
2. Create a CNAME record pointing a subdomain like cdn.yoursite.com to your B2 bucket’s S3-compatible endpoint.
3. In Cloudflare, make sure the proxy (orange cloud) is enabled for that CNAME. This routes traffic through Cloudflare’s network, triggering the free egress partnership.
4. Set a Cache Rule for the CDN subdomain with a long TTL (e.g., 30 days) for static assets.
5. In CloudSync Master settings, enter https://cdn.yoursite.com in the CDN URL field.

Now your media flows: Visitor requests image → Cloudflare cache serves it (fast, free) → Cache miss pulls from B2 (free via Bandwidth Alliance) → Cloudflare caches it for next time.

The entire delivery pipeline costs $0.00 in egress. You only pay B2 storage ($0.006/GB) and API calls.

Eliminate egress fees completely: the Cloudflare + B2 setup

This deserves its own section because it’s the single biggest cost optimization available for WordPress media hosting. Most people don’t realize you can combine two free services (Cloudflare free plan + B2’s free tier) with the Bandwidth Alliance to get a zero-cost media delivery pipeline.

How the Bandwidth Alliance works

Cloudflare and Backblaze are physically interconnected at multiple data centers. When Cloudflare requests a file from B2, the data travels over private interconnections instead of public internet transit. Because neither company pays transit fees for this traffic, Backblaze doesn’t charge you for it. This isn’t a promotional discount. It’s a structural cost reduction that’s been in place since 2018.

What this means for your WordPress site

Without the Bandwidth Alliance, here’s what 1 TB of monthly egress costs across providers:

B2 + Cloudflare matches R2’s zero egress. The difference is B2’s storage is 60% cheaper ($0.006/GB vs $0.015/GB).

The catch (there’s always a catch)

The zero-egress benefit only works when traffic goes through Cloudflare’s proxy. Direct downloads from B2’s S3 endpoint that bypass Cloudflare will incur standard B2 egress charges. This matters for:

• API integrations that pull from B2 directly
• WooCommerce digital downloads if configured to serve from the origin URL instead of the CDN URL
• Any tool or script hitting the B2 endpoint without going through your CDN subdomain

Make sure all public-facing URLs use your Cloudflare CDN domain, not the raw B2 endpoint. CloudSync Master handles this automatically when you set a CDN URL in the plugin settings.

Other CDN partners with free B2 egress

Cloudflare isn’t the only option. These CDN providers also have Bandwidth Alliance agreements with Backblaze:

• Fastly: free B2 egress for Fastly customers
• bunny.net: free B2 egress, one of the cheapest CDNs overall
• CacheFly: free B2 egress

If you’re already using one of these CDNs, you get the same zero-egress benefit without switching to Cloudflare. Set up the CDN to pull from your B2 bucket and configure the CDN domain in CloudSync Master’s settings.

Scaling WordPress with B2

For multi-server WordPress setups, B2 provides the same architectural decoupling as S3 or R2: storage lives outside your server, so adding more servers doesn’t create media sync problems.

Load-balanced environments

Two WordPress servers behind a load balancer both read from and write to the same B2 bucket. No rsync scripts. No NFS mounts. Spin up a new server, install the plugin, and media is immediately available because state lives in the shared database and B2, not on local disk.

Cost predictability for growing sites

B2’s pricing structure makes costs easy to forecast. Storage grows linearly at $0.006/GB. Egress through Cloudflare stays at $0.00 regardless of traffic. Upload operations are free. The only variable cost is read API calls, and those are cheap ($0.004/10,000 beyond the daily free allowance). For a site adding 5 GB of media per month and growing traffic steadily, the monthly B2 cost increase is $0.03. That kind of predictability is useful when you’re planning budgets.

Why store owners trust CloudSync Master

Built by 1TeamSoftware, developers of enterprise WordPress and WooCommerce solutions used by thousands of store owners. Available on WordPress.org with 1,000+ active installations. 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.

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