How to Save Newsletter Issues Before They Disappear
In March a paid newsletter I had read for three years sent a two line goodbye note, and about six weeks later its archive started returning a 404. I had paid 50 dollars a year for that thing.

In March a paid newsletter I had read for three years sent a two line goodbye note, and about six weeks later its archive started returning a 404. I had paid 50 dollars a year for that thing. Roughly 180 issues disappeared with it, including the one budget template I still opened every quarter. The writer had moved to a new platform and never bothered exporting the old posts.
That is not a freak accident. Out of the four hundred or so feeds and newsletters I keep tabs on, eleven archives have gone dark in the past two years, and only three of those writers gave any warning first. If a newsletter matters enough that losing it would annoy you, the issues need to sit somewhere you control rather than on a domain someone else pays for.
Why newsletter archives go dark so often
Four things kill an archive, and none of them involve anybody acting in bad faith.
The first is a platform move. A writer leaves Substack for Ghost or Beehiiv, imports the subscriber list, and skips the posts because importing 200 old issues with working images is tedious and nobody is asking for them. The second is a lapsed domain. Custom domains renew yearly, and a writer who has stopped caring about the project stops caring about the 14 dollar renewal too. I have seen two archives vanish that way, both still live on the platform's default subdomain, both unreachable from every link anyone had ever shared.
The third is the platform itself shutting down. Revue closed on January 18, 2023, and Pocket, where a lot of people had parked newsletter issues for later, closed its doors in 2025. Both gave an export window. Most people found out after it had closed.
The fourth is the one that surprises paid subscribers. On several platforms the back catalogue is gated behind an active subscription, so the moment your card stops being charged, the issues you already paid for stop opening. You did not lose access to new work, which is fair. You lost access to the 40 issues you had read and wanted to re check, which is not what most people think they are buying. I wrote more about that tradeoff in the piece on whether paid newsletter subscriptions are worth the money.
Decide what is actually worth saving
The common advice here is to keep everything because storage is cheap. I think that advice is wrong, and not for storage reasons. A folder with 4,000 saved issues is a folder you will never open. You end up with the same problem you had in your inbox, moved to a slower place to search.
When I went back through that dead newsletter, I could reconstruct maybe nine issues that genuinely mattered to me from memory and scattered notes. Nine out of 180. The rest were good reading at the time and completely replaceable now.
So use a harder filter. Save an issue if it meets one of these tests: you have already gone back to it once, it contains a number or a price or a date you might need to cite, it includes a template, script or checklist, or it names a person or source you will want to find again. Being interesting is not enough. Interesting is what the newsletter is for.
With that filter, my own capture rate across 60 or so active newsletters runs at about three issues a month. That is a pile I can actually maintain.
Four ways to capture an issue, and what each one costs you
I have used all of these on the same messy Gmail account, and they fail in different places.
| Method | What you end up with | Effort per issue | Where it fails |
|---|---|---|---|
| Gmail label plus filter | The original email, searchable | None after setup | Tied to one account you may lose or close |
| Print to PDF from the web version | A file you own, images baked in | About 40 seconds | Paywalled issues print as the teaser |
| Read later or notes app clipper | Clean text, highlights, tags | About 15 seconds | The app shuts down or changes its export |
| Newsletter to RSS bridge | Full issues inside your reader | None after setup | Reader retention limits, often 30 to 90 days |
The Gmail filter is the one to set up first because it costs nothing to run. Create a label called Keep, then add a filter for each sender you care about with the action Apply label and Never send to spam. Searching label:keep newsletter name later beats searching an inbox of 40,000 messages. It is not a backup, though. It is an index of mail that lives on Google's servers.
Print to PDF is the ugly option that has never once failed me. Open the web version of the issue, not the email, because the email often has tracking pixels and broken layout. Then print to PDF with background graphics switched on. Average file size across my own archive is about 1.2 MB, so 300 saved issues take under 400 MB. That fits anywhere.
The bridge approach, where a service turns an email address into a feed, is the one I use for daily reading rather than for keeping. It is genuinely good at getting newsletters out of email, and I walked through the setup in the guide on reading newsletters in your RSS reader. Just do not mistake it for storage. Most readers trim old entries, and you will not notice until the entry you wanted is gone.
Plain folders beat a clever system
My first attempt at this used a notes app with tags, nested notebooks and a colour scheme. Two years later I could not remember my own tag rules and the app had changed its export format twice.
What survived is boring. One folder per sender. One file per issue, named with the date first in year month day order, then a few words from the subject line, like 2026-03-14-oversharing-weekly-paper-mills.pdf. Date first means the folder sorts itself chronologically in any file browser on any operating system, with no database and no app. I keep a single plain text file at the top level with one line per saved issue, the date, the sender and why I kept it. That last column is the part I would not skip. Six months on, "has the 2024 pricing table" tells me more than any tag ever did.
Put the whole thing wherever your other important files already sync. If your backup habit covers your documents folder, it now covers this too, and you have not added a new thing to remember.
Grab paid archives before you cancel
This is the one piece of timing that actually matters. Before you cancel a paid subscription, spend 20 minutes in the archive while your access still works.
Sort oldest first, scan subject lines, and save only what passes the filter above. On a three year subscription that is usually six to twelve issues and about 15 minutes of printing. If the writer has an official export, use it first. Ghost and Buttondown will hand a subscriber a readable copy of posts they have access to, and Substack keeps a web version of each post that prints cleanly while your subscription is live.
Do the same thing when a writer announces a platform move, even a cheerful one. The gap between "we are moving to a new home" and "the old links stopped working" has averaged about five weeks in the cases I have tracked, and I have never seen an archive come back after it broke. That sample is small, maybe a dozen cases, so treat the five weeks as a rough warning rather than a rule.
If you want somewhere to start this week, pick your three most valuable subscriptions, make the Keep label, and save the five issues you can already name from each. That is under an hour of work and it covers the cases you would actually miss. The rest of the archive discipline can grow slowly, and more ideas for pruning what arrives in the first place are in the newsletters section.
FAQ
Can I get back a newsletter archive that is already offline?
Sometimes. Try the Wayback Machine with the exact post URL, and if that fails, search for the subject line in quotes, since issues often get quoted or reposted elsewhere. For email you still have, check your own account before anything else. Deleted mail sits in trash for 30 days on most providers.
Does saving newsletter issues break any rules?
Keeping a personal copy of something sent to you, for your own reference, is normal. Reposting a paid issue publicly is not. The line I use is simple: my folder, my eyes, no sharing of paid work.
Should I save the email or the web version?
The web version, when there is one. Emails carry tracking pixels, inconsistent layout and sometimes truncated text with a read more link that will one day point nowhere.
How much space will this take?
Less than people expect. At around 1.2 MB per saved PDF, even an aggressive year of 200 issues lands near 240 MB, smaller than a single phone video of a birthday party.
More in Newsletters
Newsletters
How to Find an Old Newsletter Issue You Half Remember
Someone asked me last month for the newsletter that explained why a particular bookshop in Lisbon shelves by publisher instead...
Newsletter Tracking Pixels and How to Block Them
A writer I had corresponded with twice mentioned, in a friendly way, that he could see I had opened his last issue four times...
Newsletters
How to Unsubscribe From Newsletters in Bulk Without Regret
Your inbox shows 4,000 unread messages and most of them are newsletters you signed up for to get a 10 percent coupon in 2021.