Every few weeks a screenshot goes around and the argument restarts. This week's version is a listener posting a chapter and a timestamp — hit play here, and the audiobook reads out the instruction it was given instead of the sentence it was supposed to say. The thread title in r/mildlyinfuriating is Book I bought didn't edit out the AI prompt, and the comments quickly turned into people swapping other titles where the same thing happens.
Our position, stated up front: almost none of these incidents are evidence about what a machine can or cannot narrate. They are evidence that somebody sold a first draft. The reader is not detecting AI. The reader is detecting that no one ever read the book.
The pattern is always the same seam
The now-canonical case is from May 2025, and it is worth restating precisely because it gets remembered as an AI story when it is really a proofreading story.
Readers of a published fantasy novel, Darkhollow Academy: Year 2, found an editing note sitting in the middle of chapter three: a line explaining that the passage had been rewritten to align more closely with another working author's style. It was covered by 404 Media, Futurism, and Fast Company. The author, Lena McDonald, said she had used AI to help edit and shape parts of the book and could not afford a professional editor. The title came off Amazon; the screenshots did not come off Goodreads.
Two things are true about that at once. The tool did what it was asked. And the manuscript went to a storefront without anyone reading chapter three.
The audiobook version of this failure is louder, because a book with a bad line can be skimmed past and an audiobook with a bad line has to be sat through in real time. When a generated read includes text that was never meant to be spoken — a stage instruction, a heading, a note to self — a listener hears it at full narration pace, in a voice performing it sincerely. There is no charitable reading available to them in that moment.
Ready to try it on your own book?
Start your first chapter free →What listeners are actually objecting to
It is easy to read the r/audiobooks and r/selfpublish threads as blanket hostility to synthetic narration, and some of it is. But the specific complaints are more useful than the general mood, and the specific complaints are almost all production complaints:
| What the thread says | What actually went wrong |
|---|---|
| "The narrator read the prompt out loud" | Nobody listened to the finished file |
| "It reads every heading and page number" | Source text was never prepared for speech |
| "Every character sounds identical" | The book was never cast |
| "The names are pronounced wrong" | Pronunciation was never set before the final render |
| "It's flat — nothing happens in the scene" | No direction, no sound design, no mix |
None of those are arguments that the format cannot work. They are the checklist of steps between a generated pass and a production, listed by the people who noticed the steps were skipped. We wrote about the last row of that table separately in what an AI narrator tells listeners they're hearing — the tells are consistent enough to enumerate, which is another way of saying they are fixable.
The reason this matters commercially is that a listener who is burned once generalizes. One of the comments in this week's cluster is a reader announcing they will not buy any format from an author who ships an AI audiobook. That is a reaction to a specific bad product, expressed as a rule about a category. Authors doing careful work inherit that rule.
Disclosure is a separate question, and it's already answerable
The other half of the current argument is whether authors should have to say so. This gets treated as unsettled; it mostly isn't, at least operationally.
Standard ACX submission requires human narration unless ACX authorizes otherwise, so a third-party AI-narrated audiobook should be treated as ineligible on the normal indie route into Audible. Spotify for Authors accepts digital voice narration, adds a disclosure sentence to the description, and says it does not currently share digital-voice titles to referral partners. Google Play Books and Apple Books digital narration each run their own programs with their own terms. We keep the route-by-route detail current in does Audible accept AI narration.
The practical read: disclosure is a cost of doing business on most routes, and it is not the thing damaging authors. Disclosed, well-produced audio sells. Undisclosed, unfinished audio gets screenshotted. The two failure modes get conflated because they often occur in the same book, but only one of them is what the listener is angry about.
The finished-work standard
The standard we hold ourselves to is simple enough to state as a question: would you put this in front of a listener who paid for it, at full length, without warning them first?
That means the book gets cast rather than read in one voice; that names and invented terms are resolved before the final render rather than after a review complains; that scenes get direction and sound design rather than a flat pass; and that somebody listens to the whole thing. On Midsummerr those are steps in the workflow, not optional extras — the pronunciation step exists before generation for exactly this reason, and every production goes out mixed rather than as a raw render.
If you want the difference in your ears rather than in a table, our Frankenstein production is the clearest short demonstration: distinct cast, scored scenes, and — the boring part that matters — no artifact of how it was made anywhere in the audio.
The category's reputation is currently being set by the people who skipped that last part. It is worth not being one of them.
FAQ
Why do published books contain leftover AI prompts?
Because the manuscript was moved from the drafting tool to the storefront without a full read-through. The tool inserted a note or an explanation of its own edit, and no human pass caught it. It is a proofreading gap, not a generation gap.
Do I have to disclose AI narration?
It depends on the route. Standard ACX submission requires human narration unless otherwise authorized. Spotify adds a disclosure sentence automatically for digital voice narration, and Google Play Books and Apple Books run their own digital-narration programs with their own terms. Check the route before you produce, not after.
Does disclosing AI narration hurt sales?
The visible damage in these incidents comes from unfinished audio, not from the label. Listeners who chose a digitally narrated title knowingly are not the ones posting timestamps; the ones who felt misled by a product that was obviously never checked are.
How do I stop this happening to my audiobook?
Prepare the text for speech, set pronunciation for names and invented terms before the final render, cast the book, and listen to every chapter end to end before you publish. If your process has no step where a person hears the whole thing, that is the gap.
