Skip to main content

How to Write Scripts That Sound Natural in Text-to-Speech

The fastest way to improve text-to-speech audio is to improve the text. Writing for the ear is different from writing for the eye, and a few habits make almost any voice sound more natural.

By Abdul WaheedPublished: 7 min read

Write for the ear, not the eye

A reader can glance back at a complicated sentence. A listener cannot. Text that reads well on a page can become hard to follow when spoken, and a synthetic voice makes that worse because it cannot add the emphasis a human narrator would. Aim for text that you could comfortably read aloud yourself in one breath per sentence.

Keep sentences short and direct

  • Prefer sentences of about 10 to 20 words. Split anything that needs more than one comma-separated clause in the middle.
  • Put the main point first. "Press Save to keep your changes" is easier to follow than "To keep your changes, which you will otherwise lose, press Save."
  • Avoid stacking parentheses and dashes. Turn asides into their own sentence.
  • Use paragraphs. A new paragraph gives the voice, and the listener, a natural reset.

Use punctuation to control rhythm

Punctuation is the main way you tell a voice where to pause and how to shape a sentence. A comma gives a short break, a full stop a longer one, and a question mark usually makes the voice rise at the end. Missing punctuation is the most common reason sentences run together.

On Open Text to Speech you can also add pause tags such as [pause:short] or [pause:long] where you want a deliberate break, for example before revealing an answer or between list items.

Write numbers, dates and symbols the way they should be said

Voices guess how to read numbers and symbols, and the guess depends on context. When it matters, write it out:

Instead ofWriteWhy
3/4three quartersCould be read as a date or "three slash four".
10-15 min10 to 15 minutesHyphens and abbreviations are read unpredictably.
1998nineteen ninety-eightOnly if it is a year and the voice reads it as a number.
#1number oneSymbols may be skipped or read literally.
e.g.for exampleLatin abbreviations are often read letter by letter.

Handle names, acronyms and tricky words

  • Acronyms. If it should be spelled out, add spaces or full stops: "U N" or "U.N.". If it should be said as a word (like NASA), leave it as one word.
  • Unusual names. Spell them the way they sound for the listener, even if it looks odd on screen. Keep a short list of your phonetic spellings so you use the same one every time.
  • Homographs. Words like "read", "lead", "live" and "record" change pronunciation with meaning. If the voice picks the wrong one, rephrase the sentence ("I have read" instead of "I read") so only one reading makes sense.
  • Foreign words. A voice for one language may mispronounce a phrase from another. Consider a simpler synonym or a short explanation.

Split long scripts into sections

Each request in the Studio can contain up to 2,000 characters, roughly 300 words. For longer scripts, split at natural breaks such as paragraphs or scene changes, never mid-sentence, and keep the same voice and settings for every part so the pieces join smoothly.

A quick checklist before you generate

  • Read the script aloud yourself once. Anywhere you stumble, the voice will too.
  • Check every number, date, symbol and abbreviation.
  • Check names and acronyms, and use your phonetic spellings.
  • Make sure every sentence ends with punctuation.
  • Generate a short test passage first, then the full script.

Frequently asked questions

Why does the voice run sentences together?

Usually because of missing punctuation or very long sentences. Add full stops, split long sentences, and use a pause tag where you want a clear break.

How do I fix a mispronounced name?

Spell it the way it should sound, test it, and adjust the spelling until it is right. Then reuse the same spelling everywhere.

How many words fit in one request?

Up to 2,000 characters per request, which is roughly 300 words of English. Split longer scripts at paragraph breaks.

Should I use emojis or special characters?

No. They are either skipped or read out in unexpected ways. Remove them from the text you send to the voice.