Copywriters have kept swipe files for a century: folders of ads that worked, to study and borrow from. Designers do the same thing, they just rarely call it that. Your screenshots folder is a swipe file with no index. This is how to build one with an index.
What a swipe file is for
A swipe file is not a collection of things you like. It is a collection of things you might use. The difference is the note. Every item in a good swipe file carries a sentence about what is worth borrowing: the way the pricing toggle handles annual savings, the spacing rhythm on a long marketing page, the empty state that tells you what to do next.
That sentence turns admiration into a tool. Without it you have a moodboard. With it you have a design swipe file.
What to put in a UI swipe file
Organise your saving around the problems you keep solving, not around aesthetics. Most product designers end up with clusters like these.
- Onboarding and first-run screens.
- Empty states and zero-data screens.
- Pricing pages, especially how tiers and toggles are handled.
- Data tables: density, inline editing, filters, pagination.
- Settings and preferences layouts.
- Error, loading and success states.
- Navigation on small screens.
- Type pairings and spacing systems you want to try.
- Copy: microcopy, button labels, confirmation wording.
You do not build these as folders. They are the kinds of things you save, and the tags and notes make them findable as groups later.
How to capture into it
Two rules. Capture the screenshot and the link together, and capture in one click. Anything slower and the swipe file stops growing within a month. A browser extension is the standard answer; we compared them in Chrome extensions for designers, and for full pages there is how to save a website design. Mobile screens need their own route, covered in saving UI inspiration from mobile apps.
How to make it searchable
This is where digital swipe files beat paper ones, and where most digital ones fail. If your file is a folder of PNGs, it is searchable by filename and nothing else.
You want three layers of searchability on every item.
- The text in the image. Recognised automatically when you save, so "Pricing", "Annual", "Start free trial" all become search terms.
- Automatic tags. What kind of screen it is, what style, what colour. Applied on save, correctable by you.
- Your note. The sentence about what is worth borrowing.
A tool that does the first two for you is what makes the third one enough. GetRef does this for designers; mymind does it for a broader mix of content; Eagle does it for large local libraries with some setup. See the best reference saving tools for the trade-offs.
How to use it
A swipe file you never open is a hoard. Two habits keep it alive.
Search before you start. When a new problem lands, describe it to your swipe file first: "settings page with sidebar", "table with bulk actions". Five minutes of looking at how others solved it saves an hour of solving it from scratch.
Review weekly. Ten minutes to skim what you saved, delete what has gone stale, and sharpen notes. We wrote the routine up in a weekly inspiration review.
Swipe file versus moodboard
The swipe file is the whole archive, grown over years. A moodboard is what you pull from it for one project, one client, one presentation. Keep the archive in your reference tool. Build moodboards in Figma or Milanote from what you find there, and throw them away when the project ends. The archive is permanent; the boards are disposable. More on the boards in how to make a UI moodboard.
Common questions
- What is a swipe file in design?
- A swipe file is a personal collection of examples of work you admire and might borrow ideas from: layouts, flows, components, copy, type pairings. The term comes from advertising, where copywriters kept files of ads to learn from.
- How do I organise a swipe file?
- By search rather than by folder. Save each item with its link and a one-line note on what is worth borrowing, let a tool read and tag it, and find items later by describing them. Folders work until an item belongs in two.
- What should go in a UI swipe file?
- Solutions to problems you keep having: onboarding, empty states, pricing, tables, settings, error handling, navigation on small screens. Also anything that made you stop, with a note on why.
- Is a swipe file the same as a moodboard?
- No. A swipe file is the whole collection, kept over years. A moodboard is a curated selection pulled from it for one project or one presentation.
