Blog · 10 July 2024

How to build a swipe file in Notion (and where it falls apart)

Set up a swipe file in Notion with a database, a gallery view and the web clipper. Then the honest part: where it stops working, around the few-hundred-row mark.

TLDR

  • A Notion swipe file is a database with a gallery view, a few properties and the web clipper. You can set it up in 15 minutes.
  • It works well for small, text-heavy swipe files, especially if your team already lives in Notion.
  • It gets painful when it’s mostly screenshots, gets past a few hundred rows, or you need the page as it was when you saved it.

Step 1: make the database

  1. New page, call it Swipe file.
  2. Type /database and pick Database – Full page.
  3. Add these properties:
    • Type (select): Ad, Landing page, Email, Social post, Onboarding, Other.
    • Brand (text).
    • Tags (multi-select): whatever you’ll filter by. #pricing, #dark-mode, #good-copy.
    • URL (URL).
    • Why I saved it (text). This one matters more than the others.
  1. Click + next to the default table view and add a Gallery.
  2. Under Card preview, pick Page content or Files & media, so the screenshot shows on the card.
  3. Set Card size to Medium. Small is too small to read an ad.

Now it looks like a swipe file instead of a spreadsheet.

Step 3: getting things in

  • The Notion Web Clipper (a browser extension) saves the current page into your database. It keeps the URL and a copy of the text, not a screenshot.
  • Screenshots: paste them straight into a new row. ⌘ + Shift + 4 on a Mac, Windows + Shift + S on Windows.
  • Emails: forward-to-Notion isn’t built in, so it’s copy and paste, or a screenshot.

Step 4: views that make it useful

  • By type: a gallery filtered to Type = Ad, another for Landing page.
  • Recent: sorted by Created time, newest first.
  • Unsorted: filtered to Tags is empty, so you know what still needs a label.

That’s a perfectly decent swipe file. If yours stays small, and it’s shared with a team who already use Notion, you might never need anything else.

Where it falls apart

0273 · screenshot · words stuck in the image
0370 · lumen.io · pricing · since redesigned
0467 · onboarding · 4 screens
The three kinds of save that give a Notion swipe file a hard time: a screenshot, a page that later got redesigned, and a multi-step onboarding flow.
  • Search doesn’t read your screenshots. A swipe file is mostly images. Search “SSO add-on” and Notion finds titles and text you typed, not the words inside the pricing table you screenshotted.
  • It keeps the link, not the page. The clipper saves text. When the pricing page gets redesigned, your row points at the new one.
  • Galleries get slow. A few hundred image-heavy rows and the gallery view starts to crawl.
  • No order. An onboarding flow is five screens in a sequence. In Notion that’s five rows you hope stay sorted.
  • Nobody tags consistently. #pricing, #Pricing, #price-page. Multi-select lets everyone make their own.

When to move it

If your Notion swipe file is mostly screenshots nobody can search, or it’s past the point where the gallery is pleasant to scroll, that’s when a tool built for it earns its place. The Notion comparison goes through it row by row, including what Notion does better.

Savepad takes the Notion export as a CSV: export the database, import the file, and it fetches every link again with a fresh preview and a full-page snapshot. Then every screenshot gets read with OCR, so the words inside them are searchable.

Starting from scratch? The swipe file template has a folder structure that works in any tool, Notion included. And if you’re still deciding whether you need one at all, what is a swipe file covers the basics.

Join the waitlist