How to listen to the articles you never read
Saving was never the hard part. How a cluttered page becomes something you can listen to on the walk, with no connection needed.
In short: Load it at home, generate the audio, and the article plays in a tunnel. Nothing was uploaded to make that work.
You save things. You do not read them. When Pocket shut down, an enormous number of people discovered that what they had actually built over ten years was not a reading list but a guilt archive, and then dutifully exported it to somewhere else so the guilt could continue in a new app.
Saving was never the bottleneck. Sitting down in front of a screen to read something you saved on a different screen — that is the bottleneck.
An article is about one commute long
This is why listening suits articles far better than it suits books.
A book asks you to hold a thread across weeks. An article is one sitting. Two thousand words is roughly a walk to the station, or the washing up, or half a drive. There is nothing to lose track of, and you finish it, which after four months in a queue is not nothing.
Paste a link, get the article
Paste in a URL and you get the piece back, cleaned up.
You get the writing, the headline, the author, the images that belong to the article. You do not get the cookie banner, the newsletter pop-up, the navigation, the sidebar, the "you may also like" grid, or the eleven ways to share it.
It reads it the way a person would read it to you. The headline and the standfirst are read. The source, the byline and the "12 min read" are shown on the page but never spoken, because nobody has ever wanted to hear that out loud.
It handles modern sites properly, too. A lot of pages today contain almost nothing until their scripts have run — fetch the page the naive way and you get an empty shell. Here the page is loaded and given a moment to build itself, and only then is the article pulled out of it. It is the same idea as Safari's Reader view, and it works on the same sites.
One honest limit: anything behind a login or a paywall gives you only what a stranger would see. If you are subscribed, you are subscribed in your browser, not here.
Where this sits next to your read-later app
Worth saying plainly, because the temptation is to overclaim.
There is no browser extension. There is no syncing queue, no inbox, no tags, no recommendation feed. You paste a link.
If your saving already lives in Readwise or Instapaper or a folder of bookmarks, keep it there. This is not where you save things — it is what you open when you want to listen to one of them. The two jobs are different, and the app that is good at collecting is not automatically the app that is good at reading aloud.
The point is that it works with the signal off
Here is the bit that changes the habit.
Load an article in the evening, have the audio generated, and it is on your device. Not streaming. Not "cached, probably". On the device.
So it plays in a tunnel. It plays on a plane. It plays in the lift, in the basement car park, and in the two miles of the A-road where nothing has ever worked. It plays at exactly the same quality offline as on, because there was never a server involved in the first place — the voice is generated on your Mac or iPhone.
That last part is also why nothing you read gets uploaded anywhere. The page itself is fetched, obviously; that is what a link is. Everything after that happens on your machine.
If you want to test any app on this — not just this one — turn the network off and try to play something you have never opened before. Anything cloud-based will either fail or drop to a noticeably flatter system voice. It takes about a minute and it is the only claim in this whole category you can check yourself.
It reads anything you paste, not just links
The same box takes text. Paste in your own notes, a draft you want to hear back, a chunk of something a colleague sent you, a chapter you typed up. If it is a link it fetches it, and if it is not, it just reads it.
Notes written in Markdown are recognised as such, so the headings become a contents list you can jump around in rather than being read out as a row of hash marks.
Start with the oldest thing in the queue
Not the newest. The oldest — the one that has been sitting there since March that you still think you will read.
Paste it in, generate the audio, and listen to it on the way somewhere. Either it was worth keeping, in which case you have finally read it, or it was not, in which case you can delete it and feel nothing. Both outcomes are better than it sitting there for another six months.
Papers and books work much the same way — papers here, books here — and if you are weighing up the alternatives, the comparison is here.