Guide · Azure Blob Storage
A client gave you a container. Someone needs one file from it, today, and you want to take the link back if it goes to the wrong person. Six steps, no desktop app, and the file never leaves the container.
Open app.klarsend.com and choose Create account. There is no email address to enter: a passkey is the account, created by your device's own prompt (Windows Hello, Touch ID, a security key). You are shown a 24-word recovery code once. Write it down somewhere that is not this device; it is the only way back in if the passkey is lost, and nobody at Klarsend can reset it.
If your device cannot bind a key to the passkey, the app asks for a vault passphrase instead. The rest of the guide is identical either way.
Under Connections choose Add, then Azure Blob Storage. Paste the SAS URL, SAS token or connection string, fill in the storage account name and the container name if they are not already part of what you pasted, and give the connection a name you will recognise, such as the client's.
Before anything is sent, the credential is 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 talks to Azure directly, using that credential, and Klarsend's servers are not in the path.
Browsers only let a page call a storage API if the storage account says that origin is allowed. That is a CORS rule, it is set once per storage account, and it is the only configuration this whole flow needs. It grants nothing by itself: every request is still signed with your credential, and recipients of your links never need it because a download is a plain navigation.
The app shows the exact command for your account on its storage help page. With the Azure CLI it is one line of this shape:
az storage cors add --services b \
--methods GET HEAD OPTIONS PUT DELETE \
--origins https://app.klarsend.com https://send.klarsend.com \
--allowed-headers "*" --exposed-headers "*" --max-age 3600 \
--account-name YOUR-ACCOUNT
In the Azure portal instead: open the storage account, then Settings, then Resource sharing (CORS), tab Blob service, and add one row with the two origins above, the methods, allowed and exposed headers *, and a max age of 3600. Azure allows five CORS rules per service; if the account already has five, add the two origins to an existing rule rather than a new one.
The change takes effect within a minute. If a Klarsend tab was already open, hard-refresh it; browsers cache the old answer for up to an hour.
Open the connection. You are looking at the container as it is, folders and sizes included, read live from Azure. Find the file and choose Get link.
Under the options the app shows an egress cost estimate: what Azure will charge you for the downloads, from the file size, the cap and the published rate for the account's region. It is an estimate, not a quote, and it is paid to Azure, not to Klarsend.
Choose Create and copy the link. It looks like send.klarsend.com/f/k3v9x2.
Paste the link into whatever you already use: email, Slack, a ticket. The recipient opens a page with the link's name and its expiry and a Download button, and the file downloads from your container 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 files of 5 GB or more, desktop Chrome and Edge are offered a reliable download that chooses where to save, can pause, and resumes after a lost connection or a closed browser without spending another download from the cap. A folder link lists the files with per-file downloads or a zip assembled in the recipient's browser.
Your plan page lists every link. For each one you see 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 anyone who opens it from then on. Be clear about what that does not do: it cannot recall a download that has already started, and the signed Azure URL behind the short link keeps working until its own expiry, which is why the short link is the thing to share and the direct link is not.
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.