Reading speed: how fast a synthetic voice should read French aloud

People talk a lot about the timbre of a synthetic voice and almost never about its speed. Yet pace is the first setting that decides whether a listener stays or leaves. A pleasant voice that reads too fast tires the ear within two minutes; the same voice dragging its feet sends the listener to sleep. Pace is not a comfort detail, it is what makes an article finish or get abandoned halfway. This article gives concrete benchmarks, shows what they do in practice, and explains when to touch the setting and when to leave it alone. It is written about French, where the numbers differ from English for a reason worth understanding.

The starting benchmark: around 155 words per minute

A French-language radio presenter reads a news bulletin at roughly 150 to 160 words per minute. A measured audiobook reading often drops toward 140. Above 180 you enter the register of a recited hold message, the kind you hear without retaining a word. These figures are for French, and that matters: written French uses more small words (articles, prepositions, pronouns) than English to say the same thing, so for a given duration a French text lines up more words. A pace calibrated on English therefore feels slightly rushed in French.

The sensible default, for a blog or news article read by a synthetic voice, sits around 155 words per minute. That is the point where diction stays crisp, where the liaisons have time to happen, and where the listener can think for half a second without losing the thread.

What pace does to running time

The arithmetic is simple, and worth doing because it often surprises. For a 1000-word article:

• at 140 words per minute (measured reading): about 7 minutes 9 seconds;
• at 155 words per minute (the recommended benchmark): about 6 minutes 27 seconds;
• at 170 words per minute (fast reading): about 5 minutes 53 seconds.

Between the slowest and the fastest, the gap is over a minute on a single article. Across a blog of 300 posts, that is no longer one minute but hours of cumulative listening, and above all a very different experience. The temptation is to push the pace to "keep it short." It is a false economy: the time saved is paid back in comprehension lost, and a listener who retains nothing does not return. A slightly longer article that gets heard to the end beats a clipped one that gets dropped.

When the text sets its own rhythm

The displayed pace is not the felt pace, because punctuation adds silences on top. A text of short sentences, dotted with commas and full stops, listens more slowly than its words-per-minute suggests, since each mark calls for a pause. A text of long, breathless sentences gives the opposite impression, a flow that never stops, even at a moderate rate. Setting the speed without looking at the punctuation treats a symptom: often the real problem is a badly punctuated paragraph, a point we set out in our article on how text to speech breathes with punctuation. Start there before touching the slider.

Some content also calls for its own pace. A legal or medical text, dense with precise terms, benefits from being read a notch slower than the benchmark, to let the listener absorb it. A short opinion piece or a news brief, by contrast, takes a livelier rhythm. The right setting is not a constant, it is an editorial choice that follows the content.

Setting it without getting it wrong

The practical rule fits in a sentence: set it once, aloud, on a representative article, then leave it. The trap is adjusting the pace article by article on the feeling of the moment, which produces a blog where every page reads at a different speed. A listener moving from one post to the next notices, and it sounds improvised. A stable setting, applied by default to the whole blog through the player settings, gives a consistency that no case-by-case tweaking can match. The listener always keeps control anyway: most audio players let you speed up or slow down on the fly, and it is their call whether to go faster, not yours to make for everyone.

What to check

Do not trust the number alone: listen. A voice can display 155 words per minute and still feel too fast because it fumbles the liaisons or clips word endings. That is the kind of flaw you only catch by ear, which is why testing a voice on a real text, at the intended pace, belongs in any serious evaluation, as we explain in our checklist for evaluating a neural voice. Pace is the first setting to fix and the last to touch: set well, it disappears, and that is exactly what you want from a good reading. It is the same standard that drives our work on reading French aloud, set out on the French text to speech page.

Read next

• Dialogue and quotations: what French text to speech does with the marks
• Adding audio to a Tumblr blog: what works, and what gets blocked
• Adding an audio version to your Magento pages