SReader Blog
Build a Reading Inbox That Survives Every App Shutdown
Saved links are not saved copies. Here is how to capture article text in open formats, store it locally, and read it offline in a library you own.
Build a Reading Inbox That Survives the Next Read Later App Shutdown
Why saved links are not saved copies, what Pocket's closure proved, and a workflow that keeps your articles readable in any app, on any device.
In May 2025, Mozilla announced that Pocket would shut down in July 2025. Readers who wanted to keep their archives had to export them before the service closed. That is what a read later app shutdown looks like from the reader's side: an announcement, an export window, and a deadline.
Every reader who has built a save-for-later list carries the same quiet anxiety. What happens to all of it when the app goes away? Pocket answered that question in public, and the answer was not comforting.
The argument of this post is that permanence does not come from picking the right app one more time. It comes from open file formats stored on your own devices. The workflow has three moves: capture the article instead of the link, archive it locally, and read it offline in one calm library. SReader, a local-first reading app for iPhone, iPad, Mac, and Android, is the reading layer this workflow ends with.
Why every read later app shutdown follows the same script
Read-later apps sit on borrowed ground. The articles live on publishers' servers. Your archive lives on the company's servers. You own neither.
Shutdowns are not bad luck. A free cloud reading list needs an account system, sync infrastructure, and servers that someone pays for every month, indefinitely. The service survives as long as a parent company stays interested, a monetization plan keeps working, or an acquirer keeps the lights on. When any of those change, the script runs the same way every time: an announcement, a short export window, then deletion.
None of this predicts which app closes next. It describes a structural fragility. Trusting a cloud service with years of reading is a bet that its incentives never change, and a bet is not a preservation strategy.
The contrast is worth anchoring on. A folder of files on your own disk has no kill switch. Nobody can announce its end-of-life, because no company stands between you and the files.
A saved URL is not a saved article
Suppose your read-later app never shuts down. You are still exposed, because links rot on their own schedule. Pages get deleted. Sites reorganize, and old addresses start returning errors. Articles get rewritten, trimmed, or moved behind a paywall. The URL you saved keeps pointing at whatever is there now, and eventually at nothing.
The framing worth keeping: a read-later list of links is not an archive. It is a promise that someone else's server will still be there tomorrow. Saved links are not saved copies.
Even a perfectly healthy app cannot rescue you from this. When the source page dies, the saved link dies with it. The app held the address. The publisher held the content. Neither of them consulted you.
So the goal is not a tidier bookmark list. It is a personal link rot archive: a collection where the article text itself lives on your device, in files any application can open.
The Pocket post-mortem: what export actually bought
Mozilla offered an export before the July 2025 shutdown, which was the decent thing to do. Users who acted before the deadline could pull their saves out as HTML or JSON. That is better than nothing, and it is also where the lesson lives.
The exported HTML was flat and unsorted, a data dump that was hard to read offline. An export is an escape hatch, not a reading experience. A library is something you can sit down with, organized the way you think, opening in whichever app you choose. The gap between those two things is the gap between having data somewhere and being able to read it in ten years.
The scramble also exposed the hidden cost of cloud archives: your reading exists as long as the company does, and only in the shape the company permits. If you stay with a cloud read-later tool anyway, ask the due-diligence questions now rather than on shutdown day:
- Can you export your archive?
- Into which formats?
- Will the result actually be readable, with titles and order intact?
A separate guide to moving saved articles after Pocket's shutdown covers where those exports can land, and backing up reading highlights from any reader app is worth practicing before you need it.
The durable workflow: capture content, not links
The fix is a four-step habit. It takes about as long as tapping Save.
- Capture the content itself. When something is worth keeping, extract the article text rather than the address. Reader-mode extraction turns a cluttered page into clean text, and the output should land in an open format: HTML, Markdown, or EPUB.
- Store the files locally. Keep them in a folder structure on your own disk and sync it with a service you control, whether that is iCloud Drive, Dropbox, or any folder sync. The cloud now serves your files instead of holding them.
- Embed the metadata. Title, author, source URL, and date belong inside the file, so the article's provenance travels with the text into any future tool.
- Read offline in a local-first app. The files are the archive. The app is just the window onto them.
Open formats do the long-term work here. Plain text formats remain readable decades later, with no vendor lock-in, no license, and no subscription to outlive. A Markdown file from ten years ago opens today in any text editor. For the web-article side of step one, reading web articles offline without feeding the algorithm goes deeper on capture.
SReader handles the capture step directly: paste an article link and it fetches the text as readable content, ready for offline reading.
Save articles offline permanently: the habit and the folder
To save articles offline permanently, the habit matters more than the tool. Fetch the link or paste the passage at save time, not later. Later is when link rot wins; the page you planned to extract next week may already be gone.
Format follows content. Markdown suits articles and notes, because it is light, searchable, and readable in any editor. EPUB suits books, as an open, reflowable format designed for long text. TXT and PDF cover the rest.
Organize with a folder taxonomy simple enough to browse with no app at all: topic, author, or year, whichever matches how you actually look for things. The test is the Files app or the Finder. If you can find an article there, your system depends on nobody's search.
Put metadata in every file. Title, author, source URL, date: four lines at the top, and future you will know where a text came from even after the original site is gone.
Let your own sync handle backup. A folder of Markdown files copied by iCloud Drive or Dropbox behaves the same with the sync on or off, which is the difference between a cloud that serves your files and a cloud that hosts your library.
The durability test is blunt. Open a saved article in a plain text editor. If you can read it there, it will outlast any company. If you cannot, you are renting.
Own your reading library: the local-first principle
Local-first is a design stance with a practical shape: your data lives on your device, no account is required, and there is nothing for a company to switch off. To own your reading library is to hold the files themselves. SReader's own page compresses the stance into one line: "No account · No ads · No feed · Your library stays on your device."
There is no kill switch for a folder of Markdown or EPUB files. No shutdown notice. No export deadline. No deletion day. The formula is almost boring: open formats plus local storage equal permanence that no shutdown, price change, or acquisition can revoke.
The honest version includes the trade-off. Cloud tools genuinely make multi-device reading easier: one login, everything in sync, nothing to manage. Local-first gives up some of that convenience and takes back durability, privacy, and simplicity. For an archive meant to last decades, the trade is worth making.
The mindset shift matters more than any tool. Apps come and go. The library is the asset; the app is just the current tenant.
The calm reading layer: SReader on a library you own
This is where SReader completes the workflow. It reads the formats a durable archive already uses: TXT, Markdown, EPUB, and PDF. PDF import extracts the text for reading; it does not re-create the original page layout, perform OCR, or convert PDFs to EPUB.
Capture and reading can happen in one step. Paste a passage or fetch an article link, and SReader pulls it in as readable text. Progress and bookmarks stay on-device with no account, so you resume exactly where you stopped, offline, on iPhone, iPad, Mac, or Android.
The reading experience itself is built for calm rather than speed-hype. Word, Line, and Book modes with adjustable pace turn archived articles into focused sessions: faster when the material is easy, slower when an idea needs room. No feed, no ads, and no account screen between you and page one.
Then the part that makes the setup genuinely shutdown-proof. If SReader disappeared tomorrow, your files would remain open-format and readable anywhere. The archive survives the app, which is the entire point.
Still readable in 2036
Pick any article you saved today and run one test: will it open in ten years, in any app, on any device? A link inside someone else's database fails twice, once against the app and once against the publisher's server. An open-format file on your own disk passes by construction.
The chain is short enough to memorize: capture content, not links; use open formats; store locally with your own sync; read offline in a local-first app.
Pocket's lesson, inverted, is to stop hoping the next service lives forever and remove the dependency instead. The next read later app shutdown can take an app you liked. It cannot take a folder you own.
Try SReader and build a reading inbox no company can switch off.