I save articles but never read them.

If that's you, you're not lazy. Your bookmark app is broken.

The bookmark folder where saved articles go to die has a name in research literature: the read-later graveyard. Studies on read-later behavior consistently show 94% of saved articles are never reopened. The number is the same whether you use Pocket, Instapaper, Raindrop, or native browser bookmarks. The tool is not the problem. The workflow is.

Why saving feels like progress when it isn't

Saving an article is a dopamine hit. The article is captured, the obligation discharged, the loop closed. Reading the article would be the actual work — and your brain has already collected its reward for the "productive" action of saving. This is why your saved-articles count keeps growing while your read-articles count doesn't.

Bookmark apps reinforce this by making saving frictionless and reading optional. There is no expiry, no nag, no surfacing. Articles sit in a folder forever, and the folder grows. After 6 months you have 400 saved articles you can't even remember saving. After 2 years it's 4,000. The bookmark graveyard is the natural endpoint.

The fix is a 24-hour timer on saves.

If a saved article auto-deletes in 24 hours unless you read it or explicitly tag it as "keep", accumulation becomes impossible. The first week is uncomfortable — saves keep disappearing. By week 2-3 your behavior changes: you only save what you actually intend to read, and you read it within a day. The graveyard becomes a reading queue.

This is what Burn 451 does. The 24-hour auto-delete is not a punishment, it's a forcing function. It forces the question every bookmark app avoids: are you going to read this or not?

Related — the user-original-quote landing pages

Frequently asked questions

Why do I save articles but never read them?

Because saving is dopamine and reading is work. Every time you save, your brain registers it as 'done' — the article is captured, the obligation discharged. Reading the article would be the actual work, and the brain has already collected its reward. Bookmark apps reinforce this by making saving frictionless and reading optional. Until something forces the question 'are you going to read this or not?', the saved article will sit in a folder forever.

Is it normal that 94% of saved articles are never reopened?

Yes. Studies on read-later behavior consistently show 90-95% of saved articles are never reopened, regardless of which tool you use — Pocket, Instapaper, browser bookmarks, Raindrop. The number is the same because the problem is not the tool, it's the workflow: indefinite storage with no surfacing layer leads to accumulation, and accumulation leads to abandonment.

What's the fix?

An expiry timer on saves. If a saved article auto-deletes in 24 hours unless you read it or explicitly tag it as 'keep', accumulation becomes impossible. The first week is uncomfortable — saves keep disappearing. By week 2-3 your save behavior changes: you only save articles you actually intend to read, and you read them within 24 hours. The graveyard becomes a reading queue. Burn 451 is built around this principle.

Doesn't that delete useful articles I forgot to tag?

Yes — sometimes. That's the cost of the system. The benefit is that 94% of saves which would have died unread also die unread, but now visibly (deleted) rather than invisibly (still in folder). The 6% of articles you actually want to keep get tagged for vault. After a few weeks the tagging becomes instinctive. The system trades occasional loss for permanent fix of the accumulation problem.

Is this just another bookmark manager?

No. Burn 451 is the opposite of a bookmark manager. A bookmark manager helps you save more. Burn helps you save less and read more. The product mechanic — auto-delete in 24h — is intentionally hostile to accumulation. If you want to save 4,000 articles indefinitely, use Raindrop. If you want to actually read what you save, use Burn.

What if I want to keep some articles permanently?

Tag them as 'vault' before the 24-hour expiry. Vault articles never delete. The vault is queryable via an MCP server so Claude or Cursor can search across your saved articles. The flow is: save → triage within 24h → either finish reading (gone), tag vault (kept), or let it expire (gone). The vault becomes a curated library of articles you actually engaged with, not a folder of articles you meant to engage with.

Try the 24-hour timer.

Free. Chrome + iOS. Watch your reading queue stop being a graveyard.

Start burning →