Skip to main content
NullPaste

Burn-after-read pastes explained

What burn-after-read means, when to use it, and how to share a paste that self-destructs after a single view.

A burn-after-read paste self-destructs after a single view. It's the right choice when something should be seen exactly once and never left sitting on a server.

  1. Write your paste

    Add the text or code you want to share once — for example a token, a temporary password, or a private note.

  2. Turn on Burn after read

    Flip the Burn after read switch. The paste will be deleted permanently the first time it is opened.

  3. Share the link with one person

    Send the link to a single recipient. When they open it, they first see a confirmation — "Opening this deletes the paste permanently" — and only after they confirm is the content shown once and destroyed. Reloading the page will not bring it back.

When to use it

  • One-time credentials, API keys, or recovery codes
  • A private message you don't want lingering in chat history
  • A password or secret you want to confirm was received (one view = confirmed)
  • Anything where a second view would be a problem

Good to know

Opening a burn link shows a confirmation first, so link-preview bots and crawlers never consume the view — only an explicit human click does. The remaining risk is human: whoever gets the link first can be the one to burn it, and the reader can copy the content. If only one specific person should be able to open it, combine burn-after-read with a password shared through a different channel.

Frequently asked questions

What happens to a burn-after-read paste after it is opened?
The reader first sees a confirmation screen; once they confirm, the content is shown a single time and permanently wiped from the server. Afterwards the link shows a dedicated "burned" notice — there is no way to recover the content.
Can someone read a burn-after-read paste twice?
No. The paste is wiped on the first confirmed read — concurrent requests cannot both succeed. Any later visit to that URL shows a burned notice, even for the creator.
What if a link preview bot opens my burn-after-read paste?
Preview bots from Slack, Discord, Twitter, WhatsApp, iMessage, and similar apps do not consume the paste: reading requires an explicit confirmation click that bots never perform, and paste responses are never cached. The honest caveat is about humans — whoever holds the link first can be the one to burn it, and the reader can copy or forward what they saw. Add a password if only one specific person should be able to open it.
Can I combine burn-after-read with a password or encryption?
Yes. Adding a password means only the intended recipient can open and consume the paste. Adding end-to-end encryption means the server never sees the content even before it is deleted. You can use all three options at once for maximum security.
What is the difference between burn-after-read and a timed expiry?
A timed expiry deletes the paste after a set time (10 minutes, 1 hour, etc.) regardless of whether it has been viewed. Burn-after-read deletes the paste the instant the first person opens it, regardless of time. You can combine them: if you set both a 1-hour expiry and burn-after-read, the paste disappears whichever comes first.
Is burn-after-read available for free?
Yes. Burn-after-read is available on every paste, no account or subscription required.

Related guides

Create a paste