Guide
How to build a visual library
Everyone who works visually accumulates references. Very few people can find the right one at the moment they need it, which means the collection is decoration.
A library earns the name when a search takes less time than starting over.
01 · Step one
Capture broadly, judge later.
Curating at capture time is a mistake for the same reason filing is: you don't yet know what the reference is for. The value of a saved image is often invisible until the project that needs it exists.
Save anything that produces a reaction. Volume is fine if retrieval works; it's only a problem when retrieval doesn't.
02 · Step two
Describe visually, not thematically.
The instinct is to file by project: onboarding, pricing, brand. But you don't recall a reference by project. You recall it by appearance: the dark one with the huge serif, the layout with the sidebar, the muted photography.
If you tag at all, tag for appearance. Colour, density, typography, medium, mood. Those are the terms your future self will actually use.
- Colour and tone
- Dark, warm, monochrome, high contrast.
- Type
- Serif, condensed, oversized, editorial.
- Structure
- Grid, sidebar, single column, split screen.
- Feeling
- Calm, dense, playful. Vague, but it's what you'll search.
03 · Step three
Make it browsable, because you'll recognise before you recall.
Visual memory is recognition-heavy: you can't describe the image, but you'll know it instantly. That makes a fast, dense grid more valuable than a perfect search box.
Whatever you use, optimise for scanning a hundred thumbnails in a few seconds. Anything that hides images behind rows of text is working against you.
For visual work, recognition beats recall. Design the library for the eye.
04 · Where Shelf fits
A visual library that also reads its own contents.
Shelf keeps references in a visual library you can scan, while reading the text inside each image and writing a short local description of what it shows. Related references gather into collections by shared subject rather than by a folder you made.
It's not a full digital asset manager: there's no team library, no shared tagging workflow, no design-file versioning.
Next thought
The same method scales up to research, where the stakes are higher.
How to organize researchIf 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.