The operator manual for R2 Desk Pro.
Documentation is organized around real product workflows: setup, platform-specific behavior, bucket operations, transfer discipline, preview and delivery tooling, security posture, release workflow, and support.
By platform, by workflow, and by failure mode.
Use the start-here path first. Then branch by operating system, workflow, or failure pattern before you ever open support.
- App version from the About panel
- Operating system and whether this is a release build or source build
- Exact repro steps and the expected result
- Actual result with screenshot or recording where relevant
The shortest reliable path to a working deployment workflow.
Follow this sequence instead of jumping between random pages. It gets a new user from installer to stable operating baseline with the least support debt.
Get from installer to first working bucket operation
Use Quickstart for the shortest safe path: install, unlock the vault, save a profile, and run a first smoke check.
Open stepUse the correct Windows, macOS, or Linux runtime path
Platform notes cover installer types, keychain behavior, local build prerequisites, and OS-specific failure patterns.
Open stepValidate credentials before trusting the profile
Profiles and connections explains bucket-list validation, HTTPS-only fields, cache purge credentials, and delete behavior.
Open stepKnow the reporting standard before something goes wrong
Support and issue reporting defines the evidence bar so defect reports start with version, repro, and the docs already followed.
Open stepWindows, macOS, and Linux are documented as first-class paths.
Platform behavior is documented separately because installers, local build prerequisites, keychain behavior, and failure patterns are not identical across the three supported desktop targets.
If a report depends on the operating system, the platform page is required reading before support treats it as a product defect.
Windows
- NSIS .exe and .msi release artifacts
- WebView2 and Visual Studio build-tool path for source builds
- Antivirus and EDR interference covered explicitly
macOS
- DMG release path and local build distinctions
- Keychain prompts and native file access behavior
- Xcode Command Line Tools path for source builds
Linux
- Deb and AppImage release paths
- GTK/WebKit and desktop keyring dependencies for source builds
- Distro-specific behavior handled as an environment problem first
Find the guide by the job you are actually doing.
The product is not one screen. The docs are organized around real operator tasks: connection setup, bucket operations, transfer execution, preview and delivery, settings, security, and release engineering.
Open the guide for the task in front of you instead of skimming every page and hoping the right answer is somewhere in the middle.
Browse buckets and object paths
Prefix navigation, saved shortcuts, folder semantics, bulk actions, and keyboard shortcuts.
Open guideRun transfers and sync safely
Queue model, retry visibility, multipart behavior, conflict policy, dry runs, and cancellation semantics.
Open guidePreview assets and ship links
Image and text preview eligibility, signed URLs, public URL mapping, cache purge, and estimate-based cost visibility.
Open guideTune the product for daily use
Theme, density, transfer runtime, preview thresholds, URL defaults, cost assumptions, and vault policy.
Open guideUnderstand security and licensing
Vault behavior, keychain storage, HTTPS enforcement, license activation, and update checks.
Open guideBuild, package, and verify releases
Desktop and website commands, installer output, CI expectations, and production build discipline.
Open guideCommon failure paths have dedicated entry points.
The goal is to stop vague support requests before they start. If the issue is recurring, the docs point you to the exact failure tree or operator rule.
A useful docs hub routes users to the right diagnostic path first. It does not ask support to sort setup drift from real defects by hand.
Profile save fails with AccessDenied
Start with Profiles and connections, then Troubleshooting. This is usually a permission issue, not a broken install.
Open pathUploads or downloads behave unpredictably
Transfers and sync covers queue states, retrying, multipart thresholds, summaries, and cancellation semantics.
Open pathPreview, URLs, or purge actions do not line up
Preview, URLs, cache purge, and cost analysis explains file eligibility, mapping rules, and purge requirements.
Open pathThe machine or distro is the variable
Platform setup and environment notes tells you when to treat the issue as Windows/macOS/Linux environment behavior first.
Open pathGetting Started
3 article(s)
Quickstart
Install the app, unlock the vault, add a profile, and complete a first bucket smoke check.
- Desktop prerequisites
- First-launch vault setup
- First profile validation
Platform setup and environment notes
Release artifacts, native runtime behavior, filesystem differences, and local build prerequisites for Windows, macOS, and Linux.
- Release installer types by platform
- Native keychain and dialog behavior
- Local build prerequisites
Profiles and connections
How profile validation works, which inputs are required, and what permissions the app expects.
- Required and optional profile fields
- Validation behavior
- HTTPS enforcement
Operations
4 article(s)
Bucket browser and object operations
Prefix navigation, folder semantics, search, filters, keyboard shortcuts, and object actions.
- Prefix and folder behavior
- Global search and local filters
- Folder actions
Transfers and sync
Upload, download, retry, multipart behavior, folder expansion, and sync plan review.
- Transfer states and summaries
- Conflict behavior
- Multipart and retry behavior
Preview, URLs, cache purge, and cost analysis
How asset preview works, when public and signed URLs differ, how cache purge is enabled, and what the cost view is actually estimating.
- Inline preview eligibility
- Public URL and signed URL behavior
- Cloudflare cache purge requirements
Settings, defaults, and operator preferences
What every settings section controls, which values affect future jobs, and how to set the app up for daily use instead of first-launch defaults.
- General UI settings
- Transfer and sync runtime defaults
- Preview and URL behavior
Security
1 article(s)
Security, vault, and licensing
Vault gating, keychain storage, passphrase behavior, licensing activation, and update checks.
- Vault lock model
- Keychain credential handling
- HTTPS enforcement
Release Engineering
1 article(s)
Build, packaging, and release workflow
Source builds, local quality gates, installer output, website build, and CI expectations.
- Local source prerequisites
- Desktop and website build commands
- Installer output paths
Support
2 article(s)
Troubleshooting
Concrete fixes for the failure modes people hit first: profile save, uploads, build issues, and local environment problems.
- Profile save failures
- Upload and download failure patterns
- Build and runtime setup issues
Support and issue reporting
The support contract for serious users: what to read first, what evidence to include, and what gets sent back.
- What to read before contacting support
- Required evidence checklist
- Redaction rules