Everyone has a folder of screenshots they never open again.

We spent a week talking to designers, writers, and researchers about the moment they decide something is worth keeping. The pattern was almost identical every time: the saving is easy, and the finding is hard. People described desktops full of unnamed images, messages sent to themselves, and browser tabs kept open for weeks because closing them felt like losing the idea.

What surprised us was how little anyone wanted a new filing system. Nobody asked for more folders, stricter naming, or a tidier archive. They wanted the reference to arrive already carrying its own context — where it came from, what it looked like in place, and the reason it caught their attention. That is the problem Clarity is built around.

The questions that shaped the roadmap

One researcher asked why she should have to remember where a screenshot came from when the computer already knows. A designer asked whether a saved reference could keep its annotation attached instead of living in a separate document. Those two questions changed how we prioritised the next release: less time spent on organisation features, more time spent making a single Clarity carry everything it needs.

A short tour

The video above walks through the flow we heard described most often: notice something useful, save it with one shortcut, keep working, and come back later to a library where the reference still makes sense. It is intentionally unremarkable to use. A Clarity tool earns its place by staying out of the way at the exact moment you are concentrating.

We came away with fewer feature requests and a clearer principle: a saved idea is only valuable if it survives the trip back to your desk. Everything we build next is measured against that.