← Blog · 27 September 2026 · Lire en français

Listening faster (or slower): the audio player's playback speed

Six speeds from 0.8x to 2x, one button that cycles them, a choice the player remembers from one article to the next with no account. How playback speed works, and why it must not be confused with the pace of the voice itself.

A regular listener does not want every article at the same tempo. A column is savoured at normal speed; a press round-up they already half-know gets rushed; a dense technical piece gets slowed down to be followed. The player's speed control is exactly for this, and it is one of the most-used commands as soon as a site offers more than a few minutes of audio. It is worth stating precisely what it does, because "variable speed" is a box everyone ticks and few implement cleanly.

The six speeds, and why they loop

The player offers six speeds: 0.8x, 1x, 1.25x, 1.5x, 1.75x and 2x. A single button cycles through them in the order people ask for most often: you start at normal, step up to 2x, and the next press drops to 0.8x before returning to normal. That loop is not an implementation quirk. It puts the slow setting one press away from the fastest, which matters when you have pushed a text to 2x and a suddenly harder passage calls for slowing down without going all the way round.

The steps are deliberately close between 1x and 2x. The useful differences in listening to a voice live in that range: at 1.25x you save a fifth of the time with no comprehension cost, at 1.5x you are still perfectly intelligible on well-read French, beyond that you are into skim-listening. The single step below normal, 0.8x, exists for the moments you want to follow word by word, a foreign phrase, a quotation, a figure to write down.

What the setting really changes, and what it does not

Speed acts on the actual playback of the file, not on a new synthesis. Nothing is regenerated, nothing is re-billed: the same audio is played faster or slower by the browser, exactly like a podcast app. The player preserves pitch, so speeding up does not turn the voice into a chipmunk.

The choice is remembered. Once set, the speed is stored on the listener's device and carries to the next article, with no need to set it again and no account required: it is a listening-side comfort setting, not profile data. On mobile, the chosen speed is respected when playback continues with the screen locked, and the remaining time shown on the lock screen accounts for the tempo, so "4 minutes left" means four minutes at the speed actually being played, not at normal speed.

This works alongside the player's other controls, the fifteen-second skip forward and back, and resuming where you left off. On that last point, the behaviour is described in resume where you left off: the saved position and the remembered speed are two independent comforts that together let you return to an article without re-configuring anything.

Do not confuse listening speed with the pace of the voice

Two settings have similar names and nothing in common. The playback speed this article is about is on the listener's side: it speeds up or slows down an already produced file, on demand, at the moment of listening. The pace of the voice is on the production side: it decides how fast the text is spoken when the audio is made, and it is the same for everyone. The first is a slider each listener moves for themselves; the second is an editorial choice, covered in reading speed and pace in French TTS. Confusing the two leads to turning the wrong knob: you do not make an audio "faster for everyone" by changing the listening speed, which is per-device.

What it takes on the site side

Nothing in particular to install for the control to exist: it is part of the listening player described on the audio player page. The point to hold on to is that speed is a command of the listening experience, served by the player, not an audio variant to generate. That is consistent with the logic of the French text-to-speech page: you produce one clean audio once, and let the listener play it at their own tempo, without multiplying files or costs.

The test to run

On one of your narrated articles, start playback, open the listening player and press the speed button several times, counting the steps: you should find 1, 1.25, 1.5, 1.75, 2, then 0.8 before returning to normal. Switch articles without touching anything: the chosen speed should still be there. And on a phone, lock the screen mid-playback: the remaining time shown should match the speed you are listening at, not normal speed. Those three checks tell you in a minute whether the control is real or only displayed.

Give your articles a voice with WeDispatch

This blog is itself voiced by WeDispatch. Curious how it sounds on your content?

Book a demo

Read next