Read It Later Without an Account: Why Your Reading List Should Live on Your Device

Your reading list reveals more about you than your browsing history. Here's the case for a local-first read-it-later app: no account, no server, and no shutdown that can take your list away.

3 min read

Think about what's in your reading list right now. Probably an article about a health symptom you haven't told anyone about. A guide to negotiating salary, saved on a Tuesday afternoon. Something about the neighborhood you're thinking of moving to. A long read on a political topic you'd rather not argue about at dinner.

A reading list is a diary of your curiosity. It's arguably more revealing than your browsing history, because it's the curated part: the things you cared about enough to keep.

So it's worth asking where that diary lives.

The hidden cost of "sign up to save"

Most read-it-later apps work the same way: create an account, and every article you save is copied to the company's servers. That's how they sync across devices, and for years it seemed like a fair trade.

It comes with three costs that are easy to ignore until they aren't.

1. Someone else holds a record of what you read

Even with the best intentions, a server-side reading list is data: stored, backed up, possibly analyzed, and subject to whatever the company's privacy policy says this year. A breach, an acquisition or a policy change can put it somewhere you never agreed to.

2. Services shut down

Pocket, one of the oldest and best-known read-it-later services, was shut down by Mozilla in July 2025. Omnivore, a popular open-source alternative, closed in late 2024. In both cases users got a deadline to export their data, and anyone who missed it lost their list.

When your reading list lives on someone else's server, its lifespan is tied to their business decisions.

3. Your list is only as portable as they let it be

Exports tend to be an afterthought: a CSV of links without the article text, or without your highlights and notes. Moving between services often means starting over.

What "local-first" means

A local-first app keeps your data on your device as the primary copy. The network is optional: it's used when you ask for it, not as a precondition for the app to work.

For a reading list, that means:

  • Saving stores the article in your browser, not on a server.
  • Reading works offline, because the article is already on your device.
  • Searching runs locally, across the full text of everything you've saved.
  • Leaving is easy, because the data is already yours to export.

How Savely does it

Savely is a read-it-later extension for Chrome, Firefox and Firefox for Android, built local-first from the ground up:

  • There is no Savely server. Not a small one, not an optional one. There's nowhere for your list to be uploaded to.
  • There is no account. Install it and start saving.
  • There is no telemetry. No analytics, no crash reporting, no "anonymous usage statistics".
  • Articles are stored in your browser's own database (IndexedDB), along with your tags, highlights and notes.
  • The network is used only when you act: to fetch the page you're saving, to show that page's images in the reader (which you can turn off), or to sync, if you switch that on.

"But I need it on more than one device"

Fair. Savely's sync is off by default, and when you turn it on, it goes through a place you own, never through us. Today that's a private GitHub Gist on your own GitHub account. Both devices read and write the same Gist, and Savely merges the changes. Here's the full walkthrough, including the privacy trade-offs.

"What if I want to leave?"

You should always be able to. The options page exports:

  • a full JSON backup with every item, the article text, your tags and your highlights, and
  • a bookmarks file in the standard format every browser can import.

Savely also keeps a daily snapshot of your list's metadata (tags, favorites, archive state, dates), so an accidental mass-delete isn't the end of the world.

The trade-offs, honestly

Local-first isn't free of compromises:

  • Your device is the backup. If you clear your browser data without exporting, the list goes with it. Export occasionally, or turn on sync.
  • No web app. You read in the browser where Savely is installed.
  • No iPhone app. Savely runs where browser extensions run: desktop Chrome, Firefox and Chromium browsers, plus Firefox on Android.

For many people those are easy trades for a reading list that nobody else can read, mine, sell or shut down.

The short version

Your reading list is personal. It should work offline, survive any company's business decisions, and be yours to take anywhere. That's the whole idea behind Savely.