Why Tags Beat Folders for Screenshots

Screenshots are the worst-case scenario for folders. Consider what a screenshot actually is: a file named Screenshot 2026-06-30 at 14.02.11.png, captured in two seconds, about several things at once, and destined to be needed at some unknowable point months from now. Every property of that file fights the folder model.

Why folders lose this fight

The filename tells you nothing. A photo of your dog is recognizable in a grid. A screenshot of a pricing page looks like forty other screenshots of pricing pages until you open it. Folders rely on you knowing where you put something; screenshots give you no handle to remember them by.

One screenshot, five categories. You screenshot a confirmation email with a nice illustration. Is that email-design, illustration, microcopy, onboarding, or competitor-x? It’s all five. A folder forces you to amputate four of those facts — and whichever one you keep won’t be the one you search for later. This is the structural argument in full in tags vs folders, and screenshots are its sharpest case.

The volume is relentless. You don’t take one screenshot a week; you take ten a day. Any system that requires a filing decision at capture time dies within a month, because the decision cost gets paid ten times daily. Tags let you capture now and label in a quick weekly pass — the decision moves to when you have attention for it.

Capture happens on the wrong device. Half your screenshots are taken on your phone, where nobody in history has ever maintained a folder tree. A tag-and-search library tolerates a messy inbox; a folder hierarchy doesn’t.

The tag model, in one paragraph

Give each screenshot two to four tags describing what you’d search for: the pattern (pricing, empty-state), the quality that made you save it (playful, data-dense), maybe the source (linear). Don’t file it anywhere. When you need it, you search — and because a screenshot carries all its facts instead of one, any of them finds it. The retrieval test: think “that pricing page with the toggle” and have it on screen in under ten seconds.

Two rules keep this from sprawling: use a small, fixed vocabulary you reuse (more on that in how many tags should you use), and skip tags that apply to everything — if your whole library is screenshots, a screenshots tag is dead weight.

Where Kelu fits

This is the exact model Kelu is built on. Screenshots go in from the iPhone share sheet or a drag on the Mac; each one carries as many tags as it needs; search does the finding — and the same library is on your iPhone, Mac, and the web, so the screenshot you took on the train is on your desktop when you sit down. The first 2,500 items are free.

If your camera roll is already 90% screenshots, start with a tagging system for screenshots — it’s the practical version of everything above.