Attachments have the same problem as passwords in email: they stay there. A signed contract, an ID scan or a private key sent as an attachment is copied into every mailbox and backup along the way. Sending it as a one-time link means there is one copy, encrypted, until the person you meant it for downloads it, and then there is none.
How to send a file once
- Sign in and choose File on the new secret page. You’ll need an account with a confirmed email address.
- Pick the file, up to 25 MB, and an expiry time: 1 hour, 24 hours, 3 days, 7 days or 30 days.
- Add a label for yourself. The filename is encrypted along with the contents, so your dashboard can’t show it. A label such as “signed contract for Acme” is how you’ll tell your links apart. Keep it free of anything confidential, as labels aren’t encrypted.
- Send the link, by copying it or having it emailed to the recipient. It’s only shown this once.
- Keep your own copy. There’s no way to retrieve the file once it’s gone.
Which files can be sent
| Type | Extensions |
|---|---|
| Word, Excel or PowerPoint | .docx, .xlsx, .pptx |
| PNG image | .png |
| JPEG image | .jpg, .jpeg |
| Text, key or certificate | .txt, .csv, .json, .yaml, .yml, .env, .md, .log, .conf, .ini, .pem, .key, .crt, .cer, .pub, .asc, .gpg, .ppk, .xml |
The extension alone doesn’t decide it. The file’s contents have to match, so a program renamed invoice.pdf is refused. Files in the text, key and certificate group must really be text: a key in a binary format is refused, so export it in a text format such as PEM first.
What gets refused, and why
Allowing only “safe” formats wouldn’t do much on its own, because documents are among the most common ways of delivering malware. The danger lies in the active content inside them. So as well as limiting the formats, we refuse:
- Programs and scripts, including Windows, Linux and macOS executables, whatever the file is called.
- Office documents containing macros, and older .doc, .xls and .ppt files as a class. Save them as .docx, .xlsx or .pptx instead.
- PDFs with active content, such as embedded JavaScript, actions that run on opening, links that launch programs and files embedded inside.
- Archives, because nothing can check what’s inside a nested zip.
- SVG images, which can contain scripts despite looking like pictures.
These checks catch common and careless cases rather than a determined attacker, and a dangerous file might still get through. Once a file is stored, not even we can inspect it, which is the same property that keeps it private. Recipients are told as much before they download.
One attempt means one attempt
The file is destroyed as soon as it starts sending, not when it finishes arriving. If the connection drops part-way through, it can’t be resumed. That’s a deliberate choice, since a resumable download would mean “once” quietly became “more than once”. So:
- ask the recipient to download it on a reliable connection, and to leave the page open until it finishes;
- warn them that reloading the page won’t bring it back;
- be ready to send it again if it fails.
When this is the wrong tool
- Several people need the same file. Each link opens once, so you’d upload it once per person. A shared folder with proper permissions may suit you better.
- You’re sending lots of files. Each account has a fair-use ceiling of around 250 MB of files waiting to be collected. Revoking old ones frees up space.
- You need to work on it together. This is for delivery, not for collaboration or long-term storage.
If the file holds other people’s personal data, UK GDPR expects you to keep it appropriately secure. A one-time link helps with how it’s delivered, but whether you should be sharing it at all is a separate question. Our guide to how the encryption works sets out what is and isn’t protected, so you can judge whether it fits.