The onboarding flow you screenshotted in March is in there somewhere

A UI designer's screenshot folder grows the same way for almost everyone: a pattern worth remembering shows up in some other product, Cmd-Shift-4 happens on reflex, and the file lands in a folder named Inspiration or Reference or, eventually, nothing at all. Six months on, a critique brings up "that empty state we all liked" and nobody can say which app it was from, which means the fifteen minutes spent finding it again is fifteen minutes spent not doing the redesign it was supposed to inform.

Why a flat folder of screenshots stops working around month three

Screenshots do not carry the context that made them worth saving in the first place. The filename is whatever the OS assigned, the app it came from is not written down anywhere the Finder can search, and scrolling by eye works only as long as the folder is small enough to hold in memory. The pattern is identical to every other reference problem on this site, just with a shorter runway: UI screenshots accumulate fast, because capturing one costs a single keystroke, so the point where scrolling stops working arrives sooner than it does for a photographer's or illustrator's folders.

Renaming files by hand does not survive contact with the actual habit of screenshotting mid-browse. What does survive is tagging at the moment of saving, because it costs about the same keystroke and pays off the first time a crit needs "every empty state we've collected, the good ones."

Finding a pattern by what it does, not what it was called

Tag a screenshot for the pattern it demonstrates rather than the product it came from — onboarding, empty-state, error-handling, paywall — and the query line reaches all of it later: type:image keeps it to stills, tag:any:a,b matches either tag, rating:>=4 narrows to the ones actually worth revisiting. AND across keys, OR inside a comma list, no parentheses.

tag:any:micro-interaction has:notes        annotated interaction studies
type:image width:>=2000 -is:favourite      full-resolution, not yet pinned
added:>2026-01 tag:any:dark-mode           this year's dark-mode captures

A term the parser does not recognise renders as free text instead of an error, so a half-remembered word still returns something to narrow down from.

From a shortlist to a board for the review

Drag a shortlist onto a canvas and it becomes a .coii-canvas file, saved wherever the project's other files live. It names the screenshots it uses without copying them, so the board sits beside the folder it drew from and travels with the project if that folder moves to another drive.

There is no sharing link and nothing renders in a browser; a board here is a file you send, and the person receiving it needs Coii Ref installed to open it. If the actual job is a live board five people annotate together during a call, FigJam and Miro do that better than this page pretends to — both are built around several people being on the same board at once, which is not something Coii Ref attempts.

Organising by pattern instead of by the product you took it from

A structure that tends to hold up for design screenshots is subject-first rather than source-first: folders like Onboarding, Empty states, Forms, Navigation, with a tag for whichever product the example actually came from. That answers two different questions from one collection — "show me empty states" and "show me what this competitor does with theirs" — without needing to keep two copies of anything. Neither structure is required; the query line reaches into subfolders the same way regardless of how deep the hierarchy runs.

tag:any:navigation tag:any:mobile rating:>=3    mobile nav patterns worth a look
tag:any:competitor-a -tag:reviewed              this competitor's captures, unsorted

-tag:reviewed assumes a habit of tagging a screenshot once it has actually been discussed in a crit, which turns "have we looked at this one" from a guess into a one-line answer.

Keeping the source written down, since a screenshot never says it

The one piece of context a screenshot genuinely loses on capture is where it came from, and there is no metadata field for that the way there is for a photograph's EXIF. A note solves it directly: write the product name and the flow in the note field the moment the file is saved, and has:notes becomes a search for everything that got that treatment, while an untagged capture from a rushed afternoon is still findable by pattern tag even without one.

Saved views for the question every crit asks again

Certain questions come up in nearly every design review regardless of the project — "show me the best empty states we've collected," "what have we saved on paywalls lately" — and a saved view answers the same question instantly the next time it comes up, because a view stores the text of a search rather than a fixed list of results. A view built once during a slow week off tag:any:empty-state rating:>=4 keeps returning the current best answer to that question as new screenshots get tagged, without ever being rebuilt by hand, and renaming a tag later does not break it, since the view re-parses its query on open rather than storing which files matched on the day it was saved.

What still belongs in the design file, not the search folder

Not every reference image should leave the design file it lives in. A screenshot pasted directly into a Figma frame as an annotated callout for a specific review is doing a job that belongs there — it is part of the conversation about that exact frame, not a pattern worth searching for later. The distinction worth making a habit of is between reference kept for a decision and reference kept because it might matter again: the first stays wherever the decision is being made, and only the second is worth the ten seconds it takes to drop a copy into a tagged folder where it becomes part of a searchable pattern library rather than a one-off annotation nobody will look for again.

Where this stops being the right tool

If the actual need is a shared, real-time canvas that a team edits together — stickies, cursors, a facilitator running a workshop — that is not what this app does at all, and FigJam or Miro is the honest answer, both built specifically around several people on one board at once. And if the collection is mostly about discovering new patterns rather than re-finding ones already saved, Are.na is a better fit for that half of the job — it is a place to browse what other people have collected, which a private folder on a Mac cannot be.

What Coii Ref is for is the part neither of those solves: a screenshot habit that has been running for years, spread across a Mac's worth of folders, that nobody can currently search by anything other than opening the folder and scrolling.

What it costs and what it runs on

$19 once, three Macs, updates included, nothing that renews. The trial runs 30 days with every feature enabled, no card and no account required to start. It needs macOS 11 Big Sur or later, on Apple Silicon or Intel, as two native builds.

The app's entire outbound network activity is a licence check on Activate and a launch-time read of a server's Date header, so a wound-back clock cannot extend a trial. There is no in-app updater, so no update check, and no analytics or crash reporting of any kind.

Past day thirty of an unpaid trial, growing the library — registering a new folder, running the importer, starting an index by hand — needs a licence. Search, tags, ratings, notes, canvases and the folder watcher all keep working permanently on whatever was already indexed.

A screenshot habit that survives a change of design tool

A pattern library built around screenshots does not depend on which design tool made the screens it captured, and it should not depend on which tool you personally use either. Because the files are ordinary images in ordinary folders, tagged by the pattern they show, the collection survives a move from one design tool to another entirely — registering the same folder again after switching tools costs one re-index, not a rebuilt collection.

Working between a personal Mac and a work machine

A lot of UI designers keep a personal pattern-spotting habit going outside work hours and use a separate, work-issued machine for client or product work during the day. Register a personal screenshot folder on a personal Mac and a work folder on the work machine, and each one keeps its own local index with nothing syncing between them and no account tying the two together. Licensing covers three Macs on one purchase, which in practice covers a personal machine, a work laptop and a second seat without paying twice.

What a killed direction is still worth

A pattern collected for a project that got shelved does not become useless just because the project did, provided it was tagged by what it demonstrates rather than only by the project it was gathered for. An empty-state capture saved for a cancelled feature is exactly as useful the next time an empty state comes up on an unrelated screen, found by tag:any:empty-state regardless of which folder it happened to land in when it was first saved.

What a screenshot habit is worth once it is actually searchable

The difference a search-first archive makes is not really about the crit that goes well because a pattern turned up in four seconds instead of fifteen minutes, though that happens. It is that a designer who trusts a folder to be findable later keeps screenshotting, rather than quietly letting the habit lapse because the payoff never seems worth the clutter. A pattern library that nobody trusts to be searchable eventually stops growing, the same way a reference folder does in any other creative field — and the fix is the same one too: an index, rather than a resolution to be more organised next quarter.

Who this actually suits

Someone who has been screenshotting UI patterns for long enough that the folder has stopped being scrollable, and who wants that folder searchable without adopting a hosted tool built for team collaboration they do not currently need. If the actual job is a live workshop board, FigJam or Miro is the more direct answer; for the general version of the search argument without the UI-specific framing, the reference-manager page covers the same ground, and the moodboard page covers what happens once a shortlist becomes a board. A wider shelf of moodboard tools, hosted and otherwise, sits at the round-up.

Thirty days, every feature, no card and no account: download it and point it at whichever screenshot folder has been quietly growing the longest. Tag the ten patterns you reference most often first — that is the search that pays for itself the next time a crit asks for "the good empty states, the ones we all liked."