Save less, read more

Tue, 01 Sep 2026 00:00:00 GMT

About a year ago I built a read it later / archiving service, and I've been its first and most loyal user ever since. Being on the builder side after years of being just a user changed how I see this whole category, so I wanted to share some observations.

"Read it later" usually means saving a post to read some other time. It's baked into every social platform, and most forums have some kind of bookmark or save feature. Then there are dedicated services. Pocket (RIP, shut down after the Mozilla acquisition) and Instapaper focus on saving articles, while Raindrop is more about bookmarking the sites themselves. It exists at the OS and browser level too. Safari has it built in.

Whatever you call it (bookmarking, saving, archiving, read it later), the people who use these features all have one thing in common. Most of them never read the stuff later. Saving scratches the data hoarder itch and feels productive. Reading is the part that actually takes effort. And to be clear, none of this is about storage. Text is basically free to store and grep is fast. The scarce resource is attention, and every unread save adds a little noise when you're deciding what deserves your reading time.

Why? The most fundamental reason is that people don't save things they're actually going to read later. In my experience there are three kinds of saves.

You read something, loved it, and want to archive it
It's reference material you'll want to look up or share later
You're interested but have no time right now, so you save it for later

The first group does fine if they have a system. People who already have their own way of capturing and organizing information use it well, whatever the tool (Notion, Obsidian, plain notes, a spreadsheet). Basically the PKM crowd. Lately the trend seems to be toward tools that connect with AI, since being able to classify, search, and summarize what you've read with an LLM basically gives you a small personal wiki. Retrieval even changes what saving means. When I posted a version of this elsewhere, a commenter pointed out that the question shifts from "will I come back and read this" to "would I want this to resurface when I'm thinking about the topic," and the second framing has no guilt attached. I mostly agree, with one caveat. Resurfacing works best on things you actually read and annotated, because that's when the reminder connects to a real thought. Resurfacing an article you never opened is just a recommendation engine fed by your past impulses.

There's a trap here though. Once you start building a second brain, it's tempting to clip everything that looks vaguely useful, whether or not you'll ever read it. The archive keeps growing, and at some point you can't tell which saves were things you genuinely meant to read and which were just there to round out the collection. A knowledge base full of unread articles you meant to read isn't a second brain. It's hoarding with a nicer UI. (Reference notes you write for lookup, serial numbers, insurance details, maintenance logs, are a different thing entirely. Those did their job the moment you wrote them, and hoping to never read them again is the correct goal.)

Reference material mostly gets processed on the spot. Found a good restaurant? You pin it on a map immediately. A timely article? It goes straight into a group chat or gets posted somewhere. If it's something you'll need later, a lot of people just DM the link to themselves and forget about it. You probably know that one friend who relentlessly shares everything they find interesting. You might be that friend.

The third case (interested, no time, "later") is usually long form stuff like research papers, foreign press articles, blog posts, and long threads. Ironically, this is the pattern that fits "read it later" most literally, and it's exactly where people fail the most.

So if you want read it later to actually work, here's what I'd suggest.

Only save something on the premise that "later" actually exists. Content saved with no idea of when you'll consume it tends to come back as guilt and homework.
Don't save long reads. People save long articles precisely because they have no time, but you'll usually have even less time later. If a long piece is genuinely important and tied to your work, don't file it under "read eventually." Treat it as its own task or small project. If you do GTD, give it the weight of a real task.
Set an expiration rule. For example, everything saved gets consumed within a week, and anything unread after a week gets archived, no exceptions. In my service, I modeled saving after email. Saved articles land in an inbox first. You read from the inbox, then archive. You can set deadline rules too. (For context, I run my email on inbox zero.) While reading you highlight, take notes, and tag, and once something's archived, it has to be easy to search.
Don't use the platform's own save feature. A social feed exists to keep you scrolling, and the save UI is never the main feature. You have to wade through the feed just to reach your saved posts, and by then you're back to doomscrolling instead of reading. Eventually you forget what you even saved. Link rot is real, too. If the original post gets deleted, your save is gone with it. And worst of all, saving is a strong preference signal, so you're just feeding the recommendation algorithm.
Make your own magazine. If you save like a data hoarder (dump everything, filter nothing) you end up spending more time agonizing over whether to read the pile than actually reading it. Instead of stressing over the backlog, think of it as editing your own magazine and do some quality control. The you who saved something and the you who reads it later are different people in different situations, so ruthlessly filter out whatever doesn't hold up on second look. You seek out good food. Do the same with content.
Save writers, not just posts. Good writing comes from good writers, but even good writers aren't good every time. When someone has a consistently high batting average, I subscribe to everything they publish. RSS for blogs, notifications elsewhere. I don't want to miss anything they write. (This is why I built subscriptions into my service.) Writers who are only occasionally great, I archive selectively.
What reads well is what looks good to read. Everyone has a preferred setup. Save on mobile and read on mobile, or on desktop, an ereader, a tablet. What actually matters is how long you can stay immersed. Physical books are great because a book contains only text and affords exactly one activity, which is reading. Ereaders are good for the same reason. In the end, though, it comes down to will. Most of us fill spare moments with short form video. Swap some of that time for your own archive and you trade a little dopamine for content that actually fills you up.
Long videos are long reads. Reread point 2. Short form is mostly not worth saving, but quick tips, recipes, and informational clips can be. Personally I prefer transcribing videos and saving the text. Once you've watched something you rarely need to watch it again, and reading is faster than watching anyway. There are plenty of good transcription tools now, and YouTube often has captions built in, so you can get the text without doing the work yourself.

Social Archive Blog

Save less, read more