BlogGuide
How to run a swipe file you actually open again
Saving inspiration is easy and finding it later is the whole problem. How to file references so they come back when you need them, and three Mac apps that keep the file on your own disk.
· 5 min read · 3 products
The short answer
Short answer: file by the problem the reference solves, and let the look follow. A folder called pricing pages that you can search in two years beats a board of two thousand screenshots called inspo. Save the source with the shot, tag the job it does, write one line on why it is in there, and prune the file twice a year. The three Mac apps below keep the whole thing on your own disk.
Saving is the easy half. Every designer has a folder, a board, a bookmark bar or a camera roll full of screenshots, and almost every one of them stops opening it after the first month. The file grows, the finding gets harder, and the day you need that one pricing page you saw in March you go back to Google.
The fix is a filing rule, and it costs about a minute per save.
File by the job, and the look follows
A reference is worth keeping for what it solves. A pricing page, an empty state, a footer that folds four columns onto a phone, an onboarding step that asks for one thing. File it under that job, because that is the question you will be holding when you come back. Colour, mood and style are a search a tool can run for you now: two of the apps below index colour and run visual search on the device, so leave the aesthetic to the index and spend your one minute on the job.
Keep the source with the shot
A screenshot with the URL attached is a reference. A screenshot alone is a rumour. Two years on you will want to see how that page evolved, check what the copy said, or credit the designer, and a bare PNG has lost all three. Every capture tool worth using keeps the source URL on the file, and the three below do it by default: Resurf even records which page was behind a screenshot when you took it.
Write the one line
Next to every save, one sentence on what it does well. "Pricing table that puts the annual saving in the header." "Empty state that teaches the gesture." This is the step everyone skips and the step that makes the file yours. A thousand unlabelled screenshots are a gallery. A thousand with a line each are an opinion you can search.
Where it lives: your disk, your iCloud, or somebody else's server
The choice is who owns the file. A board in a web tool is quick to fill and gone the day the tool changes plans or the account lapses, and client work sitting on a third party server is a conversation with the client you would rather skip. A local library takes an hour to set up once and stays yours: plain files in a folder, a database beside them, Time Machine doing the backup. The three apps on this list all take the local route, and one of them syncs over your own iCloud instead of a server of theirs.
The rule that keeps it small
A swipe file works while it stays readable, and readable is a few hundred items, one folder per job. Prune it every six months. Anything that has stayed closed since the last prune leaves, and prune day takes about an hour. The saves that survive three prunes are the ones you actually design from, and there are rarely more than fifty of those. Fifty references with a line each is a taste. Two thousand bare screenshots are a hard drive.
Where to start
The inspiration shelf on the board holds 64 galleries and reference sites, hunted by members and kept only while they still open them in a working week: Footer for footers sorted by type, Webzooo for sites by brand colour, AppShot Gallery for App Store screenshots, Logos & Brands for 2,400 marks. Those are the sources, and the shortlist of them is the design inspiration galleries collection. For the App Store half of the problem there is a separate post.
The three Mac apps below are where the saves go. Each keeps the file on your own disk, each keeps the source on every capture, and each exports back to ordinary folders, which is the test that matters most: a library you can leave is a library you can trust.
A local library with on device AI that reads the text and the colour inside every save
Links, images, screenshots, GIFs, video and notes go into a visible folder on the Mac, and the app tags them, reads the text inside images and indexes their colours, all on the device. Search takes a full sentence or a colour name. Clip from Chrome or Firefox, or drag, paste and hit the screenshot hotkey with the extension closed. It imports an Eagle library, Raindrop, Pinterest boards and browser bookmarks, and exports a plain copy organised by board.
Pros
- $29 once, a 30 day trial with every feature, zero accounts
- On device tagging, OCR, colour and full sentence search
- Imports Eagle, Raindrop, Pinterest and bookmarks, exports plain folders
Cons
- Apple silicon only, macOS 14 and up
- Chrome and Firefox today, Safari still to come
- Sync between two Macs is yours to arrange
Plain files on your disk, synced through your own iCloud, on Mac, iPhone and iPad
Every capture is a folder: a note in markdown, the original file, a small JSON with the source. Command Shift C opens the capture box in any app, a screenshot keeps the page behind it as its source, and search covers article text, words inside screenshots, PDF text and voice transcripts. Sync runs through a private CloudKit database inside your own iCloud, with your Apple ID as the only account in the loop, and the iPhone and iPad apps are free.
Pros
- Free for 50 captures, then $49 once with two years of updates, or $99 lifetime
- Plain files in a folder, a dated zip backup, export everything
- iCloud sync you own, free iPhone and iPad apps
Cons
- Chrome extension today, Safari on the roadmap
- AI summaries need your own OpenAI key
- Visual and similarity search still to come
Capture onto a Figma style canvas, with X bookmarks and Instagram saves flowing in
Drag, paste, screenshot or right click any image in Chrome and it lands in a local library as a real file with the source kept. Bookmarks on X and saves on Instagram sync in by themselves through the extension. Spaces are an open canvas for arranging what you saved into a mood board, and the library runs AI visual search, colour search and auto tagging. It is in public beta, with the 1.0 still ahead.
Pros
- Local files, zero telemetry, the source URL kept on every capture
- X bookmarks and Instagram saves sync in automatically
- An infinite canvas for mood boards next to the library
Cons
- Public beta, version 0.18 as of September 2026
- Chrome extension only, Mac only
- Pricing is published by third parties only, at $4.99 a month or $49 a year, and the site itself stays silent
Questions
How many references is too many?
Past a few hundred the file stops being read and starts being stored, so the working ceiling is about 300, with a prune every six months that removes anything left closed since the last one. The number that matters more is the fifty or so a person actually designs from. A swipe file exists to be opened, and every item in it that goes unread makes the next search slower.
Is a Figma board good enough?
For a single project, yes: paste the shots on a page, write the line beside each, and archive the page with the project. It stops working as the long term file, because a board loses the source URL, the search across years, and the way back to last spring's pricing page among four hundred frames. Keep the board for the project and the library for the decade.
What should I write next to a saved reference?
One line, and it names the job: what the page solves and what it does well. "Onboarding that asks for one field per screen." "Footer that folds four columns into an accordion on a phone." Skip the adjectives, because "beautiful" will match every item in the file two years from now and narrow the search to zero. The line is for the person you will be, holding a specific problem.
Local library or cloud tool?
Local, if the file holds client work or you plan to keep it longer than the tool's business plan. The three apps here keep plain files in a folder on the Mac, Resurf syncs them over your own iCloud, and each one exports back to ordinary folders. A cloud board is faster to start and worth it for a shared team file, with the understanding that the team owns it only while the subscription runs.
