Comparison chart of cloud storage providers showing cost and performance metrics for large file uploads

S3 vs Cloudflare R2 vs Backblaze B2 for File Uploads

Compare itemised storage, request and download costs, multipart limits and Next.js upload architectures with a local workload calculator.

Ops·Updated 2026-11-18

Choose storage by the amount you retain, the bytes you deliver and the operations your upload workflow generates. S3 fits AWS integrations, R2 removes direct internet egress charges, and B2 offers a lower standard storage rate with a download allowance tied to stored inventory. This comparison uses provider documentation checked on 16 November 2026 and a shared calculation model. Start with the operations guides for deployment concerns beyond the storage bill.

Choose a provider for the workload

RequirementStarting choiceConstraint to check
Existing AWS permissions, events and processingS3Region, delivery route and service charges
Repeated internet deliveryR2Request volume, rounding and application compute
Retained archives with modest downloadsB2Monthly average inventory and 3x delivery allowance
Browser-to-storage uploadsAny supported providerAuthenticated signing, multipart limits and cleanup

Use the workload calculator to test those choices with your own assumptions. A storage price alone cannot answer a question about a media application that repeatedly serves the same file. Equally, a download allowance has little value to an archive that is rarely read.

Reviewed Standard storage prices

USD rates checked 2026-11-16. Storage per provider GB-month, requests per million.
ConfigurationStorageWrites/listReadsDelivery
Amazon S3 Standard
us-east-1
$0.023/GiB$5$0.4$0.09/GiB
Cloudflare R2 Standard
Standard, default placement
$0.015/GB$4.5$0.36$0/GB
Backblaze B2 pay-as-you-go
Standard published rate
$0.00695/GB$0$0$0.01/GB

The model uses S3 Standard in us-east-1, R2 Standard and B2 pay-as-you-go. AWS billing GB are binary units, shown here as GiB. R2 and B2 use decimal units in this model. The form converts the chosen input units before pricing. All costs are USD, with a steady 30-day inventory assumption. Provider records supply the table, worked examples and calculator so a reviewed rate change updates all three.

S3's first storage and delivery tiers are the supported range. Larger AWS workloads need additional tier calculations. R2 rounds storage and operation usage up to its billing unit after the selected allowances. B2 standard Class A, B and C API operations are free under its current pay-as-you-go schedule. Event-notification transactions are outside this calculator. Review account-wide allowance consumption before applying the free amounts to another workload.

R2 versus S3 for an upload application

S3 provides integration with AWS IAM and services used to process uploaded objects. That can simplify a pipeline already running in AWS. Consider the full path from receipt to scanning, transformation and delivery. Object storage, compute, encryption key operations and CDN delivery can belong to different billing categories. A direct S3 internet download and delivery through a CDN need different cost assumptions.

R2 supports event notifications through queues and has Standard and Infrequent Access classes. Its object operations are strongly consistent. Permission propagation and cached copies have separate behaviour, so a bucket permission change is not a substitute for designing cache invalidation or a protected delivery endpoint. The default model here uses Standard storage. Infrequent Access adds retrieval fees and a minimum duration that need their own calculation. R2 consistency, event notifications and storage classes.

If your application already runs on Azure or Google Cloud, include its native storage service in the shortlist. This object storage comparison covers both alongside S3 and R2. Price the actual region and request mix separately using each provider's rate card.

Test upload speed from the regions your users occupy. An edge receiver can be close to the browser while its storage operations still travel elsewhere. The route, part size and concurrency affect measured throughput. Neither a low storage price nor a nearby request handler establishes a performance winner.

R2 versus B2 for storage and downloads

B2's published standard price is tied to stored byte-hours over the billing cycle. Its included download amount scales with average monthly storage. A steadily retained archive and a short-lived media collection can therefore produce different allowances even when they accept the same number of uploads. Use completed average inventory in the calculator and enter newly uploaded bytes separately.

R2's free internet egress can become attractive as repeated delivery rises, while its storage and rounded request charges remain relevant. For many small objects, count GET and HEAD calls as well as writes. Listing millions of objects also has operational consequences beyond the bill. A community question about managing large inventories on R2 and B2 highlights the need to design object discovery before migration. Inventory discussion.

B2 supports webhook-based event notifications. Review delivery retries and the application's handling of repeated notifications before using an event to trigger release or billing. A provider notification indicates an event occurred, while your application state decides what processing remains. Backblaze event notifications.

S3 or Cloudflare R2 for a Next.js app?

Keep the browser client separate from the authenticated control API. The browser requests a session for an authorised destination. The server checks ownership and quotas, chooses an object key and creates the multipart upload. It signs only the expected part operations, with short expiry. File bytes can then travel directly to storage if the client supports that lifecycle.

Completion belongs to the authenticated control API too. Verify the expected parts and object identity, complete once, then quarantine or process the result before release. Persist a completion receipt so a retry after a lost response returns the same result. An expiry job aborts abandoned multipart uploads. A status request must enforce the same owner binding as the write path.

The modern-framework example covers the client boundary. See how to implement resumable uploads to S3-compatible storage with a multipart adapter. Hosting request caps apply when bytes pass through a function, while direct browser-to-storage requests follow provider limits. Next.js alone does not specify a hosting body limit.

Multipart limits and protocol differences

S3's current multipart documentation specifies a 48.8 TiB maximum object, up to 10,000 parts and part sizes from 5 MiB to 5 GiB, with a smaller final part allowed. R2 documents a separate maximum and equal-sized non-final parts. Read its limit footnotes before designing near the boundary. The calculator conservatively accepts B2 objects up to 5 TB and parts up to 5 GB. These constraints are provider-specific. S3 limits, R2 limits, B2 large files.

Resumable.js sends application chunks. A receiver must translate them into provider parts, persist ETags and serialise completion. A presigned PUT changes the byte path but still requires session ownership, signing and reconciliation. Use a native multipart client when that reduces the integration work, and compare the library choices.

Three worked upload workloads

30-day examples with unused eligible allowances. Inventory and downloads are decimal GB.
Scenario and assumptionsAmazon S3 StandardCloudflare R2 StandardBackblaze B2 pay-as-you-go
archive: 1000 GB stored, 100 uploads of 100 MB, 100 reads, 10 GB delivered, 100 list calls, 8 MiB parts, no retries or incomplete storage$21.43
Storage $21.42, writes $0.01, reads $0.00, delivery $0.00
$14.85
Storage $14.85, writes $0.00, reads $0.00, delivery $0.00
$6.88
Storage $6.88, writes $0.00, reads $0.00, delivery $0.00
media: 1000 GB stored, 1,000 uploads of 100 MB, 100,000 reads, 10000 GB delivered, 1000 list calls, 8 MiB parts, no retries or incomplete storage$850.73
Storage $21.42, writes $0.07, reads $0.04, delivery $829.19
$14.85
Storage $14.85, writes $0.00, reads $0.00, delivery $0.00
$76.88
Storage $6.88, writes $0.00, reads $0.00, delivery $70.00
small: 100 GB stored, 2,000,000 uploads of 0.05 MB, 20,000,000 reads, 100 GB delivered, 0 list calls, 8 MiB parts, no retries or incomplete storage$20.14
Storage $2.14, writes $10.00, reads $8.00, delivery $0.00
$9.45
Storage $1.35, writes $4.50, reads $3.60, delivery $0.00
$0.63
Storage $0.63, writes $0.00, reads $0.00, delivery $0.00

These examples use the same calculation function as the interactive result. They assume a uniform average file size, count multipart creation and completion, and distinguish new uploaded bytes from retained inventory. Mixed file-size distributions need separate estimates because splitting an average file can underestimate request counts. No benchmark or actual customer bill is implied.

Compare costs for your upload workload

Estimate a steady 30-day workload. AWS uses binary billing GB (GiB here). R2 and B2 use decimal GB. R2 inventory represents average daily peaks. B2 inventory represents average byte-hours.

Override USD rates

Overrides retain the provider unit and allowance rules shown above.

Amazon S3 Standard
Cloudflare R2 Standard
Backblaze B2 pay-as-you-go

Last calculated monthly estimate in USD
ProviderStorageWrites/listReadsDeliveryTotal
Amazon S3 Standard$21.42$0.01$0.00$0.00$21.43
Cloudflare R2 Standard$14.85$0.00$0.00$0.00$14.85
Backblaze B2 pay-as-you-go$6.88$0.00$0.00$0.00$6.88

1,500 estimated write/list requests. New uploads total 10.000 GB, independently of stored inventory. Multipart files include creation, each part and completion. Small files use one PUT.

Standard storage has no modelled retrieval or minimum-retention charge. Excludes tax, Workers/Lambda compute, CDN costs, replication, KMS, scanning, B2 event notifications, account credits and higher AWS tiers. Allowances may be shared with other workloads. Incomplete parts count toward storage here, and conservatively do not increase B2 delivery allowance.

Rates checked 2026-11-16. Model 2026-11-16.1. Review every 30 days.

Export the result with its assumptions before discussing an architecture change. Check whether an allowance is already consumed elsewhere, how failed uploads are removed, and which costs belong to the application runtime. Then apply the security checklist to the signing, status and release paths before exposing uploads to users.