Chrome extensions that read articles aloud

Search the Chrome Web Store for "read aloud" and you get dozens of extensions that look interchangeable. They are not. They split into two families that do genuinely different jobs, and picking the wrong family is why people install three of these and keep none.

Family one: speak the page in front of me

You are at your desk with an article open. You press the button and a voice reads it, with a highlight following along. Close the tab and it is over.

These use the speech engine already in your browser, which makes them free forever, instant, and account-free. They are the right tool for proofreading your own writing, getting through a dense paragraph, resting your eyes, or following along while you read.

What they are not built for is leaving your desk. Nothing is stored, there is no queue, and the audio almost never survives a locked phone — the reasons are structural, and no amount of polish gets around them.

Family two: build me something to listen to later

You are at your desk, you find something long, and you know you will not read it now. You send it somewhere, and later — walking, driving, doing the washing up — you listen to it on your phone.

Here the extension is a capture tool, not a player. It grabs the article text and hands it to a service that turns it into stored audio, reachable from your other devices. That costs money to run, so expect an account and a limit of some kind.

The pay-off is that listening is decoupled from the tab you found it in. That is the entire difference, and it decides which family you want.

Which one you want

One question settles it: when do you plan to listen?

• Now, at this desk, on this page — family one. Use what is already free. Do not create an account for this.
• Later, away from the computer — family two. Nothing in family one can do it, no matter how good the voice sounds in the demo.

Plenty of people want both, and there is no harm in having one of each. The mistake is installing a family-one extension expecting family-two behaviour, then concluding that browser read-aloud does not work.

What to check before installing anything

• What permissions does it ask for, and when? Reading the page you are on requires access to that page. An extension asking to read every site at install time, with no explanation, is asking for more than the job needs. Granting access one site at a time is a better shape.
• Is there a stated privacy policy that says where text goes? Family two necessarily sends article text to a server. That is fine and unavoidable — but it should be written down.
• Does it survive a locked phone? Only relevant for family two, and the deciding feature if you are.
• Do the screenshots match the current product? Stale screenshots usually mean a stale extension.
• How does it handle a page it cannot parse? Single-page apps, paywalls and login-gated pages defeat article extraction regularly. A good tool offers a fallback — fetch by URL, or paste the text — instead of a dead end.

Where ours sits

The ListenMore extension is firmly family two. It opens a side panel, reads the page you are on, and sends it to your library as stored audio in one of six voices. There is a built-in player for listening at your desk, but the point is that the audio is on your phone afterwards, playing with the screen off.

It asks for access one site at a time from inside the panel rather than demanding every site at install, and it only reads a page when you ask it to. A free account covers it, with the limit stated in plain minutes rather than buried in characters — we wrote up how to read a free tier and hold ourselves to the same test.

The reason to pick this family is the part a desk-side reader cannot do: the article is waiting on your phone afterwards, in a voice worth an hour of your attention, playing with the screen off. If that is the listening you have been meaning to do, this is the shape of tool that does it.