Guide · Amazon S3
The usual S3 answer to "send this file" is either a public bucket, which is a mistake, or a presigned URL that lives in a chat thread until it expires, which you cannot take back. This gives you a short link that you can revoke, with an access log, from a bucket that stays private.
Open app.klarsend.com and choose Create account. No email address: a passkey is the account, created by your device's own prompt. You are shown a 24-word recovery code once. Keep it somewhere that is not this device; nobody at Klarsend can reset a lost passkey. If your device cannot bind a key to the passkey, the app asks for a vault passphrase instead.
Under Connections choose Add, then Amazon S3. Enter the bucket name, its region (for example eu-west-1), and optionally a prefix if you want Klarsend to see one folder rather than the whole bucket.
The wizard then shows the IAM policy to attach to a user: one statement to list the bucket, one to get objects and to request restores of archived ones, both scoped to the bucket or the prefix you entered. Create a user in the AWS console with exactly that policy, create an access key for it, and paste the access key ID and secret into the wizard. It accepts a pasted credentials block too.
Before anything is sent, the keys are encrypted on your device with AES-256-GCM under a key derived from your passkey. What reaches Klarsend's server is ciphertext it cannot open. From here on your browser signs every request to S3 itself, with those keys, and Klarsend's servers are not in the path.
Browsers only let a page call the S3 API if the bucket says that origin is allowed. That is a CORS rule, set once per bucket, and it is the only configuration this flow needs. It grants nothing by itself: every request is still signed with your keys, and recipients of your links never need it, because a download is a plain navigation.
The app's storage help page shows the rule and the commands for your bucket. The rule is one object in the bucket's CORS configuration:
{
"AllowedOrigins": ["https://app.klarsend.com", "https://send.klarsend.com"],
"AllowedMethods": ["GET", "HEAD", "POST", "PUT", "DELETE"],
"AllowedHeaders": ["*"],
"ExposeHeaders": ["ETag", "x-amz-restore", "x-amz-request-id", "x-amz-id-2",
"Content-Range", "x-amz-server-side-encryption"],
"MaxAgeSeconds": 3600
}
In the AWS console: open the bucket, then Permissions, then Cross-origin resource sharing (CORS), and paste the rule into the array. With the CLI, aws s3api put-bucket-cors sets it, but note that it replaces the bucket's existing rules; if the bucket already has rules for another application, add this object to them rather than overwriting. The app's help page has the append variant.
The change takes effect within a minute. If a Klarsend tab was already open, hard-refresh it.
Open the connection. You see the bucket or prefix as it is, read live from S3, with the storage class of each object. Find the file and choose Get link. An object in Glacier or Deep Archive shows why it cannot be linked yet, and you can start a restore from the same row.
Under the options the app shows an egress cost estimate: what AWS will charge you in data transfer out, from the object size, the cap and the published rate for the bucket's region. An estimate, not a quote, paid to AWS, not to Klarsend.
Choose Create and copy the link. It looks like send.klarsend.com/f/k3v9x2.
Paste the link wherever you already talk to the recipient. They open a page with the link's name and its expiry and a Download button, and the file downloads from your bucket in any browser on any device, nothing to install. The page tells them, before they click, that opening it records their device and approximate location for you.
For objects of 5 GB or more, desktop Chrome and Edge are offered a reliable download that can pause and resume after a lost connection without spending another download from the cap. A folder link lists the objects under a prefix, with per-file downloads or a zip assembled in the recipient's browser.
Your plan page lists every link with when it was opened and downloaded, the approximate country, and the browser or device, for seven days. If the link went to the wrong person, choose Revoke: the short link stops working immediately for new opens. What it cannot do: recall a download that already started, or shorten the presigned URL behind the short link, which runs to its own expiry. That is the reason to share the short link and never the direct one.
Free accounts can have ten active short links at a time; expired and revoked links do not count. Premium, EUR 6 a month VAT included, removes that limit and changes nothing else. Cancel any time, and any charge is refundable in full within 14 days. Details on the pricing section.
Get started
Connect it, send a link, revoke it — in under ten minutes, with no card and no email address.
The core stays free. Premium is €6 a month, VAT included — pricing · refund policy.