The collector's fallacy is the quiet belief that saving something is the same as knowing it. You bookmark the article, screenshot the thread, add the book to a list, and feel a small click of progress. Then nothing happens. Christian Tietze gave the habit its name in 2014, and once you've read his description, it's hard to unsee it in your own phone.
I'll start with a confession. Before I built Reminari, I had a read-later queue that ran into the thousands. I had read a small fraction of it. I still felt, every time I added to it, that I was getting smarter.
Where the term comes from
Tietze wrote "The Collector's Fallacy" for zettelkasten.de in January 2014, mostly with students and researchers in mind. His opening line is the whole idea in seven words: "To collect is a reward in itself."
He borrows an older warning from Umberto Eco about photocopies. The student who copies a text, Eco said, has given in to the illusion of having read it already. Tietze points out that bookmarks do exactly the same thing. As he puts it, "kept isn't read."
The photocopier is gone. The habit isn't. If anything it got cheaper: a save now costs a single tap, and most of us do it dozens of times a day.
Why saving feels like progress
Saving closes a loop. You saw something useful, and the vague worry of "I should remember this" disappears the moment you tap save. That relief is real, and it feels the same whether or not you ever come back.
Some research points the same way. In a 2014 study, the psychologist Linda Henkel walked students through a museum and had them photograph some objects and simply look at others. They remembered the photographed ones worse, a result she called the "photo-taking impairment effect". Her explanation was that people rely on technology to remember for them, counting on the camera to record the event.
A few years earlier, Betsy Sparrow, Jenny Liu and Daniel Wegner published a paper in Science that's often called the "Google effect" study. People who expected information to be saved were worse at recalling the information itself, and better at recalling where it was kept.
Put those together and you have the whole problem in miniature. The act of saving tells your brain it can let go. That's perfectly fine, as long as the place you saved it into can actually hand it back.
What the pile actually costs
The obvious cost is time. I don't think that's the real one. The real costs are quieter.
The guilt pile
A read-later list doesn't stay a library for long. It turns into a to-do list you never agreed to, and every unread item is a tiny reproach. Plenty of people stop opening the app altogether, which I wrote about in read-it-later is broken.
Lost retrieval
This is the cost that actually hurts. You saved the thing, so you stopped trying to remember it, and now you can't find it. The address, the recipe, the article with the one number you need for a meeting. Saved, technically. Gone, practically.
Saving twice
When retrieval fails, you save the same thing again, and then a third time. Your library grows while your access to it doesn't. That's how you end up with the four-thousand-screenshot camera roll from digital hoarding: the screenshot edition. Information hoarding rarely looks like greed. It looks like a reasonable person who couldn't find the first copy.
The usual cure, and where I part ways with it
The standard prescription comes from the note-taking world, and it's Tietze's too: stop collecting, start processing. Read the thing, write notes in your own words, connect them to what you already know. Work in short cycles of research and reading so the pile can't build up in the first place.
For a researcher or a writer, that's right, and I'd follow it. If you want to learn from what you read, nothing replaces putting it in your own words. There's more on that in how to remember what you read.
But most of what we save isn't study material. It's a wifi password, a parking spot, a recipe for Thursday, a gift idea, a hotel confirmation, a line from a song. Nobody is going to write a reflective note about a parking spot.
And when you ask people to process every save, saving gets expensive. Expensive capture has a predictable result: people stop capturing. The pile stops being the problem because there's nothing in it, and you've lost the thing you needed anyway.
So here's my version of the argument. The fallacy isn't saving. It's believing that saving is the end of the job.
What actually helps
Know which kind of save it is
Some saves are things to learn: an essay you want to absorb, the argument of a book. Others are things to retrieve: facts and references you'll need once, later, at a specific moment. Saving vs learning isn't a contest. They're two different jobs, and they need different treatment.
Things to learn deserve real attention. Read them soon, and write one sentence about why they matter. Things to retrieve deserve nothing at save time. They just need to come back when you ask.
Keep capture cheap, and make retrieval cheaper
The one-tap save isn't the enemy. A system that makes saving hard, to stop you overdoing it, punishes the wrong moment. Put the effort on the other side: finding something should be easier than saving it was.
Process when you need it, not when you save it
You don't need to tag, file and summarize a recipe the day you see it. You need it the day you cook it. Processing at the point of need means you only spend effort on the saves that turn out to matter, and that's a small share of them.
Ask instead of browsing
Scrolling through a library to find something is the slowest kind of retrieval there is. Describing what you remember, like "that article about sleep and coffee from last spring," and getting it back is much closer to how memory works. That's the idea behind searching by meaning.
Forgive the backlog
If you have a thousand unread articles, you're not going to read them. Archive them all and start fresh. Nothing bad happens. The few that mattered will resurface when you search for them, as long as they're somewhere searchable.
How I try to build against it
This argument is more or less why Reminari exists, so I'll be upfront about the bias.
Capture stays one tap: the share sheet, or a screenshot, which Reminari can add for you automatically. It doesn't ask you to file anything when you save. The app does the remembering instead. It reads the text inside screenshots on your device, keeps links with their titles and previews, and can write a short summary of each item. Later you ask a question in plain language, and the answer comes from your own saves with the sources shown.
What it can't do is make you learn something you never read. For that, you still need the old advice: read it, and write a sentence. Reminari is for everything else you save, the stuff you simply need back at the right moment.
It's Android first, iOS is in active development, and you can join the early access list.
Frequently asked questions
What is the collector's fallacy?
The collector's fallacy is the belief that collecting information, by saving, bookmarking or copying it, is the same as knowing it. Because the act of saving feels like progress, the material often never gets read or used. Christian Tietze described it on zettelkasten.de in 2014.
Who came up with the term "collector's fallacy"?
Christian Tietze named it in a January 2014 post on zettelkasten.de, building on Umberto Eco's warning about students who photocopy texts instead of reading them. It has since become a common idea in personal knowledge management circles.
Is the collector's fallacy the same as digital hoarding?
They overlap. Digital hoarding describes the pile itself: thousands of files, screenshots or tabs you can't bring yourself to delete. The fallacy is the belief that feeds the pile, that saving something means you've dealt with it.
Why do we save things we never read?
Saving relieves the small worry of forgetting, and that relief arrives whether or not you return. Research on photo-taking and on the "Google effect" suggests that when we expect something to be stored, we put less effort into remembering it ourselves.
How do I stop saving things I never read?
You don't have to stop saving. Separate what you want to learn from what you only need to find later, read the first kind soon, and keep the second kind somewhere you can search by description. Then archive the old backlog without guilt.
