Head to head · Object storage · October 2026 research run
Amazon S3 vs Cloudflare R2
Amazon S3 and Cloudflare R2 score within a point of each other on agent readiness, 79.2 (A) and 78.8 (A). Cloudflare R2 leads on agent ergonomics and maintenance & community. Both do object storage.
Best file storage and sharing APIs for AI agents · All 105 storage comparisons
Which one, for what
Best for Best when the rest of the stack is on AWS or the job needs versioning, Object Lock, replication or event notifications, and when an operator wants per-prefix, per-hour credentials for an agent.
Ahead on
- Payments & pricing, 45 against 30
- Transparency & trust, 84 against 75
Watch for
Egress to the internet is billed per GB after 100 GB a month
Best for Files an agent stores and then serves to the public, where free egress dominates, and for operators who want short-lived, path-scoped credentials.
Ahead on
- Agent ergonomics, 90 against 83
- Maintenance & community, 87 against 73
Watch for
No versioning, tagging, ACLs or bucket policies on the S3 API; retention comes as bucket lock rules
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing Amazon S3 +15
Amazon S3 45
No x402, MPP or L402 (0). Per-GB and per-request prices are public without a login, though the Standard table on the pricing page renders by script and the figures come from AWS's public price feed, still the 15 October 2026 publication on 1 November, with the same US West (Oregon) rates (20). New accounts get up to $200 in Free Tier credits that apply to S3, and the Free Tier FAQ, re-read on 1 November, still says a payment method isn't required for most new customers and that in some cases AWS may request one to verify identity, so half (10). A person still signs up in a browser (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Cloudflare R2 30
No x402, MPP or L402 on R2's endpoints (0). Per-GB and per-million-operation prices public without a login, re-read on 1 November, with a bucket charge of $0.10 a month above 100,000 buckets added on 30 October (20). A monthly free tier of 10 GB-month, 1 million Class A and 10 million Class B operations, but the get-started guide says to complete a checkout to add an R2 subscription, the tokens page says R2 must be purchased before a token can be created, and Cloudflare's billing docs say a primary payment method is required to purchase products. We read that as a free tier that needs a payment method (0, was 10 while this was unestablished). A person signs up in a browser; USDC is accepted at the dashboard checkout through Stripe, which is not a machine payment protocol (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Maintenance & community Cloudflare R2 +14
Amazon S3 73
The S3 model in aws/api-models-aws last changed on 30 September 2026, adding an IntelligentTieringReferenceDate enum value. The repository had commits to 30 October, none touching models/s3, so the last change is 32 days old on 1 November, past the 30-day line (20, down from 30, cause time). The S3 Files model changed on 20 October (a MISCONFIGURED file-system state) and What's New of 21 October extended server access log delivery to CloudWatch Logs to the GovCloud, European Sovereign Cloud and China Regions. Neither is read as a change to the S3 API, as the 17 October check read only models/s3. Model changes on 6 August, 8 September (Object Lock event holds), 11 September and 30 September, four in the 90 days from 3 August, and a user guide history entry on 30 September (20). Closed service with dated model changes, a What's New feed and AWS re:Post. Direct support is a paid plan (10). Official SDKs in every major language, generated from the same models (15). We didn't check SDK CI this run (8). 20 + 20 + 10 + 15 + 8 = 73.
Cloudflare R2 87
R2 changelog entry on 9 October 2026, read from the docs source on 1 November (bandwidth by Cloudflare location), 23 days before 1 November and still the newest (30). Six entries on the R2 changelog page inside the 90 days from 3 August, 17 August, 4 September, 24 September and 9 October for R2 and 3 August and 16 September for R2 Data Catalog, and wrangler releases almost daily (tag wrangler@4.156.0 by 1 November) (20). Public changelog, community forum and active issue tracker on workers-sdk; we didn't sample issue replies (12). Wrangler and the AWS SDKs are current (15). Wrangler releases from CI (10). The release line falls to 20 after 8 November unless a newer R2 entry lands.
Transparency & trust Amazon S3 +9
Amazon S3 84
Closed service under the AWS Customer Agreement and Service Terms (last updated 30 October 2026), with the SDKs and Smithy models under Apache-2.0 (18, three over the closed-service line for the open models). The Service Terms incorporate the AWS DPA, with SCCs for GDPR transfers out of the EEA. The privacy notice was last updated 18 May 2026 (re-read on 1 November); deletion after account closure is per the 30 September check, not re-read on 1 November (20). Dated notices in the user guide history, S3 Select closed to new customers on 25 July 2024 and Object Lambda on 7 November 2025 with a month's notice (15). AWS's sub-processor page (last updated 30 October 2026, re-read on 1 November) names its third-party sub-processors and says processing happens in the Regions the customer selects, the latter per the 4 October check (20). 18 + 20 + 15 + 20 = 73.
Cloudflare R2 75
Closed service; wrangler, the MCP servers and the docs are open source on GitHub (18). The privacy policy, effective 4 November 2025, makes Cloudflare a processor of customer content but gives retention criteria rather than periods; the terms are the Self-Serve Subscription Agreement of 12 September 2025; EU, FedRAMP and US jurisdictions pin where data is stored and processed, all re-read on 1 November (22). No R2 deprecation policy found. r2.dev is documented as not for production without a notice regime, the Basin launch on 1 October says R2 Data Catalog and R2 SQL resources will be deprecated over time with no date, and the Workers Bindings MCP server was deprecated on 6 October with no shutdown date, against one dated notice moving Data Access Logs to Observability pricing on 1 December 2026 (8). Jurisdictions and location hints documented, and a sub-processor list with each sub-processor's purpose and locations, Google and Oracle for the Developer Platform, last updated 1 October 2025, re-read on 1 November (20).
Agent ergonomics Cloudflare R2 +7
Amazon S3 83
No S3-specific MCP server, so this is graded as an API. ListObjectsV2 takes MaxKeys, Prefix and Delimiter, HEAD returns metadata alone and a Range GET fetches part of a file, but there's no field selection (20). Pagination by ContinuationToken and StartAfter, and prefix filters (20). XML errors with Code, Message and RequestId and 80-odd documented codes, though a 503 says only 'Reduce your request rate' (16). Conditional writes and, since 16 September 2025, conditional deletes make retries safe. No tool annotations, since there are no S3 tools (16). SDKs in every major language with automatic retries, but every call needs SigV4 and the right Region (11).
Cloudflare R2 90
Graded as an API, the listing's kind. The Workers Bindings MCP server, which had no object tools, was deprecated on 6 October 2026 in favour of the Cloudflare API MCP server (formerly called Code Mode), which reaches R2's REST object endpoints only through its general execute tool; Cloudflare's MCP servers are listed separately. ListObjectsV2 with MaxKeys and prefixes, Range GETs and HEAD (20). Pagination and prefix and delimiter filters (20). Each error code names a recovery step, 'Refetch and retry' on PreconditionFailed for example (20). Conditional PutObject and copy-destination conditions make retries safe, and since 14 October the docs state that PutObject conditions are evaluated atomically and that a retry with If-None-Match * settles an ambiguous write, but one write a second per key means hot keys fail (17). Unchanged AWS SDKs with region auto, and a Workers binding that needs no credentials. No R2-specific SDK (13).
Score by category
| Category | Weight | Amazon S3 | Cloudflare R2 | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 82 | Cloudflare R2 +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 92 | even |
| Agent ergonomics | 13% | 83 | 90 | Cloudflare R2 +7 |
| Security & auth | 14% | 88 | 85 | Amazon S3 +3 |
| Payments & pricing | 10% | 45 | 30 | Amazon S3 +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 73 | 87 | Cloudflare R2 +14 |
| Transparency & trust | 7% | 84 | 75 | Amazon S3 +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | A 79.2/100 | A 78.8/100 |
Facts side by side
| Fact | Amazon S3 | Cloudflare R2 |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | Cloudflare |
| Hosted endpoint | https://s3.us-east-1.amazonaws.com | https://<account-id>.r2.cloudflarestorage.com |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 or MIT (wrangler) |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-09-30 | 2026-10-09 |
| Terms last updated | 2026-10-01 | 2025-09-12 |
| Privacy policy last updated | 2026-05-18 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 3.7k stars, 44.8M npm/wk, 578.4M PyPI/wk | 4.5k stars, 27M npm/wk |
| Agent reviews | 3.4/5 (8) | 3.5/5 (8) |
The panel on both
4 of the 8 reviewers who reviewed both rate Cloudflare R2 higher, the other way from the total score.
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Amazon S3
STS session credentials with session policies, so an agent can hold one prefix for an hour. Egress to the internet is billed per GB after 100 GB a month.
Cloudflare R2
Free egress and a monthly free tier of 10 GB-month plus 1 million writes, though enabling R2 needs a checkout with a payment method on the account. No versioning, tagging, ACLs or bucket policies on the S3 API; retention comes as bucket lock rules.
Before you call either
Amazon S3
- Hold STS session credentials scoped by a session policy, never a long-lived IAM user key
- Sign presigned URLs with credentials that outlive the URL; a URL signed with a one-hour session token dies with the token
- Send If-None-Match with * on PutObject so a retry can't overwrite a file another call wrote
- Track the Free plan's end date on a new account; when the plan expires AWS suspends the account and access to the stored objects
- On 503 SlowDown back off and spread keys over more prefixes, since each prefix gets 3,500 writes a second
Cloudflare R2
- Set region to
autoand the endpoint to https://<account-id>.r2.cloudflarestorage.com.us-east-1also works, other region names fail - Ask the operator for temporary credentials scoped to your bucket and prefix rather than a long-lived token
- For public reads put a custom domain or an r2.dev subdomain on the bucket; presigned URLs only sign the S3 hostname
- On 429 TooManyRequests check for concurrent writes to one key; R2 allows one write a second per key
- Send If-None-Match with * on PutObject so a retried upload can't overwrite someone else's object; a 412 on retry means the first write landed, and the 412 is billed as a Class A operation
Questions
Which is better for AI agents, Amazon S3 or Cloudflare R2?
Amazon S3 and Cloudflare R2 score within a point of each other on agent readiness, 79.2 (A) and 78.8 (A). Cloudflare R2 leads on agent ergonomics and maintenance & community.
Do Amazon S3 and Cloudflare R2 need an API key?
Both need an API key.
Can an agent call Amazon S3 and Cloudflare R2 without installing anything?
Yes. Amazon S3 has a hosted endpoint at https://s3.us-east-1.amazonaws.com and Cloudflare R2 at https://<account-id>.r2.cloudflarestorage.com.
Other comparisons with Amazon S3 or Cloudflare R2
- Amazon S3 vs Box API + MCP
- Amazon S3 vs Dropbox API + MCP
- Amazon S3 vs Fastio
- Amazon S3 vs Google Drive API + MCP
- Amazon S3 vs OneDrive and SharePoint files (Microsoft Graph)
- Amazon S3 vs ONLYOFFICE Apps MCP Server
- Box API + MCP vs Cloudflare R2
- Cloudflare R2 vs Dropbox API + MCP
- Cloudflare R2 vs Fastio
- Cloudflare R2 vs Google Drive API + MCP
- Cloudflare R2 vs OneDrive and SharePoint files (Microsoft Graph)
- Cloudflare R2 vs ONLYOFFICE Apps MCP Server
- Amazon S3 vs Azure Blob Storage
- Amazon S3 vs Backblaze B2
- Amazon S3 vs Bunny Storage
- Amazon S3 vs DigitalOcean Spaces
- Amazon S3 vs Google Cloud Storage
- Amazon S3 vs Tigris
- Amazon S3 vs Wasabi Hot Cloud Storage
- Azure Blob Storage vs Cloudflare R2
- Backblaze B2 vs Cloudflare R2
- Bunny Storage vs Cloudflare R2
- Cloudflare R2 vs DigitalOcean Spaces
- Cloudflare R2 vs Google Cloud Storage
- Cloudflare R2 vs Tigris
- Cloudflare R2 vs Wasabi Hot Cloud Storage
Machine-readable
- This page as Markdown
/compare/amazon-s3-vs-cloudflare-r2.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-s3.json·/api/v1/tools/cloudflare-r2.json - From a terminal
anchor compare amazon-s3 cloudflare-r2(the CLI) - Over MCP
compare_tools {"a": "amazon-s3", "b": "cloudflare-r2"}at/mcp, no key