About Wordcast
Wordcast reads text aloud in your browser. Paste something, open a local PDF or Word file, or hand it a web article URL, and it speaks using a voice your browser and operating system already provide. There is no account, no upload step for local files, and no per-character bill. What it sounds like, and whether it needs a network at all, depends on the device you are on.
How it works
Pasted text and local files are processed in the browser. A URL is sent to the extraction service; the returned article text is not stored. Voice availability and network needs depend on your browser, device, and selected voice.
Why we built this
Many voice readers ask you to upload text or start a subscription. Wordcast is for listening: paste text or open a local file, choose a voice your browser or device provides, and start. Article URLs use reader-mode extraction; voice quality and offline availability vary by environment.
What it can't do
Wordcast cannot save audio as MP3, clone a voice, or generate speech that does not exist in your browser. If you need those, you want a paid AI TTS service like Azure, Google Cloud, or ElevenLabs.
Who runs Wordcast
Wordcast is an independent project rather than a company. It went live in May 2026 and is maintained in spare time, which is why there is no team page and no support line. The site is open source at github.com/rocnubie/wordcast-Free-text-to-speech, so you can read what the reader actually does with your text instead of taking our word for it. Bug reports and voice requests go to the issue tracker there; anything else reaches a person at hello@wordcast.app.
How it is paid for
There is no paid tier, no account, and no usage meter. Wordcast is a static site with no application server behind it, so hosting costs very little and there is no per-character synthesis bill to pass on. Advertising is the only revenue we plan to add. Analytics are cookieless and aggregate only, and we do not sell or share visitor data.
How we check what we publish
Every capability claim on this site is checked against what the build actually does. A script runs before each deploy and blocks copy promising things the reader cannot deliver: unlimited file sizes, guaranteed offline playback, voices that are not installed on your device. Articles that make a technical claim link the browser documentation or the bug report behind it, with the date it was checked. Where the honest answer is that behavior depends on your browser, we say that rather than picking the flattering version.