Skip to main content
← All Comparisons

qURL™ vs Cloudflare R2 Presigned URLs

An object on R2’s API domain, or the app on your machine.

An R2 presigned URL is an S3-style signed request for one object: GET, HEAD, PUT or DELETE, valid from 1 second to 7 days, reusable by anyone who holds it, and only on R2’s r2.cloudflarestorage.com API domain. qURL shares the file or app from your machine with no upload: one-time links, email invitations, and sessions that end on time.

R2 speaks the S3 API, so its presigned URLs work much like Amazon S3’s; the broader file-or-app decision is on the S3 comparison. This page covers what is specific to R2, and how qURL handles the same handoff.

Hand over a file from the command line

qURL CLI
# Serve the folder on this machine only
python3 -m http.server 8000 --bind 127.0.0.1 --directory ./export
# In a second terminal: publish it and make a one-time link
qurl publish http://127.0.0.1:8000
qurl share <CRID> --ttl 1h --session-duration 30m

How qURL and Cloudflare R2 Presigned URLs differ

R2 presigned URLs. You sign the URL yourself with an R2 API token’s Access Key ID and Secret Access Key and an AWS Signature Version 4 implementation; generating one does not contact R2. A URL authorizes one operation on one object: GET, HEAD, PUT or DELETE. POST form uploads are not supported. Expiry runs from 1 second to 7 days. Cloudflare says to treat presigned URLs as bearer tokens: anyone with the URL can perform the operation until it expires, and the same URL can be reused. They work only on the S3 API domain, <ACCOUNT_ID>.r2.cloudflarestorage.com, not on a custom domain; for a custom domain, Cloudflare points to WAF HMAC validation on the Pro plan or above. R2’s presigned URL documentation describes no way to revoke one URL before it expires.

qURL. Nothing is uploaded and nothing is signed by hand. qurl publish registers the app, or a file server for a folder, on your machine; qurl share prints a link that opens once; qurl access invite lets one named email address in with a passkey. Revoking one invitation leaves everyone else’s access alone.

What is specific to R2

  • One domain. Presigned URLs answer only on the account’s r2.cloudflarestorage.com endpoint. A bucket served on your own domain needs a different control, such as WAF HMAC validation.
  • Uploads too. A PUT presigned URL lets a recipient upload one object without credentials; DELETE lets them remove one.
  • Not the public bucket URL. An r2.dev public URL is rate-limited and meant for development, with no WAF or Access features.
  • Revocation is not covered. The presigned URL page names no way to revoke one URL. API tokens stay valid until revoked or until a preset expiry.

The rest, reuse until expiry, bearer semantics and an upload before sharing, matches S3.

The same handoff with qURL

  1. Start a file server for the folder, bound to 127.0.0.1.
  2. Publish it with qurl publish: no bucket, no API token, no signer.
  3. Send one person the link from qurl share, or publish with --access invite_only and invite a named recipient with qurl access invite.
  4. The recipient opens it in a browser and downloads the file during the session.
  5. qurl stop <CRID> stops serving; qurl delete <CRID> retires the resource for good.

For a live app, skip the file server and publish the app’s own address.

Hand over a folder
# Serve the folder on this machine only
python3 -m http.server 8000 --bind 127.0.0.1 --directory ./export
# In a second terminal: publish it and make a one-time link
qurl publish http://127.0.0.1:8000
qurl share <CRID> --ttl 1h --session-duration 30m

Feature Comparison

FeatureqURLCloudflare R2 Presigned URLs
What is sharedAn HTTP app or file server, by its originOne object, for GET, HEAD, PUT or DELETE
Upload or copyNone: the data stays where it isThe object lives in an R2 bucket
Publisher setupThe qurl CLI; no account for up to 3 active resources, with links that last up to 24 hoursA Cloudflare account, a bucket, an R2 API token and a SigV4 signer
AddressA qurl.link access link; the app answers on its own qurl.site name<ACCOUNT_ID>.r2.cloudflarestorage.com only; custom domains are not supported
What the recipient needsA browser; an invited recipient also verifies their mailbox and saves a passkeyThe URL
ReuseA qurl share link opens once; an invitation brings the same person backReusable by anyone who holds it until it expires
ExpiryThe link at --ttl; the session separately, up to 24 hours1 second to 7 days
Revoking one grantRevoke one invitation; with an account, revoke one link through the APINot described in R2’s presigned URL documentation
Recipient identifiedInvitation: the verified mailbox. One-time link: no, it is a bearer linkNo: it is a bearer token

Which one to use

Choose qURL to

Hand a file or a live app to one person without a bucket, an API token or a signer to write: a link that opens once, an invitation that names the recipient, and access you can end in one command.

Already sending R2 presigned URLs?

An R2 presigned URL needs the object in a bucket, a token to sign with, and the r2.cloudflarestorage.com domain, and anyone holding it can reuse it until it expires. For files you produce locally or an app you are running, share with qURL instead: no upload, a link that opens once, and per-person revocation.

qURL connects outbound, so you can share your app without opening an inbound port. Keep any other public routes to your app restricted. A link’s expiry controls when it can be opened; an opened session has its own duration. Explore access and revocation.

Frequently Asked Questions

Can I use an R2 presigned URL on my custom domain?

No. Cloudflare says presigned URLs work with the S3 API domain and cannot be used with custom domains; it points to WAF HMAC validation, on the Pro plan or above, for custom domains. A qURL link needs no domain of yours.

Can an R2 presigned URL be reused?

Yes, until it expires, by anyone who holds it. A link from qurl share opens once.

Can I revoke one R2 presigned URL?

R2’s presigned URL documentation describes no way to revoke a single URL before it expires. With qURL, revoke one invitation, or with an account one link through the API, and everyone else keeps access.

Who can open a qURL link?

Whoever holds it, once: with no flags, qurl share prints a single-use link. The documented browser flow starts a session for that browser, which lasts 1 hour by default for an app published from the CLI; another browser on the same public IP cannot use that browser session. A script or agent that opens the link without a browser can be admitted by its network address, which other devices on that public IP may share until the session ends. Keep your app’s own sign-in for anything sensitive. A link admits whoever opens it: the API’s IP and country rules do not apply to the signed links qurl share issues.

Hand over a file or an app without an account

Paste one prompt into your coding agent, or install the qURL CLI and publish the folder or app yourself. No bucket, no upload, no sign-up.

New to qURL? Start at qurl.link

Book a pilot

Tell us what to hide. We’ll scope a pilot.

Enterprise starts with a paid pilot on one application, typically 60 to 90 days, credited in full toward year one if you convert within 60 days. After that, an annual package sized to what you protect, not per seat.