R2 Desk ProR2 Desk PRO
Beta $25First 250 per platform
Navigation
Beta $25First 250 per platformRead docs
Desktop-native / local-first / privacy-first

Cloudflare R2 deserves a desktop client built for real operators.

R2 Desk Pro gives developers and small teams a serious desktop workflow for bucket operations, transfer reliability, sync planning, asset preview, and delivery tooling without pushing credentials into the browser.

View beta pricingRead docs
Scroll to explore the product
Product overview

A desktop workflow for serious Cloudflare R2 operations.

Secure profiles, reliable transfers, sync planning, asset preview, and delivery tooling in one professional desktop client.

Bucket browser

Browse buckets, prefixes, metadata, and bulk object actions from a desktop workflow built for real storage operations.

Transfer engine

Run parallel uploads and downloads with retry visibility, resumable multipart handling, and clear completion summaries.

Sync planning

Review dry-run diffs before execution so replacements and deletes stay explicit instead of hidden in automation.

Preview and delivery

Preview supported assets, generate signed URLs, copy public URLs, and purge cache paths from one workflow.

Read docsView beta pricing
R2 Desk Pro
Scroll or click tabs
Bucket browser

Global search, prefix shortcuts, folder downloads, and object details.

productionmedia-assets
Search the entire bucket
4parallel uploads
32 MBmultipart threshold
Fastbucket-wide search
NameSizeModifiedStatus
marketing-assets/----folder
release-notes/----folder
launch/hero/r2-desk-pro-hero.webp1.8 MBMar 6, 2026ready
release/R2DeskPro_0.1.0_x64-setup.exe84.2 MBMar 6, 2026synced
Interactive preview: browser, transfers, sync, and cost workflowsDesktop app / production-grade UX
Object details

Launch image asset

Typeimage/webp
URL modesigned + public
Cache-Controlpublic, max-age=3600
  • Preview inline
  • Copy signed URL
  • Purge cache on publish
3desktop platforms shipping
0telemetry collected
TLSbackend-only R2 operations
Fastparallel transfers with retry
Feature stack

The R2 workflow layer the dashboard still does not give you.

The product is not positioned as a thin browser wrapper. It is the local operations layer for Cloudflare R2: bucket work, sync, preview, URL tooling, cache actions, transfer visibility, and storage intelligence.

Positioning

Built for actual storage workflows: uploads, previews, sync plans, URL tooling, and operator visibility.

Browser

Desktop-native bucket operations

Browse buckets and prefixes, rename and move objects safely, inspect metadata, and work with Cloudflare R2 like a serious storage client rather than a console tab.

Core workflowBuckets / prefixes / objects
Audience fitDeveloper and operator workflows
  • Bucket-wide search instead of page-limited filtering.
  • Folder actions, bulk selection, and object detail from one view.
  • Rename, move, delete, preview, and URL tooling without context loss.
Workflow

Move from bucket management to delivery operations.

The value is not just listing objects. The value is controlling storage, delivery, and transfer reliability from one app with enough visibility to trust the result.

Operator fit

The product replaces context-switching between Cloudflare dashboard tabs, scripts, and ad hoc file browsers.

01
Connect

Connect profiles once

Save Cloudflare R2 credentials to the OS keychain, validate access, and switch between environments without re-entering secrets.

Operator resultProfiles verified and ready
  • Profiles stay reusable instead of being recreated for every environment.
  • Credential validation happens before the user trusts the connection.
  • Switching between environments becomes operational, not fragile.
Security

The credential asset is treated like the product risk it actually is.

R2 Desk Pro is built around the real security boundary: credentials with read, write, and delete access to storage. Backend-only operations, local vault gating, and OS keychain storage are baseline behavior, not optional polish.

Vault

Vault lock and command gating

Operational commands stay blocked until the local vault is unlocked.

Primary guardrailLocked means non-operational
  • The vault is a real gate, not a cosmetic lock screen.
  • Operational commands are blocked until local unlock succeeds.
  • The product treats active credentials as the core asset to defend.
Runtime posture

Trust model stays legible at a glance.

Local-first / desktop-native
vault statusunlocked locally
credential storageos keychain only
r2 requeststauri backend
transporthttps only
license verificationlocal signature check
analyticsdisabled by default
Pricing tiers

Three tiers for different stages of adoption.

Beta is open at $25 per platform for the first 250 users on Windows, macOS, and Linux, with free updates for the first year only. Pro and Enterprise are already positioned here so buyers understand the commercial path, but those tiers are not open yet.

Offer shape

Beta is open now, Pro is the recommended long-term tier, and Enterprise stays visible as the future team path.

Beta Access
Open now
$25
per platform / free updates for the first year only
Windows: first 250macOS: first 250Linux: first 250
  • One platform seat during the beta program
  • All beta builds for your platform
  • Free updates for the first 12 months from purchase
  • Direct product feedback loop during beta
  • 7-day refund policy
Join beta
Pro
Recommended
$59
single-user commercial license / launch details coming soon
  • Permanent single-user license positioning
  • Commercial release builds outside the beta cap
  • Upgrade path after the beta window ends
  • Pricing and license terms will be published before launch
Coming soon
Enterprise
Coming soon
TBC
team rollout, procurement, and enterprise support track
  • Team procurement and deployment planning
  • Centralized purchasing and commercial support path
  • Enterprise-friendly rollout and update handling
  • Handled separately from the public beta and Pro launch
Coming soon
Documentation

Documentation that closes the support loop before it starts.

The docs are part of the product surface. Setup, operations, security, release workflow, and support standards need to be clear enough that users can resolve setup drift before it ever becomes a support request.

Operator baseline

The docs section is the client-facing manual for setup, troubleshooting, release workflow, and day-to-day operation.

Docs hub

Documentation hub

Task-based product docs for setup, operations, security, release workflow, and support.

CoverageSetup / operations / security / release
Use casePrimary product path
  • Start from the docs hub when you need the right guide faster than search.
  • The hub groups setup, operations, security, release, and support in one place.
  • It is the top-level manual for the shipped product, not a generic content listing.
Open resource
Docs hub

Documentation hub

Task-based product docs for setup, operations, security, release workflow, and support.

CoverageSetup / operations / security / release
Quickstart

Quickstart

The shortest path from installer to working bucket workflow, including first-run smoke checks.

Time to first successInstall / unlock / validate / upload
Troubleshooting

Troubleshooting

Concrete fixes for profile validation, uploads, build/runtime setup, and local environment issues.

Failure handlingAccessDenied / upload / build / local runtime
Support

Support standard

Exactly what support expects before a report is treated as actionable.

Evidence baselineVersion / OS / repro / docs followed
Releases

Release notes

Track shipping builds and download artifacts directly from GitHub Releases.

Delivery pathCurrent release channel
Legal

License agreement

Commercial terms for R2 Desk Pro.

PolicyCommercial license terms
Legal

Privacy policy

Local-first handling of credentials, logs, and diagnostics.

PolicyLocal-first privacy posture
Legal

Refund policy

Refund window and purchase terms for commercial licenses.

PolicyPurchase and refund terms
Support baseline

Good support starts with evidence and reproducibility.

Reports without version, environment, repro steps, and the docs page already followed are incomplete. This is the line between product support and avoidable setup drift.

  • Version from the About panel
  • Operating system and install type
  • Exact repro steps and expected result
  • Actual result with redacted evidence
  • The docs page already followed
Product FAQ

Questions buyers ask before they trust a Cloudflare R2 desktop client.

These are the recurring product questions behind evaluation and purchase decisions: platform support, local credential handling, transfer workflows, and how quickly the app gets a new operator to a working Cloudflare R2 setup.

What is R2 Desk Pro?

R2 Desk Pro is a desktop-native Cloudflare R2 client for Windows, macOS, and Linux. It gives developers and operators a real GUI for browsing buckets, running uploads and downloads, planning sync jobs, previewing assets, and generating delivery URLs.

Does R2 Desk Pro store Cloudflare R2 credentials locally?

Yes. The app is designed around local-first credential handling. Secrets stay in the OS keychain, operational requests are executed by the desktop backend, and the product ships with no telemetry pipeline by default.

Can I upload, download, and sync Cloudflare R2 buckets from the app?

Yes. R2 Desk Pro covers bucket browsing, parallel transfers, resumable multipart uploads, folder downloads, preview-first sync planning, signed URLs, and cache-purge-aware delivery workflows for Cloudflare R2 operators.

Which operating systems does R2 Desk Pro support?

The current product and docs support Windows, macOS, and Linux. The docs hub includes platform-specific setup notes, runtime prerequisites, installer paths, and troubleshooting guidance for each OS.

How do I get started with R2 Desk Pro?

Start with the Quickstart guide. It covers install, first-launch vault setup, profile validation, a first bucket smoke check, and the shortest safe path from fresh install to a working Cloudflare R2 workflow.

Download

Get release builds and start testing the real product.

Beta releases are currently delivered through GitHub Releases while direct commercial fulfillment is finalized. Quickstart walks you through install, first launch, profile validation, and a first working bucket check.

View release buildsRead quickstartTalk to us about team licensing
Support standard

Support starts after the docs, not instead of them.

If the issue is real, the docs let you prove it. Version, operating system, exact repro steps, and the documentation page already followed are the minimum baseline for a useful report.

Expectation

Good support starts with reproducible evidence. The reporting baseline is visible before a request is submitted.

Before support

Bring reproducible detail.

  • Version from the About panel
  • Operating system and install type
  • Exact repro steps
  • Expected and actual result
  • Redacted screenshots, activity, or transfer evidence
Full reporting standard
Reference the docs first

A useful support request cites the exact documentation page followed before the behavior diverged.

Read the support requirements
Version and environment are mandatory

Include the app version, operating system, and whether this is a release installer or a source build.

Read the support requirements
Support needs reproducibility

If the issue cannot be reproduced from your steps, there is nothing meaningful to debug.

Read the support requirements
Secrets stay redacted

Bucket names and object keys are useful. Secret Access Keys, Cloudflare tokens, and live presigned URLs are not.

Read the support requirements