Use a human-recorded Spoken Wikipedia track when the article provides one. For current text or an article without a recording, CastReader reads the visible headings and paragraphs while leaving most navigation, reference lists, and page furniture out of the queue.
To listen to Wikipedia, first check whether the article links to a human-recorded Spoken Wikipedia version. If it does not, or if you need the current article text, open the page in Chrome or Edge and start CastReader. It reads the main headings and paragraphs; infoboxes, tables, footnotes, reference lists, and navigation may be skipped, so select a specific passage when those details matter.
Article prose, human recordings, tables, references, and other languages do not behave the same way.
CastReader targets Wikipedia's central article container and reads prose in section order. This is the useful default for an overview, biography, history, or conceptual explanation.
Some Wikipedia pages link to community-recorded audio. Use that version when available and current enough for your purpose; it may sound more natural but can lag behind later edits.
Tables and infoboxes often lose meaning when flattened into speech. They are excluded from the default queue on supported Wikipedia layouts; select one row or fact when it is important.
English and Mandarin Chinese voices are the most established CastReader catalog paths. Other available languages remain Beta or Lab, so pronunciation and synchronization quality can vary.
Use the canonical /wiki/ article, not a search-results page, category list, or mobile preview card.
If Wikipedia provides an audio link, decide whether you prefer the human recording or the latest visible text. Recordings can be easier to hear but may not reflect subsequent edits.
The reading queue follows the visible headings and paragraphs and highlights the current passage as playback moves through the page.
For an infobox value, pronunciation, table row, footnote, or citation, select that text and read it separately instead of adding the whole reference apparatus.
Wikipedia articles mix narrative prose with navigation, edit controls, citations, pronunciation guides, mathematical notation, tables, infoboxes, images, and reference lists. Reading every visible token would make the audio harder to understand, so CastReader's supported Wikipedia rules prioritize the main prose and section headings.
That filtering is a tradeoff, not a guarantee of completeness. A table may contain the exact date you need, a footnote may qualify a claim, and an infobox may summarize the subject more efficiently than the article. When a detail matters, stop the main narration, select that passage, and hear it separately while keeping the visual context on screen.
Wikipedia changes continuously. A community recording may preserve an older revision, while browser text-to-speech reads the version currently rendered in your tab. For study or citation work, use audio to understand the article, then return to the written page and sources before relying on a claim.
Answers for spoken recordings, current text, references, tables, pronunciation, other languages, and mobile devices.
Check the article for a human-recorded audio link first. Otherwise open the full page in Chrome or Edge and start CastReader to hear the main headings and paragraphs.
Some articles have community-recorded Spoken Wikipedia versions, but availability varies. A recording may also predate later edits, so use browser text-to-speech when you need the current visible revision.
The default Wikipedia workflow minimizes citation markers, footnotes, and reference lists so the main article remains listenable. Select a specific note or source when it is important to your question.
Not reliably as part of the main queue because row and column relationships often disappear in speech. Select the exact row, value, or cell you need and read it separately.
Pronunciation templates, IPA, equations, and mathematical notation are not ordinary prose and may be excluded or spoken poorly. Keep the visual page open and use a specialist pronunciation or math tool when exact rendering matters.
Yes, when a matching CastReader voice is available, but quality varies. English and Mandarin Chinese are GA; other listed languages remain Beta or Lab, so test the opening paragraph before a long article.
The CastReader browser extension is for desktop Chrome and Edge. On mobile, use a Spoken Wikipedia recording when available or the phone's built-in accessibility speech controls.
CastReader is free to start with daily allowances. Pro provides higher usage limits and additional voice and explanation access; see the pricing page for current limits.
Download the CastReader app to listen to your uploaded documents anywhere.
Hard numbers — not vibes — from authoritative sources
$2.22 billion
US audiobook sales in 2024, up 13% year-over-year (Publishers Weekly / Audio Publishers Association)
Source →51%
of US adults have listened to an audiobook in 2025 — roughly 134 million people (APA Consumer Survey 2025)
Source →2.2 billion
people globally with near- or far-vision impairment (WHO Fact Sheet, 2024). TTS is the primary access path for digital reading content.
Source →78%
of audiobook listeners multitask while listening — commute, chores, exercise (Audiolibrix Great Audiobook Survey, 2024)
Source →27.2 minutes
average single-trip US commute in 2024, up from 26.8 (US Census ACS via Statista). That's nearly an hour each day of audio-only time.
Source →effect size 0.35
measured comprehension lift from TTS for reading-disabled students across 22 studies (Wood, Moxley, Tighe & Wagner, Journal of Learning Disabilities, 2018)
Source →15.5 million
US adults with ADHD per CDC 2024 — about half diagnosed in adulthood (CDC MMWR, October 2024)
Source →Every Chrome Web Store review below is verifiable at the link in each card. We don't hide negative feedback — we answer it within 24 hours.
“This is 1 of the best TTS and its smooth. If this is truly free i'll keep this 100%. Every other TTS says its free but has a secret. They interrupt or they just say better ai voices pay. But i like this voice. I've tried loads and this is 1 of the best ones that actually says free.”
“Works perfectly on vivaldi. One suggestion though. I wish it had a play button appear next to a paragraph when we hover over it. Just like in the case of speechify.”
“Extremely user friendly short keys. Placed forward backward and speed up down as Natural as it could be. Voices are great and smooth. I would recommend it over many hyped products.”
“At the very least it's better than many paid TTS models. Still not as good as ElevenReader or LAP, but maybe the best free model for TTS.”
“So glad I can finally switch voices! The default was fine but I found one I actually enjoy listening to for hours. Small thing, huge difference.”
“Best one i found, user friendly, and great voice over.”
“ChatGPT's long answers are finally listenable. Let it generate while I listen — doubles my productivity. Love the inline button next to each response.”
“I tried using this add-on to listen to an ebook on the O'Reilly learning platform, and it works smoothly. However, it always restarts from the first paragraph whenever I scroll or select a different paragraph. Please consider adding a bookmark or checkpoint feature so users can mark where the reading should begin.”
↪ Founder reply
Replied by CastReader founder Yan Xu within 48 hours: acknowledged the issue, shipped a bookmark feature in the following release. Reviewer's verbatim feedback drove the v1.2 roadmap.
“Need to highlight text and select it.”
“Hard to select text.”
↪ Founder reply
Replied by CastReader founder Yan Xu within 24 hours: apologized, asked which site/browser the issue occurred on, provided a workaround using the keyboard shortcut, and offered direct support at support@castreader.com.
We re-test, re-write, and ship continuously. Every entry has a real date.
Rewrote landing pages with verbatim Chrome Web Store testimonials, real audiobook market data, and tested-12-extensions methodology. Every claim now has a sourceable link.
CastReader provides native apps for iPhone and Android; Android downloads are available directly from Google Play.
Wrote up the OCR pipeline: how CastReader handles Amazon's 184 random font alphabets and 361 unique glyphs per Kindle book. Shared in dev.to.
The phone app flow now has its own landing page for bookshelf sync, Read Aloud, synced highlighting, auto-scroll, background playback, and resume progress.
Ranked #10 in Daily, 99 upvotes, 4 community comments shaped the v1.2 roadmap.
Switched from older TTS engines to Kokoro neural voices. User reviews shifted from 'usable but robotic' to 'enjoy listening for hours' (verbatim from review by patrick chiang).
OCR success rate improved from 78% to 89% on English-language Kindle books. Multi-column page detection added for academic PDFs.
I built CastReader because I owned hundreds of Kindle books and couldn't listen to them on my morning runs without buying separate Audible copies. The technical problem — Amazon's Cloud Reader font encryption — turned out to be solvable with OCR. The product problem — making it actually pleasant across phones, desktops, and 9 supported languages — took two years of iteration. We're a small team. I answer every Chrome Web Store review personally (see testimonials above — including the 3-star and 1-star ones). If something's broken or missing, email support@castreader.com.
— Yan Xu, founder
Last reviewed: · CastReader Team — reviewed against 2025 testing data
Listen to the main prose, select structured facts on demand, and return to the written sources before citing a claim.
Official App Store and Google Play downloads · Chrome, Edge, and Firefox extensions