S3 Presigned URL Alternative: qURL™ vs S3 Presigned URLs
Hand over a file, or let someone use the app that made it.
Start with what the recipient needs. An S3 presigned URL hands anyone who holds it one object in a bucket, reusable until it expires, for up to 7 days. qURL shares the running app or folder on your machine with no upload: a one-time link or an email invitation, sessions that end on time, and revocation one person at a time.
Both answer “give someone temporary access without making it public”, but they hand over different things. A presigned URL is a signed request for one S3 object. qURL lets a person into an HTTP app or file server running where the data already is. Below, the two meet three jobs: a generated export, an interactive dashboard, and a result that has to outlive your laptop session.
Hand over a file from the command line
# 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 30mHow qURL and Amazon S3 Presigned URLs differ
S3 presigned URLs. You upload the object to a bucket, then sign a URL with credentials allowed to read it, with aws s3 presign or an SDK. AWS calls presigned URLs bearer tokens that grant access to those who possess them, and one can be used multiple times until it expires. Expiry is up to 12 hours from the console and 7 days from the CLI or SDKs, and shorter when the signing credentials end first: signed with a role session, the URL expires with the session. S3 checks expiry when a request starts, so a download that began just before expiry keeps going. There is no call that revokes one URL: you revoke the signer’s credentials or tighten the bucket policy, for example with s3:signatureAge or aws:SourceIp.
S3 Access Grants is a different mechanism. It maps IAM principals, or users and groups from your corporate directory, to S3 locations, and an application calls GetDataAccess for temporary credentials lasting 15 minutes to 12 hours. It knows the user, but it serves applications that call AWS, not a recipient holding a browser link.
qURL. Nothing is uploaded. qurl publish registers an HTTP app on your machine, or a static file server you start for a folder, and gives it a CRID. qurl share prints a link that opens once and starts a browser session; qurl access invite lets one named email address in with a passkey. When a session ends, new requests are refused and open requests, streams and WebSockets are cancelled.
S3 presigned URL alternative: S3 serves an uploaded copy to anyone with the URL until it expires; qURL Desktop shares the file from your Mac through a one-time link.
An S3 presigned URL
- You upload a copy of the file to an S3 bucket.
- Your AWS credentials sign a URL for that one object, valid for up to 7 days.
- Anyone with the URL can download the object, as many times as they like, until it expires.
A file shared with qURL Desktop
- The file stays on your Mac; nothing is uploaded to cloud storage.
- qURL Desktop makes a private link with the expiry you choose, one-time use if you want it.
- Revoke the link, or turn Sharing off, and the file stops opening.
First decide: a file, or a running app
- A copy of a finished file (an export, a build, a report): the recipient downloads bytes, and the job is done when the file is on their disk.
- Something live (a dashboard, a preview, a tool that answers queries): there is no object to sign. The recipient needs a session with the app.
- Both: a dashboard with an export button, or a folder of results you are still producing.
A presigned URL covers the first case once the file is in S3. qURL covers the second directly, and the first from wherever the file already is, without an upload.
Three jobs, side by side
| Job | With qURL | With an S3 presigned URL |
|---|---|---|
| A generated export, such as a CSV a script just wrote | Serve the folder on 127.0.0.1, publish it, and send a one-time link. The recipient downloads from your file server. Once they open the link, a forwarded copy is already spent. | Upload it, sign a GET URL for that key, and send it. Anyone holding the URL can download it again until it expires. |
| An interactive dashboard running on localhost | qurl publish http://127.0.0.1:8050, then invite the viewer by email. They use the live app with only a browser. | Not applicable: a presigned URL signs one object request, not a session with an app. |
| A result that must stay available while your laptop is off | Publish from an always-on host you control, such as a server or a container running qurl publish --foreground, and keep minting fresh links, with no upload. | Upload the object; the URL works until it expires. |
Feature Comparison
| Feature | qURL | Amazon S3 Presigned URLs |
|---|---|---|
| What is shared | An HTTP app or file server, by its origin | One object in a bucket, for one operation |
| Upload or copy | None: the data stays where it is | Upload the object to a bucket first |
| Where it is served from | Your machine, or any host you run qurl on; nothing is copied to a cloud bucket | An AWS bucket you create and pay for |
| Publisher setup | The qurl CLI; no account for up to 3 active resources, with links that last up to 24 hours | An AWS account, a bucket, and credentials allowed to read the object |
| What the recipient needs | A browser; an invited recipient also verifies their mailbox and saves a passkey | The URL |
| Reuse | A qurl share link opens once; an invitation brings the same person back | Reusable by anyone who holds it until it expires |
| Expiry | The link at --ttl (24 hours without an account, 30 days with one); the session separately, up to 24 hours | Up to 12 hours from the console or 7 days from the CLI and SDKs, sooner when the signing credentials end |
| A transfer still running at expiry | At the session deadline, open requests and streams are cancelled | Expiry is checked when a request starts; a download in progress continues |
| Revoking one grant | Revoke one invitation; with an account, revoke one link through the API | No per-URL revoke: revoke the signer’s credentials, which ends every URL they signed, or tighten the bucket policy |
| Recipient identified | Invitation: the verified mailbox. One-time link: no, it is a bearer link | No: S3 sees a valid signature, not a person |
| Cleanup | qurl stop or qurl delete; links end on their own | Delete the object; unexpired URLs keep working until then |
Which one to use
Choose qURL to
Hand over a file or a live app from the machine where it already is: no bucket to create, no upload, a link that opens once, a session that ends on time, and access you can take back one person at a time.
Share a file from your Mac with qURL Desktop →
Already sending presigned URLs?
A presigned URL needs the file in a bucket first, and it keeps working for anyone who holds it until it expires. For anything you generate or run locally, such as an export, a report folder or a dashboard, serve it on 127.0.0.1 and share it with qURL: no upload, a link that opens once, and one command to end access.
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 an S3 presigned URL be used more than once?
Yes. AWS says a presigned URL can be used multiple times until it expires, by anyone who holds it. A link from qurl share opens once, so send each person their own.
Does expiry stop a download that is already running?
Not on S3: it checks expiry when a request starts, so a download that began just before expiry continues. qURL’s session deadline cancels open requests, streams and WebSockets; data already delivered stays delivered.
Can I revoke one presigned URL?
Not on its own. AWS documents revoking or deactivating the signing credentials, which ends every URL they signed, and bucket-policy conditions such as s3:signatureAge. With qURL, revoke one invitation, or with an account one link through the API, and everyone else keeps access.
Is the recipient identified?
A presigned URL is a bearer token: S3 sees a valid signature, not a person. S3 Access Grants maps directory users to data, through applications that request credentials. A qURL email invitation admits only the invited mailbox, with a passkey; a qURL one-time link is a bearer link too.
Where do my files live with qURL?
Where they already are. qURL serves the file from your machine, so nothing is uploaded, copied or left behind in a bucket. TLS ends at LayerV, which routes the traffic and keeps none of the content.
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