How to organise design inspiration you can actually find again

Every designer collects reference images, screenshots and links, and almost nobody keeps a system for them that survives more than a few months. One post on r/UI_Design put it plainly: "I always end up with 30+ tabs/messy screenshots in Figma and lose them all." The same person said they spend two to four hours every time they start a new project just looking for inspiration they already own.

Another thread on the same subreddit was titled "My UX/UI inspo workflow is an organised chaos", which is the honest name most people would give their own setup if asked. This is not a new complaint either. Some version of how to organise reference images has been asked in r/graphic_design every year for at least four, which is worth noticing on its own. If any of the obvious answers actually worked, the question would have stopped coming back.

Below are the real methods people reach for, with the point where each one breaks, and then the principle that holds up regardless of which app you end up using.

Why does organising inspiration always fall apart?

Most systems fail for the same reason. They ask you to make a decision at the exact moment you have the least patience for one. You find an image mid-scroll or mid-deadline, and the tool wants a folder name, a board, a tag or a page picked right then. Skip that step once and the image goes nowhere findable. Skip it fifty times and you have the tab pile the r/UI_Design poster described.

The usual fix is a better filing system: tighter folder names, colour-coded tags, a Notion database with proper properties. Filing discipline can hold for a while under a strict person. It rarely survives a busy month, and a system that only works when you are not busy is not really a system.

Finder folders and tags, tested against reality

macOS lets you tag any file or folder with a colour and a name, right from Finder, no extra app required. Apple's own guide to using tags to organise files on Mac covers the mechanics: click a colour, add a name, click the tag in the sidebar later to see everything filed under it.

It genuinely works for what it is. The trouble starts once a library passes a few hundred images. Tags are colour-first, and most collections outgrow the handful of colours long before they outgrow the categories, so people end up reusing the same red for three unrelated things. A tag also does not travel: email the file, drag it into Slack, or hand it to a client, and the tag is gone, because it lives in Finder's metadata rather than in the file itself. And a tag says nothing about what is inside the image. A screenshot with forty UI patterns on it gets exactly one tag, the same as a screenshot with one.

Figma pages, Notion and Pinterest boards

Figma pages keep inspiration next to the work, which is the appeal. You can drop screenshots straight onto a page inside the file you are already designing in, no extra app to open. Figma's own guide to creating and managing pages describes pages as a way to organise a project's own content, not as a standing library. Search inside Figma matches layer and page names, not what an image shows, and a reference sits inside whatever file you pasted it into rather than somewhere you would think to look for it once that project ships.

Notion can hold images with tags, filters and a proper database behind them, which is more structure than Finder or Figma offer. The honest limit shows up at scale: one practitioner reported that once their inspiration collection grew large enough, Notion simply took a long time to load it. A tool built around text-first databases is not tuned for scrolling a wall of images, and it shows the bigger the collection gets.

Pinterest boards are still the most visual of the four, and free. The catch is who is actually in charge of the board. It lives on Pinterest's platform, under Pinterest's feed algorithm and moderation rules, not yours, so what surfaces when you open a board is partly Pinterest's decision and not only your own filing.

What about a plain folder on disk?

A folder of images on your Mac is honest. Nothing decides anything on your behalf, nothing can suspend it, and it opens on any machine with no login required. That honesty is also its ceiling. Search only matches the filename, nothing groups images by what they actually look like, and an image that genuinely belongs in three projects either gets copied three times or, more often, filed once and never found from the other two places you would have looked for it.

So what actually works?

Across all four methods, the pattern repeats. Whatever asks you to file correctly at the moment of saving loses eventually, because busy people do not file correctly at the moment of saving. The systems that hold up longer share three habits instead, and none of them require buying anything.

Capture without deciding. Save first, sort never if you have to. A tool or a folder that lets you drop something in without picking its permanent home removes the exact decision that causes people to give up.

Let tagging happen on its own. Whether that means naming files after what you would actually search for later, or using software that reads an image and tags it for you, the goal is the same: the description should not depend on you remembering to type it in at the time.

Search instead of filing. A library you can search by what is written in an image, or by what it looks like, forgives a messy folder structure. A library that only offers browsing punishes it.

This is the principle a handful of dedicated visual libraries, Muse among them, are built around: minimise the decision at the moment of capture, and let search carry the weight filing discipline used to.

Muse is one implementation of it. Anything dragged onto it is saved first and filed later if you want. The words inside an image, a screenshot's text, the site behind a saved link, all feed into one search box, and every image is colour-indexed too, so you can search for the dark green thing you cannot describe any other way. None of that depends on you having typed a tag correctly six months ago.

It does not solve everything on the list above. Muse will not stop a project file from getting messy, and it will not follow a reference into an email thread once you have sent it on. It saves what you drop onto it into its own library on your Mac, the same way Eagle and similar apps do, and that library stays open as plain folders you can view in Finder or export back out at any time. What it changes is the one habit that kept breaking above: instead of the accuracy of your filing deciding whether you find something again, the accuracy of your search does, and search is far more forgiving.

The method above works whichever tool you apply it to. Capture without deciding, stop relying on tags you have to remember to add, and pick something with search good enough to trust. Muse happens to be built around exactly that, and it is free to try for 30 days before you decide whether it earns a place in the rotation.