A read-aloud extension that stops after a couple of paragraphs

It reads the first paragraph or two, then goes quiet. Nothing turns red, nothing says why, and pressing play again sometimes works and sometimes does not. That is not one bug — it is three, they look the same from the outside, and you can tell them apart in about ten seconds.

10 September 2026 · written while building a page reader, from our own measurements. Where we only tested one machine on one day, it says so.

Start it reading a long article, then watch two things at once — the sound, and the highlight.

• The voice keeps going but the highlight freezes. The part of the extension that tracks where you are was shut down while the audio kept playing. Cause 1.
• Both stop at the same moment, part-way through, and it happens at the same place every time on that page. Something hit a length limit. Cause 2.
• Nothing ever happens, or it stops within a few seconds of starting, and there is no error anywhere. The voice itself never really started. Cause 3.

None of the three announces itself, which is why they get reported as one complaint.

Chrome extensions built on the current extension platform do not get to keep a process running. Their background script is a service worker: Chrome starts it when something happens and shuts it down when it looks idle. Playing audio does not count as busy, because the audio is played by the browser's speech engine, not by the extension.

So the speech engine carries on reading while the thing that was moving the highlight is gone. Our own reader keeps its worker awake by pinging the browser every 20 seconds while a read is in progress. That is a mitigation, not a fix: if Chrome shuts the worker down anyway, the voice continues and the highlight stops, and it stays stopped until the next thing wakes the worker up — opening the toolbar popup, pressing the shortcut, or closing the tab. We are telling you this about our own extension because it is the honest version: we made this failure rarer, we did not make it impossible.

What it means for you as a reader: if the voice is still going, nothing is broken badly. Pressing the extension's shortcut usually brings the highlight back to where the voice is.

The browser's speech interface takes a maximum of 32,768 characters in one request. An extension that hands the browser a whole article as one request is fine on a short page and stops part-way through a long one — always at roughly the same place, because the limit is a property of the page, not of your machine.

The way around it is to never make a long request: split the page into sentences and queue them one at a time. Our reader does that, and hard-splits any single "sentence" longer than 400 characters — a bulleted list or a block of code with no full stop in it would otherwise become one enormous chunk, and the highlight would land on a wall of text instead of a line. We measured the cost of doing this on a deliberately long page: 150 paragraphs, about 300 sentences, 0.03 seconds to collect, split and queue. Splitting is not what makes readers slow.

Splitting has one audible cost, and it is worth knowing before you blame the voice: each sentence is a separate request, so there is a small pause at every full stop. That gap is the speech engine starting up again, not the extension thinking.

Some of the voices in Chrome are network voices: the text goes to a server and the audio comes back. When that round trip goes wrong, the failure is silent in a particularly unhelpful way.

On 6 September 2026, on one machine, we sent one sentence to a network voice. The "speaking has started" event arrived 23.5 seconds later. There was no audio. The "finished" event never arrived. And there was no error event at all — nothing anywhere reported a problem. A different voice on the same machine, in the same minute, worked normally.

That is one machine on one day, so treat it as an existence proof and not a rate: we did not measure how often it happens and we are not going to guess. What it does establish is the shape — "no error" is not evidence that anything is playing. An extension that waits for an error before telling you something is wrong will wait forever. Ours gives up after 7 seconds of being told nothing and says so, which is the only reason this case is distinguishable from the other two at all.

What it means for you as a reader: switch to a different voice in the extension's settings, and prefer one that does not need the network. Voices that run on your own machine cannot fail this way. On some systems there are none installed, which is its own version of "nothing happens".

If a page embeds text from another site — some document viewers and comment widgets are built this way — a browser extension is not allowed to read inside that embedded frame. The reader skips it and carries on, so what you hear is the page with a hole in it, and nothing tells you a section was left out. This is a restriction on every extension, not a bug in one of them, and there is no workaround from the extension's side. It is worth ruling out before you go looking for a better reader.

All three causes are things we hit while building Highlight Reader, a Chrome extension that reads a web page aloud and highlights each sentence on the page, where the text actually is, rather than in a side panel. It is free, and the page it links to says plainly what it does, what it does not do yet, and what the paid add-on would add — including the parts above that we have not solved.

If a free reader you already have does what you need, keep it. We would rather say that here than after you have installed something.