Sign in Start free

Guides

Narrating an audiobook with AI without it sounding like one

Eight hours of audio is a project-management problem before it is an audio problem.

Last checked 2026-08-14

In short

Split the manuscript into chapters, choose one voice and never change it, build a pronunciation list for every name in the book before you render a word, render chapter by chapter as queued jobs, and re-render single paragraphs rather than chapters. Naadly's $39 plan is uncapped for standard-language speech, which is what a long book needs.

One voice, chosen slowly

A listener spends eight hours with this voice. Test candidates on your hardest page - dialogue, a name-heavy paragraph, a long sentence - not on a demo line. Prefer a deliberate pace: it sounds slow in a thirty-second test and right in hour three. Note the voice slug and never change it; two voices in one book reads as an error even when both are good.

The pronunciation list comes first

Every character, place, invented word and foreign phrase goes into the pronunciation dictionary before the first render. Doing it afterwards means finding the same name mispronounced in nineteen chapters. The dictionary is per workspace, so it applies to every chapter, every retry and every future book in the series.

Chapters, lines and re-renders

Import each chapter as its own project; paragraphs become lines. Queue the chapter as a job and let the webhook or the jobs page tell you it is done. When you find a bad sentence - and you will - re-render that line only. This is the difference between a correctable audiobook and a re-rendered one.

Sounding produced rather than generated

  • Render to WAV or FLAC and master afterwards; MP3 is a delivery format, not a working one.
  • Leave real silence between chapters, and half a second after a chapter heading.
  • Do not add music under narration. It dates the book and hides nothing.
  • Listen at 1.25x for a first pass to find broken sentences quickly, then at 1x for the ones you fixed.

What retailers ask for

Requirements change and vary by shop, so check the current rules yourself before you upload - several major platforms now require you to declare AI narration, and some restrict it entirely. Naadly's side of that is documented: the audio is licensed for commercial use, carries an AudioSeal watermark, and has a provenance record you can point at if you are asked how it was made.

Step by step

  1. Split the manuscript One project per chapter, paragraphs as lines.
  2. Build the pronunciation list Every proper noun and invented word, before the first render.
  3. Audition three voices on your hardest page Dialogue and names, not the blurb.
  4. Queue chapter one and listen to all of it Fix at the line level. Only then render the rest.
  5. Master and export WAV or FLAC out of Naadly, loudness matched in your editor, then MP3 for delivery.

Questions

Can AI narrate a whole book?
Technically yes, and the practical limit is your patience for checking it. Chapter-sized jobs and per-line re-renders are what make it feasible.
Which plan suits an audiobook?
$39 a month: standard-language speech is uncapped, which matters when a book is eight hours and the second pass is another eight.
Will Audible or Amazon accept AI narration?
Policies differ and change - check the current terms of the shop you are publishing to. Many now require a declaration that the narration is synthetic.
Can I clone my own voice to narrate my book?
Yes, on a paid plan, with a consent recording. Expect to test it hard: a clone reading eight hours exposes every weakness in the reference recording.