Try it ↓ 11 effects
048 Field notes · Build in public

Burn After Reading

Confidential
do not screenshot
Tuesday· 6 min read· self-destructs on motion

You already noticed. The words you just read are on fire - move the mouse, scroll a line, and the page starts eating itself, leaving ash where a sentence used to be. Hold still and it knits back together. That's the whole gag, it took one prompt to build, and it nearly didn't make it onto this site.

Unlocked - read freely. Lock it again

Hit the button to unlock the page - email optional.

01 One engine, any genre

The chips up top all run the same little engine - a hidden "intensity" number that climbs the moment the page loads, degrading the text until it's unreadable, then holding there until you unlock it. Only the destruction changes: fire chars the words to ash, redaction slams black bars over them, the crypto one corrupts them into glitching hex, focus just blurs them soft. Same idea, different metaphor - and the metaphor is doing the selling. A classified file that redacts itself doesn't need to explain why it's gated.

Two details make any of them hit harder, and both are baked in here. The page destroys itself the second it loads - no instruction, no waiting - so the loss is already underway when the reader arrives. And the email field below is the only way back: hit unlock and a wave sweeps the text crisp again, so the subscribe prompt becomes the payoff instead of a popup.

02 Built in one shot, not one week

I didn't hand-code any of this. I described it to an AI design tool in a paragraph - text destroys on motion, reforms when still, a meter, chips to switch the genre - and it built the whole thing as one interactive piece I could tune live in the browser. Minutes, not days. The expensive skill used to be building the effect. Now it's knowing exactly what you want and describing it cleanly - the prompt is the spec, and mine is in the box below.

03 Why it died on the way to my site

Then I tried to put it here, and it flatlined. A design tool exports its own format - a canvas file plus the tool's own runtime - and that bundle is not a web page. Drop the raw export onto a real stack and nothing runs: a dead, static page where the effect should be. The fix is almost insulting in how simple it is: don't transplant the canvas file. Ask the tool to hand you the logic stripped of its shell - one standalone HTML file, no framework, no runtime. It drops straight into a page and works on the first try.

Steal it

Put it on your own site in three steps

01 Paste this prompt into the design tool
Build an interactive blog post where the body text destroys itself as the reader moves the mouse or scrolls, and reforms when they hold still. Drive the intensity off cursor SPEED - a slow drift is a light haze, a fast jerk is full destruction. Add a small corner meter and brighten the call-to-action as the destruction peaks.

Give me a genre switcher with these destruction styles:
- Burn: words char from ink to ember and lift off as embers + smoke
- Redaction: black "classified" bars slam over the words
- Glitch: text corrupts into scrambling hex with RGB-split and scanlines
- Blur: words go soft and unreadable, sharp when still

Each genre swaps its own headline, kicker, stamp, meta line and CTA. Match my brand - fonts and colors: [paste yours here]. Keep it fully legible at rest.
02 Once it's built, ask for a clean export
Now give me this as a single standalone HTML file - no framework, no runtime dependencies. Just HTML, CSS, and vanilla JS in one file I can drop into my site.
03 Drop the file into your site

Save it as burn-after-reading.html and open it to confirm it works. To ship it, paste the markup and the single <script> into your page. On React or Next.js, render it client-side. No build step, no extra packages.

MK Matt Keddie
Operator · Builder · Receipts
This page self-destructs as you read - unlock below to restore it. Switch genres above.
Heat Dormant