← Todos os artigos
Português (Portugal)

Burn after reading: what actually eats a one-time link

Someone sends a burn-after-reading link over Slack. Slack fetches it to draw the little preview card. Ten minutes later the recipient clicks, and the page says the file is gone. Nobody downloaded anything; Slack’s preview fetch did.

That is the reason “burn after reading” is harder to build than it sounds. The internet is full of things that open links on your behalf: chat apps drawing previews, mail gateways scanning for malware, browsers prefetching the page you might click next. If opening the link is the event that destroys the file, machines will destroy it before a human ever sees it.

So here is how ttl.space decides that a file has been read, and what that means when things go wrong.

Opening the page is not reading the file

A burn-after-reading link points at a page, not at the file. The page is plain HTML: a password box and a warning that the file can be downloaded only once. Loading it does not count as a download. You can open it, close it, send it to yourself, let Slack and WhatsApp and Teams draw their preview cards, let a corporate mail filter poke at it, and the file is still there.

The same goes for the small request the page makes as soon as it opens, before you type anything. It fetches the very start of the encrypted file, at most 314 bytes (the header and the encrypted metadata), so that the password check can happen locally. That request is read-only too.

The reason this is safe is not a clever heuristic about bots. It is that the server will not hand over the file to anyone who does not have the password. When you type it, your browser derives the key that decrypts the file, and from that key a download token. The server stores only a hash of that token. A request that arrives without the right token is refused and changes nothing. A preview bot does not have the password, so it cannot produce the token, so it cannot consume the file. It may fetch the page and cache it all it likes. Any request it makes for the file itself is refused. (How the key and the token are derived is described in how the encryption works.)

The moment the file is used up

A one-time file is used up once it has been downloaded whole and the page that downloaded it has saved it. Until then nothing counts: loading the page, typing the password, the small probe request, and also a download that breaks off.

That last part changed in October 2026. Until then the file was used up the moment the first encrypted byte left the server, so a phone that lost its connection at 40 percent lost the file for good. That is what kept happening to people: a train goes into a tunnel, the browser inside a chat app cannot save anything, a disk fills up, and the file is gone with nobody holding it.

Now every download that starts gets a resume ticket: 256 random bits that the server keeps only as a hash, in its database, and that the page keeps in the browser’s own storage, never in a URL. When the connection breaks, the page comes back with the ticket, the download token and the byte where it stopped, and gets the rest from there. Reload the page, or come back hours later in the same browser, and it starts again with the same ticket instead of counting a new download; the ticket works for 24 hours. When every chunk has arrived and passed its check and the file has been handed to the device, the page tells the server, and the server deletes its copy at once.

A client that says nothing, the CLI or a script with curl, uses the file up when the server has sent the last byte. Its own ticket can still fetch what got lost on the way for two minutes, then the copy is deleted.

What that gives up

The old rule had one property the new one does not: nobody could read the file without using it up. The file is encrypted in independent chunks, so a client that receives part of it has that part of the plaintext. Someone who has the link and the password can now download the file and never say it was saved, and the file stays. We accept that, because whoever has both can read the file anyway: the one-time rule was never a defence against them. Three things keep it visible and bounded:

  • One download runs at a time. If two people race for the file, the second waits until the first stops, so a file that a script fetches to the end goes to one of them.
  • At most five downloads can be started, each from its own browser or device. Starting again in the same browser does not count.
  • The download page shows how many downloads have been started so far, so a recipient can see whether someone got there first.
What happens Does it use up the file?
Slack, WhatsApp, Teams, iMessage draw a link preview No
A mail gateway or antivirus fetches the page No
The recipient opens the page and closes it No
The recipient’s browser prefetches the page before they click No
The recipient types a wrong password (checked in the browser, never sent) No
A download breaks off, or the recipient pauses or cancels it No, it carries on or starts again
The page gets every byte but the device does not keep the file No
The file is downloaded whole and saved Yes, and the copy is deleted at once
The CLI or a script fetches the file to the end Yes
The file is never downloaded and the timer runs out It expires anyway

What the recipient sees

The download page for a one-time file says it in plain words: “This file can be downloaded only once: it is permanently deleted from the server as soon as it has been downloaded and saved. If a download breaks off, the file stays and you can try again.”

While the download runs there are two buttons under it. Pause lets the connection go, and Resume carries on from the byte where it stopped. Cancel stops the download, and the file stays. If the connection breaks, the page picks the download up by itself, so a phone that changes networks usually just pauses and carries on. If it cannot, it says the download was interrupted and that the file can still be downloaded.

Opened inside an app, in the browser built into Instagram or Facebook for example, the page first says that such browsers often cannot save files. If the recipient goes on there, it asks at the end whether the file was saved: “No” leaves the file for a real browser, and only “Yes” uses it up.

Where the robots still win

Here is what the one-time rule does not cover.

Burn after reading protects the copy on our server. It does nothing about the copy on the recipient’s device. Once the file is decrypted into their downloads folder, it lives as long as they keep it, and so does any copy they make of it.

The one-time rule is enforced by the token, so whoever has the link and the password is “the recipient” as far as the server is concerned. If you post both in the same channel, anyone who types the password can read the file. Send the link one way and the password another. Chat for the link, a call or a text for the password.

And the audit row the server keeps says that a download happened, when, from which IP address (kept as a keyed hash plus an encrypted copy) and roughly where that address was, and what the browser called itself. It cannot say who. The password itself is never sent to the server, only a token derived from it, so on the recipient’s side there is no account, no identity, nothing to attach the event to. A service that cannot read your files cannot vouch for who read them either; that is the trade.

So if you got a one-time link and the page said the file was gone, one of a few things happened, and none of them was a preview bot: someone with the link and the password downloaded it before you, all five downloads were started, the timer ran out first, or the sender deleted it early, from My uploads or their account page. In every case the fix is the same. Ask the sender for a fresh link.

If you need a signed receipt from a named person, this is the wrong tool. If you need a file to reach one person and then disappear, the rules above are how we keep the robots from burning it first.

Publicado em · Atualizado em .