Most swipe files are a folder of dead links. You clip the post, the text survives, the image quietly expires a few months later, and the thing you actually wanted to study is gone.
The swipe file that rots
The save button feels like progress. It is not.
Six months in, you open the folder and it is a list of titles. You remember one of them had a chart whose shape you wanted to steal. You cannot find it. When you finally do, the image is a gray box with a broken-link icon.
Here is the reframe that fixed this for me. A swipe file is not a collection. It is a retrieval system. Most people build the collecting half and stop, because collecting is the part that feels good.
What a clip actually saves, and what it quietly drops
I use the Obsidian Web Clipper. It is good at its job. It keeps the body text, the author, the date, and the source URL, and it drops all of it into my vault as a markdown file I own.
Here is what it does not keep. The image.
The clipper hotlinks the picture back to the platform's CDN. On LinkedIn those URLs carry an expiry parameter baked right into the query string. Nothing looks broken on the day you save it. That is the trap. A few months later the link is dead, and the post you saved specifically because of its chart is now a post with no chart.
That is the piece you most wanted. On a carousel, the image is the entire artifact and the text is just a caption. Losing it means you saved the wrapper and threw away the thing.
Capture into the place your agents already read
Whenever I save something now, it lands as a file in the vault, not a bookmark in an app I do not control.
One file per post, in a Sources folder. The URL and the author in the frontmatter. A separate to-clip list for the ones I catch on my phone and cannot process properly yet.
The rule underneath is small and it matters more than it looks: capture into the same place your agents already read. A bookmark in a browser is invisible to everything else you have built. A markdown file in the vault is readable by every routine you run, today and the ones you have not written yet.
That single decision is what turns a pile of saves into something a machine can work on.
Download the asset on the day you capture it
This is the move that actually stops the rot, and it is almost embarrassingly simple.
Pull the image down to a local media folder on the day you clip it. Not later. Later does not exist. Later is where good intentions go to expire alongside the CDN link.
The tradeoff is honest and small. You spend a little disk, and in exchange your swipe file still works when the source is gone. I would make that trade every single time.
If you only take one thing from this post, take this one. Everything else is refinement.
Write a craft note, not a summary
Capture without analysis is just hoarding with extra steps.
I run a routine every morning that reads the new clips and writes a structured note on the craft. Not what the post said. What the post did.
That distinction is the whole game. A summary tells you the topic, which you already knew, which is why you saved it. A craft note tells you the mechanism: how the open earns the scroll, what shape the structure is, how the closer lands, what pattern the whole thing belongs to, and whether that pattern is reusable in your lane or only works because of who wrote it.
A summary is a receipt. A craft note is a blueprint.
What to write down so it is still useful in a year
Keep the fields tight. Long templates never get filled in. These are the ones that carry weight.
The hook shape. Not the hook itself, the shape of it. Does it dare the reader, name a number, invert something they already believe. Shapes travel between topics. Hooks do not.
The structure. Tiered list, audience-split open, receipts-then-fix, whatever it is. Name it, so you can reach for it later without rereading the whole post.
The closer, and the one line you would actually steal.
And this one almost nobody bothers with: where the top comments landed. That is free audience research, run on someone else's post, at their expense. The comments tell you what the audience actually cared about, which is frequently not what the author thought they were writing about. I have gotten more usable signal from comment sections than from the posts above them.
Keep the source anonymized. The note is about the craft, not the person.
I keep a template with exactly these fields and nothing else. If you want it, it goes out with the newsletter.
Capture is cheap. Retrieval is the product.
Every post you save is a bet that some future version of you comes looking for it.
The bet only pays if the thing you find is readable, structured, and still has its pictures.
Build the retrieval half, or stop saving.
