Skip to main content
Konthora

Knowledge Center

Text to Speech for Audiobooks

Long-form narration is the hardest case on this site, and the limits are the reason. A chapter is tens of thousands of characters against a 2,000-character job limit, and prose is the least speech-like text there is. The work is in preparation, not generation.

Preparing prose for speech

Novels and essays are written to be read silently. Narration needs them rewritten, and this is the single largest quality difference between a good audiobook and a robotic one.

Parenthetical asides are the main offender. An aside is invisible on a page and a stumble in audio, because the narrator has to hold the main clause, deliver a subordinate thought, and return. Move it into its own sentence.

Dialogue tags and em-dash interruptions have the same problem in fiction. So do footnotes, symbols, and numbers written in digits. Resolving all of these in the source text is faster than trying to fix them by regenerating, because the model reads what is written rather than what is meant.


Managing the 2,000-character limit at length

A single audiobook chapter is usually 30,000 to 60,000 characters, so it is fifteen to thirty jobs. That is not a workaround, it is the shape of the work, and treating it as one is where projects stall.

Split at scene boundaries. A scene break gives you sections of three to eight thousand characters, each generating as two or four jobs, and it means the splits are somewhere that already made structural sense. A character-count split at 2,000 puts a seam mid-sentence.

Name the files as you go. Thirty sequential files joined in the wrong order is a genuinely painful mistake to discover at the end, and the numbering costs nothing at the start.


Pacing that holds over an hour

Pacing is the difference between a listener finishing a chapter and abandoning it at fifteen minutes, and it is mostly the paragraph pause setting rather than the speed.

A longer paragraph pause at the end of a section reads as a beat between scenes, which is exactly what a human narrator does. At the default of 500 ms the joins between generated jobs feel abrupt, and over an hour that accumulates into a sense of breathless delivery.

Keep speed constant across the whole chapter. A listener who has adjusted to one pace finds a change jarring in a way that a single odd voice never does, because the speed is what they calibrated to without noticing.


Fiction, non-fiction and voice choice

Fiction and non-fiction want different voices more than most people expect. Fiction wants a voice that disappears, so the reader stops hearing narration and starts hearing the story. Non-fiction wants a voice that carries the argument, because the words are doing the work rather than the delivery.

Multi-character fiction is the honest limitation. There is no speaker labelling, so distinct voices have to be produced by generating each character separately, which is workable for a two-hander and impractical for an ensemble cast.

For first-person narration, match the voice to the character you have written. A younger, higher voice for a younger narrator and a lower one for an older narrator are available in the catalogue, and the fit is more noticeable than the choice of accent.


Step by step

1

Split the chapter at scene boundaries, not at 2,000 characters

A character-count split cuts sentences in half. Split at a scene break, a chapter heading, or a change of speaker or time, which gives sections of a few thousand characters each that you can then generate as two or three jobs.

2

Convert prose into speakable text before generating

Prose contains constructs that do not survive being read aloud: parenthetical asides, em-dash digressions, footnotes and dialogue tags written for the eye. Resolve them in the source text first, because no speed or voice setting fixes them afterwards.

3

Use a steady mid-register voice at 0.9x to 0.95x

Narrative fiction is usually better read slightly below the default. A 0.9x to 0.95x pace matches a natural reading speed and prevents the listener fatigue that makes a long chapter hard to stay with.

4

Normalise abbreviations, numbers and symbols

Write "one hundred and twenty" rather than "120" where it appears mid-sentence, and never leave a percent sign or an ampersand in the text. The model reads symbols literally, and a footnote marker is read as a number.

5

Join the sections in one session with fixed settings

A chapter is many files, and inconsistency between them is far more audible over an hour than it is over thirty seconds. Generate everything in one sitting with the same voice, speed and pause settings, then join without re-encoding.

If you have a finished audiobook and want a written version rather than narration for a new one, see the audio transcription accuracy guide.

Frequently Asked Questions

How much text can I narrate at once?
2,000 characters per generation job, which is about three minutes at 0.95x. A full chapter is fifteen to thirty jobs. Split at scene boundaries rather than at a character count, so no section begins or ends mid-sentence.
Can I narrate a whole book?
Chapter by chapter. A whole book is hundreds of generation jobs, and joining them all at once is where errors become hard to find. Treat each chapter as a project: prepare the prose, generate every section in one sitting with fixed settings, then join.
What speed is best for audiobook narration?
0.9x to 0.95x, which matches a natural reading speed and reduces the fatigue that makes a long chapter hard to stay with. Keep the speed identical across every job in a chapter, since a listener calibrates to it without noticing.
How do I handle dialogue with multiple speakers?
There is no speaker labelling, so distinct voices have to come from generating each character separately. That is practical for a two-hander and impractical for an ensemble cast. If the book has many speakers, a human narrator is the better option.