Blog · Swipe file · 8 min read

What is a swipe file (and how to build one)

A swipe file is a personal library of copy and marketing examples you study and reuse. This guide covers the definition, swipe file examples worth saving, and a workflow that beats screenshot folders.

What is a swipe file?

A swipe file is a curated collection of marketing and copywriting examples: headlines, emails, ads, landing pages, sales letters, and more. "Swipe" doesn't mean plagiarize. It means you save work you admire, analyze why it works, and adapt the underlying pattern to your own offer.

Traditional swipe files were physical folders of mailed ads. Today most swipe files live on hard drives, Notion pages, or Pinterest boards. The format changed; the purpose didn't: compress years of copywriting craft into examples you can reference when you write.

Who uses swipe files?

  • Copywriters study hooks, offers, and proof blocks before drafting controls.
  • Marketers track competitor positioning, onboarding flows, and campaign creative.
  • Founders collect GTM inspiration while researching launches.
  • Students and essayists sometimes use the same habit for rhetorical moves and structure, not just ads.

If you read the web for a living, you already have the raw material. The question is whether your swipe file is organized enough to help on deadline.

Swipe file examples worth saving

Strong swipe file examples include:

  • Headlines with a clear mechanism (curiosity, specificity, challenge).
  • Subject lines that earned their open rate.
  • Offers & guarantees that reverse risk.
  • Proof blocks: testimonials, numbers, demonstrations.
  • CTAs that move without hype.

Browse annotated direct mail examples for classic patterns, or see our swipe files for copywriters workflow for a full Capture → Find → Use loop.

Why most swipe files become graveyards

A folder of screenshots is not a swipe file. It's archive without retrieval. Common failures:

  • No note on why the example works.
  • No source URL, so you can't verify context later.
  • No tags, so you can't filter by format (#email, #landing-page).
  • No search, so you scroll instead of write.

The fix is simple but disciplined: every save gets a quote, a one-line annotation, a tag, and a link.

How to build a swipe file step by step

  1. Capture on the live page. Save the headline or paragraph where you found it, not a paste that lost the URL. Tools like Gleanit highlight text in the browser and attach the source automatically.
  2. Annotate immediately. Name the mechanism: curiosity gap, social proof, urgency, specificity. Future-you is lazy; present-you is not.
  3. Tag by format and project. Use tags like #hooks or #vsl and projects like "Q3 launch" or "newsletter relaunch."
  4. Search when you write. Pull up five relevant examples before you draft. You're not looking for copy to steal, you're looking for patterns to combine.
  5. Prune quarterly. Delete duplicates and weak saves. A swipe file is a working library, not a museum.

Swipe file tools: folders vs. libraries

Spreadsheets and screenshot albums work at small scale. A real copywriting swipe file needs full-text search across notes and quotes, plus projects for each client or campaign. That's the gap Gleanit fills: browser capture, inline notes, tags, and search in one library.

Related: if you curate research beyond ads, see our guide to a content curation tool for reuse, not hoarding.

Quick FAQ

Is a swipe file the same as a mood board?

Mood boards skew visual and brand-led. Swipe files skew language, structure, and persuasion. You can keep both; copywriters live in the swipe file.

How many examples do I need?

Start with twenty great saves across five formats. Depth beats volume. Twenty annotated examples outperform two hundred mystery screenshots.

Can teams share a swipe file?

Yes, with shared projects and consistent tagging. The annotation is what makes sharing useful, otherwise teammates just see images without insight.

Save your first swipe file example today

Find one headline you love, capture it with a note, tag it #hooks. That's a working swipe file.

Add to browser