Article Overview
Give the voice the context it needs to read a number the way you mean it — as a price, a year, an ID, or a phone number.
On their own, digits are ambiguous — "101" could be "one oh one," "one hundred one," or "one-oh-one" depending on what it represents. A few formatting tricks, entered as a Replacement, tell the voice exactly how to read it.
Before you get started
- Enter these fixes as a Replacement: highlight the number in your script and open the Replacements panel from the Smart Toolbar, or open it directly from the right sidebar. You can also edit the digits directly in your script for a one-off fix.
- Try Rewrite for Speech in the Smart Toolbar first — it automatically suggests TTS-friendly formatting for numbers, so you may not need to fix them by hand.
Pronouncing reference numbers
Add spaces between digits so the voice reads them individually instead of as one large number.
-
1246 →
1 2 4 6reads as "one two four six"
Pronouncing dollar amounts
Spell out the unit to get a natural-sounding amount, with or without "dollars."
-
$1,200,000 →
$1.2 millionreads as "one point two million dollars" -
1,200,000 →
1.2 millionreads as "one point two million"
Pronouncing years
Add a comma so the voice reads the digits as a year instead of a plain number.
-
2022 →
2,022reads as "two thousand and twenty-two"
Pronouncing phone numbers
Add spaces between digits, keeping the last two together, so the voice reads it as a phone number.
-
(206) 555-3131 →
2 0 6 5 5 5 31 31reads as a phone number ending in double digits
FAQs
Q: What if the voice still mispronounces a number after I format it?
A: Try a Respelling instead of a plain Replacement — turn on the Phonetic Respelling toggle in the Replacements panel and spell out the sounds using the Respellings Reference Charts.
Q: Can I reuse a number fix across projects?
A: Yes. Replacements save to your Pronunciation Library, so you won't need to re-enter the same fix in a new project.