Swipe file: the reference archive that solves the blank page, and the copying line

Swipe file is an old advertising term, from when copywriters kept clippings of print ads that worked. The idea is the same today: keeping a repertoire of tested solutions to consult when you need to solve a similar problem.

It attacks a specific and common problem: the blank page. When you do not know how to open a video, the problem is rarely a lack of creativity; it is a lack of repertoire available at the moment you need it.

On the name, which causes confusion: "swipe" here has nothing to do with swiping a screen. It comes from the informal sense of borrowing, which is why the term carries an ambiguity worth confronting directly, as the last section does.

The temptation is to store beautiful pieces. What returns is storing solutions to problems. Five categories that work:

• Hooks. Openings that made you stop, with the exact sentence copied.
• Structures. The sequence of a carousel that held to the end, described in bullets.
• Covers. Opening slides that worked, and what in them worked.
• Ways of explaining. Analogies and metaphors that made something difficult comprehensible.
• Offers and CTAs. Requests that genuinely made you act.

One detail: store your own too. The pieces that performed best on your account are the best reference available, because they were already validated with your audience.

Here is why most swipe files are useless.

Saving a piece without writing anything produces a folder with hundreds of items nobody consults, because searching them costs more than thinking from scratch.

One line solves it: why did this work? Not "I liked it", but the mechanism. "The hook denies a common belief in the first sentence." "The cover uses a number and a timeframe together." "The explanation uses an everyday analogy."

That note does three things: it makes the archive searchable by problem, it forces you to understand the mechanism rather than admire the result, and it turns the collection into learning.

Worth being direct, because the term carries that ambiguity from its origin.

It is reference to use the structure, the mechanism, the type of approach. Structure belongs to nobody: the hook formula that denies a common belief is used by thousands of people.

It is copying to reproduce the execution: the specific text, the design, the whole piece with another logo. Beyond the ethical question, it does not work, because the original piece won in its context with its audience.

The practical test: if someone who saw the original recognises yours as the same content, you copied. If they recognise it as the same kind of content, you referenced.

• Every saved reference has a line explaining why it worked.
• I store structure and mechanism, not the whole piece.
• The archive is organised by problem, not by author.
• I also store my own best performing pieces.
• I use the structure, never the execution.