Share S3 files without sharing AWS.
Two ways to share an S3 file with someone who doesn't use AWS or Cloudflare: a presigned URL for one-off access, or a workspace invite for ongoing access. S3 Viewer makes both one click — and the workspace invite is revocable, scoped per bucket, and tied to a logged-in user instead of a bearer link.
- Email invite — recipients sign in to a clean file viewer in any browser
- Per-bucket roles: Viewer, Editor, Admin
- Revoke any user instantly — no IAM keys to rotate
A clean browser view for clients, designers, and execs.
Email invites
Send a link; the recipient signs in (email OTP or GitHub) and sees only the buckets you shared. No AWS account, no IAM user, no Cloudflare login, no setup.
Server-side request signing
S3 Viewer signs every S3 call on the recipient's behalf using your encrypted credentials. Your access keys never reach the browser; revoking the user stops their requests immediately.
Read-only by default
Viewers can browse and download but cannot upload, rename, or delete. Drop-in safe for clients, executives, lawyers, and external reviewers.
Presigned URLs for one-offs
Need a single file with no signup? Right-click → Share link generates a time-limited URL signed server-side. Works in any browser; treat as a bearer token.
Encrypted credentials
Your AWS keys are encrypted at rest with RSA-4096 (PKCS1_OAEP, SHA-256), decrypted only in memory to sign requests. Recipients never see them.
Revoke in one click
Pull access without rotating IAM keys. Their session ends, your other teammates keep working, your applications keep running.
Three steps to your bucket.
No agents to install, no infrastructure to manage. Paste credentials and you're browsing.
- 01
Connect the bucket once
Add your AWS S3 or Cloudflare R2 credentials to a workspace. The bucket appears in your sidebar; the credentials stay encrypted on the server with RSA-4096.
- 02
Invite by email
Type the recipient's email, pick the bucket, choose a role: Viewer (read + download), Editor (read + upload + delete), or Admin. They get a sign-in link.
- 03
They open it in any browser
They sign in to S3 Viewer (email OTP or GitHub) and see exactly the bucket you shared — no AWS account, no IAM user, no Cloudflare account, nothing to install.
Common questions.
Direct answers we wish we'd had when picking a viewer.
How do I share an S3 file with someone who doesn't have an AWS account?
Is a workspace invite better than a presigned URL?
Can I let someone view files but not delete or upload?
Can the recipient see other buckets in my workspace?
What happens when I revoke access?
How long can a presigned URL last?
Can I do this with Cloudflare R2?
Step-by-step how-tos.
Share an S3 file
Presigned URL or workspace invite — when each is the right call, and why presigned links can't be revoked.
Invite a teammate
Skip per-person IAM users for human collaboration. Email invite, per-bucket role, one-click revoke.
Granular permissions
The IAM s3:prefix Condition that everyone misses, plus when workspace roles are simpler than IAM.
Other use cases
Multi-cloud
AWS S3, Cloudflare R2, MinIO, B2, and Wasabi — same sidebar, same search, cross-cloud copy when you need it.
Team workspaces
Per-bucket roles, no per-person IAM, and one-click off-boarding without rotating any keys.
Better S3 browser
One-click rename, Tab-autocomplete bucket-wide search, and Cmd-K — focused on the daily browsing layer.