Idea
Why saving isn't remembering
Every app that lets you save something implies a promise: this will be here when you need it. The file is there. The promise usually isn't.
The gap isn't storage. It's everything you knew at the moment you saved, and nothing recorded.
01 · The moment
Saving happens at your least thoughtful second.
You save things mid-task. You're reading, building, arguing, and something is briefly worth keeping. The save has to cost nothing, so you press the shortcut and carry on.
That's correct behaviour. The problem is that everything which would make the thing findable later, why it mattered, what you were working on, what it was next to, lives in your head for about ninety seconds and then evaporates.
The save captures the artifact and discards the reason.
02 · The asymmetry
You save with your hands and retrieve with your memory.
When you go looking, months later, you don't have the filename, the title or the exact words. You have a shape: it was a dark screenshot, it was around the pricing work, someone sent it to me, there was a diagram.
Almost every tool asks for the opposite: a keyword you never wrote down, or a folder you chose while distracted. The interface is built around the cheap moment instead of the expensive one.
- What you have at save time
- Full context, no time, no intention to organise.
- What you have at recall time
- Plenty of intent, a vague description, and no keyword.
- What most tools ask for
- The keyword, at the exact moment you don't have it.
03 · What would help
A memory has to do the work you didn't.
If saving is going to stay a one-second action, something else has to record the context. Read the text inside the screenshot. Note when it arrived and what else arrived beside it. Write down, in plain language, what the thing appears to be about. Connect it to the other saves that share a subject, a day, a document or a project.
None of that is exotic. It's just work moved off the person and onto the machine, which is the only place it can go if you're honest about how saving actually happens.
04 · Where Shelf stands
This is the entire premise of the product.
Shelf keeps the save cheap and does the describing itself, on your Mac: text read out of images, short local summaries and topics, and connections between saves with the evidence for each connection visible. Later you search the way you actually remember, roughly, and it usually lands.
It isn't magic and it isn't complete. But it is a different bet: that the interesting problem was never storage.
If this idea interested you…
Shelf V3 is out now
Shelf V3 is the current build. Shelf does not use automatic updates, so download the latest build here and install it over your current version.
This is intentional. Shelf is built around a local-first, privacy-focused philosophy. An automatic updater requires additional background processes, network connections, update infrastructure, and another system with permission to modify the app. We prefer to keep Shelf’s network footprint and background activity as small as possible.
Manual updates keep the process explicit: Shelf only checks the internet when a feature actually needs it, and you decide when a new version is downloaded and installed.