wordtospeechEngine ready

[ Questions ]

What this does, and what it won't promise.

Everything below is checkable against how the tool actually behaves. Where something is a real limitation, it says so rather than working around the question.

01

Is it actually free?

Yes. There is no account, no paywall, no watermark and no trial. There is no paid tier to upgrade to, because there is no revenue model — the tool exists because it is useful.

02

Do I need to sign up?

No. There is no sign-up, and nothing to log in to. Your last-used voice is remembered in your own browser's local storage, which never leaves your machine.

03

What subtitle formats do I get?

SubRip (.srt) and WebVTT (.vtt), both UTF-8. You get them alongside the MP3 from the same synthesis, so they describe the exact audio you downloaded rather than a second, different rendering of the same text.

04

How accurate are the timings?

They are not estimated. The synthesis service reports a word boundary event for every spoken word, with an offset and duration in milliseconds, and the subtitles are built from those. Cues are then split at roughly 42 characters or five seconds, whichever comes first, so they stay readable.

05

Do the subtitles keep punctuation?

Yes. The raw word boundaries arrive as bare tokens — "sentence" rather than "sentence," — so each token is located back in your original text and the cue is sliced out of the source with its punctuation intact.

06

How much text can I convert at once?

5,000 characters per request. Longer text inside that limit is split, synthesised in pieces and stitched back into one file automatically — subtitles stay in sync across the join.

07

What audio quality is the download?

24 kHz / 48 kbps mono MP3. That is what the synthesis service is asked for, and the file you download is the exact bytes it returned — nothing is re-encoded.

08

Why does it render the whole clip instead of streaming as I listen?

Because the synthesis is not deterministic: the same text produces slightly different audio on each call. Streaming the audio and fetching timings separately would mean subtitles built against different audio from the file you keep. Subtitles are the point of this tool, so exact sync wins over a few hundred milliseconds of perceived latency.

09

Do you store my text or my audio?

There is no database and no account, so the text and audio you submit are never tied to you. Synthesised responses may be cached, keyed by a hash of the exact request, so that identical requests do not hit the upstream service twice. Cached entries are content, not identity — there is no record of who asked for them.

10

Do you use tracking or analytics?

The site loads Google Tag Manager, gated behind Google's Consent Mode with every category — analytics and ads — set to denied by default. A banner asks first, and nothing in that category is allowed to fire until you accept; reject it and the default denial simply stays in place. Full detail, including which third parties may be involved, is on the /privacy page.

11

Can I use the audio commercially?

We can't tell you that you can. Neural voices are licensed by whoever trained them, and this tool is not in a position to grant rights it doesn't hold. If your use is commercial, check the licensing terms that apply to the voice you are using, or choose a provider that grants commercial rights to you explicitly and in writing. That is a genuine limitation, not a formality.

12

How many languages are there?

The catalogue covers roughly 150 languages and locales. It is fetched live rather than hard-coded, so the voice list on this site is whatever the service currently offers.

13

Is the interface available in my language?

The interface is English only, and there are no plans to translate it. The output is a different matter — it covers the full voice catalogue, which is most of the world's widely spoken languages.