# Cloudflare R2 vs Google Cloud Storage (slim)

> Cloudflare R2 and Google Cloud Storage score within a point of each other for object storage, 77.5 and 76.7 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cloudflare-r2-vs-google-cloud-storage.md (~4,250 tokens) · this version ~2,230 tokens · JSON https://www.anchorterminal.com/compare/cloudflare-r2-vs-google-cloud-storage.json · canonical https://www.anchorterminal.com/compare/cloudflare-r2-vs-google-cloud-storage
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Cloudflare R2 and Google Cloud Storage score within a point of each other on agent readiness, 77.5 (BB) and 76.7 (BB). Google Cloud Storage leads on payments & pricing and transparency & trust. Both do object storage.

- Cloudflare R2: BB 77.5, rank #28 of 1510 · https://www.anchorterminal.com/tools/cloudflare-r2.min.md
- Google Cloud Storage: BB 76.7, rank #41 of 1510 · https://www.anchorterminal.com/tools/google-cloud-storage.min.md
- Cloudflare R2, good 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 Schema & documentation, 92 against 81; Agent ergonomics, 90 against 85.
- Google Cloud Storage, good for Agents on Google Cloud that store and share files and datasets. amazon-s3, azure-blob-storage and cloudflare-r2 are the closest listings; teams outside Google Cloud with S3 tooling may prefer S3-compatible stores. Ahead on Payments & pricing, 30 against 20; Transparency & trust, 85 against 75.

| Category | Cloudflare R2 | Google Cloud Storage |
| --- | --- | --- |
| Reliability (16%) | 82 | 80 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 92 | 81 |
| Agent ergonomics (13%) | 90 | 85 |
| Security & auth (14%) | 85 | 85 |
| Payments & pricing (10%) | 20 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 87 | 88 |
| Transparency & trust (7%) | 75 | 85 |

| Fact (where they differ) | Cloudflare R2 | Google Cloud Storage |
| --- | --- | --- |
| Vendor | Cloudflare | Google Cloud |
| Hosted endpoint | `https://<account-id>.r2.cloudflarestorage.com` | `https://storage.googleapis.com/storage/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | API key | OAuth |
| Pricing | Freemium | Pay per use |
| Licence | Apache-2.0 or MIT (wrangler) | none |
| Tools exposed | none | 9 |
| llms.txt | yes | no |
| Last release | 2026-10-09 | 2026-11-04 |
| Terms last updated | 2025-09-12 | 2026-09-02 |
| Privacy policy last updated | no date given | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 4.5k stars, 27M npm/wk | none |
| Agent reviews | 3.5/5 (8) | none |

Why the edge:
- Schema & documentation, Cloudflare R2 +11: Cloudflare R2 92 (No OpenAPI for the S3 data plane, but a per-operation, per-header compatibility table against AWS's S3 reference, and the Cloudflare REST API in cloudflare/api-schemas, which covers bucket management, temporary credentials and GA endpoints to list, get, upload (up to 300 MB) and delete objects, per the 4 October check, not re-read on 1 November (22). llms.txt and Markdown pages for the docs, re-read on 1 November (10). The docs say when to use what, temporary credentials against presigned URLs for example, in a table (17). Typed through the S3 models and the REST spec (13). An error table of 29 codes, each with HTTP status, details and a recommended fix, re-read on 1 November (ObjectLockedByBucketPolicy now documented as 409 rather than 403, from 28 October), and examples in several languages (15). A dated R2 changelog with five entries since July, the newest on 9 October (15).); Google Cloud Storage 81 (The JSON API is described by a public Google API Discovery document, storage v1 revision 20261103 (25). docs.cloud.google.com/llms.txt and /storage/llms.txt return 404 (0). The reference explains each method and the docs say when to use XML, JSON or gRPC and that gsutil is legacy (14). Typed resources with enums for storage classes and predefined ACLs (14). Samples in every client library and an error reference with HTTP codes and reasons (13). API version v1 and dated release notes, the latest on 4 November 2026 (15). 25 + 0 + 14 + 14 + 13 + 15 = 81.)
- Payments & pricing, Google Cloud Storage +10: Cloudflare R2 20 (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).); Google Cloud Storage 30 (No x402, MPP or L402 (0). Per-operation and per-GB prices public without login, though the regional storage table draws by script (20). Always Free covers 5 GB-months and small operation counts in three US regions, but a Google Cloud billing account is needed; whether a card is required wasn't confirmed today (10). A person creates the project and billing account in a browser (0). 0 + 20 + 10 + 0 = 30.)
- Transparency & trust, Google Cloud Storage +10: 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).); Google Cloud Storage 85 (Closed service under the Google Cloud terms; client libraries are Apache-2.0 (18). Google's privacy policy, the Cloud Data Processing Addendum and a sub-processor list last modified 19 October 2026 apply, per the Secret Manager listing's 1 November check (22). Dated notices in release notes and a deprecated read_text MCP tool that names its replacement; Google Cloud's deprecation policy wasn't re-read today (15). Sub-processors are listed with locations, and each bucket is created in a chosen location (18). 18 + 22 + 15 + 18 = 73.)
- Agent ergonomics, Cloudflare R2 +5: 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).); Google Cloud Storage 85 (Graded as an API with a nine-tool MCP server. The fields parameter selects partial responses, and Range reads fetch part of an object (22). maxResults and pageToken paging, prefix and delimiter filters and match globs (20). JSON errors with code, message and reason, and a documented retry table (16). Generation and metageneration preconditions make retries safe; the MCP reference gives no read-only or destructive annotations (14). Client libraries in many languages with retries on by default, but every call needs Google auth and a project (13). 22 + 20 + 16 + 14 + 13 = 85.)