<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>The AudioForge blog</title>
    <link>https://audioforge.ai/blog/</link>
    <atom:link href="https://audioforge.ai/rss.xml" rel="self" type="application/rss+xml" />
    <description>Practical guides to turning a manuscript into a multi-voice audiobook: casting, direction, publishing rules for AI narration, and what is new in AudioForge.</description>
    <language>en</language>
    <lastBuildDate>Sun, 11 Oct 2026 11:03:38 GMT</lastBuildDate>
    <item>
      <title>How to write dialogue tags that cast cleanly in audio</title>
      <link>https://audioforge.ai/blog/dialogue-tags-that-cast-cleanly/</link>
      <guid isPermaLink="true">https://audioforge.ai/blog/dialogue-tags-that-cast-cleanly/</guid>
      <pubDate>Mon, 05 Oct 2026 00:00:00 GMT</pubDate>
      <dc:creator>The AudioForge team</dc:creator>
      <description>Name the speaker early, keep one speaker to a paragraph and avoid long untagged exchanges. A listener cannot glance back up the page to see who is talking.</description>
      <category>Craft</category>
      <category>Dialogue</category>
      <category>Casting</category>
      <category>Manuscript Prep</category>
      <media:content url="https://audioforge.ai/images/blog/gen/dialogue-tags-that-cast-cleanly-ff649d43-1600.webp" medium="image" />
      <content:encoded><![CDATA[<p>Dialogue casts cleanly when the text itself says who is speaking: a name close to the line, one speaker to a paragraph, and no long runs of untagged back and forth. A reader can glance back up the page to work out who is talking. A listener cannot, and neither can the software that assigns each line to a voice.</p>
<p>None of this asks you to write differently for the page. The habits that make a scene easy to follow by ear are the same ones editors have always asked for. In audio, they decide whether a line reaches the right voice.</p>
<p>Below: why tags carry more weight in audio, the habits that make attribution clear, whether an existing manuscript needs changes, and how to check the cast before you generate anything.</p>
<h2 id="why-do-dialogue-tags-matter-more-in-audio">Why do dialogue tags matter more in audio?</h2>
<p>Because the speaker has to be decided before a line is voiced. In a full-cast audiobook each character has a voice of their own, so someone, or something, must work out who says every line.</p>
<p>AudioForge is a production tool that turns a manuscript into a multi-voice audiobook, with a distinct voice for every character. Its parser reads the prose and assigns a speaker to each line from the same clues a reader uses: tags, names, paragraph breaks. When those clues are missing, the line is marked Unsure and left for you to assign.</p>
<p>Clear attribution therefore saves you review time. The fewer lines the parser has to guess at, the fewer you have to check.</p>
<h2 id="which-habits-make-the-speaker-clear">Which habits make the speaker clear?</h2>
<p>Five small ones cover most scenes.</p>
<ol>
<li><strong>Name the speaker early in a scene.</strong> The first line or two should leave no doubt about who is present and who is talking.</li>
<li><strong>Keep one speaker to a paragraph.</strong> A new paragraph signals a new speaker. Two people sharing a paragraph is the most common cause of a misattributed line.</li>
<li><strong>Anchor long exchanges.</strong> After three or four untagged lines, add a tag or a beat. With three or more people in the room, tag almost every line.</li>
<li><strong>Use names when pronouns collide.</strong> Two characters who are both &quot;she&quot; need their names more often than feels natural on the page.</li>
<li><strong>Mark thoughts as thoughts.</strong> &quot;She thought&quot; or a consistent convention keeps inner voice apart from speech.</li>
</ol>
<p>Here is the same exchange written two ways.</p>
<div class="blog-table"><table>
<thead>
<tr>
<th>Hard to follow by ear</th>
<th>Clear</th>
</tr>
</thead>
<tbody><tr>
<td>&quot;I won&#39;t go.&quot; &quot;You will.&quot; &quot;Make me.&quot;</td>
<td>&quot;I won&#39;t go,&quot; Mara said. Jonas did not look up. &quot;You will.&quot;</td>
</tr>
<tr>
<td>She told her she was wrong.</td>
<td>Mara told Ilse she was wrong.</td>
</tr>
<tr>
<td>&quot;Fine.&quot; He left. &quot;Coward.&quot;</td>
<td>&quot;Fine.&quot; Jonas left. Behind him, Mara said, &quot;Coward.&quot;</td>
</tr>
</tbody></table></div>
<h2 id="do-you-need-to-rewrite-your-manuscript">Do you need to rewrite your manuscript?</h2>
<p>No. A manuscript written for readers usually works as it stands, and the fix for a misattributed line belongs in the script, not in the book.</p>
<p>When the parser assigns a line to the wrong character, you change the speaker on that line in the Director Studio. Your manuscript stays exactly as you wrote it. <a href="/help">The help center</a> shows where that happens in the workflow.</p>
<p>The habits above pay off most for chapters you have not written yet. If you publish a serial and plan to release audio alongside it, a tag here and a name there costs nothing while drafting and saves a correction later.</p>
<h2 id="how-do-you-check-the-cast-before-generating-audio">How do you check the cast before generating audio?</h2>
<p>Go to the uncertain lines first, then read one crowded scene. That finds most problems in a few minutes.</p>
<ul>
<li>Jump through the lines marked Unsure and assign each one.</li>
<li>Pick the scene with the most speakers and skim it line by line. Crowded scenes are where attribution slips.</li>
<li>Look at any exchange with no tags at all for a long stretch.</li>
<li>Generate that one scene and listen. A wrong voice is obvious at once.</li>
</ul>
<p>If a line still comes out in the wrong voice, change its speaker and regenerate it alone. Unchanged lines are reused, so a correction never means redoing the chapter. You can try this on a chapter of your own from <a href="/">the home page</a>.</p>
<h2 id="the-bottom-line">The bottom line</h2>
<p>Write so that a listener always knows who is speaking: name the speaker early, give each speaker their own paragraph, and anchor long exchanges with a tag or a beat. Your existing manuscript does not need rewriting, because a misattributed line is fixed in the script. Check the uncertain lines and one crowded scene before you generate, and the cast will be right.</p>
]]></content:encoded>
    </item>
    <item>
      <title>How do you turn a chapter into a full-cast audiobook?</title>
      <link>https://audioforge.ai/blog/turn-a-chapter-into-a-full-cast-audiobook/</link>
      <guid isPermaLink="true">https://audioforge.ai/blog/turn-a-chapter-into-a-full-cast-audiobook/</guid>
      <pubDate>Mon, 05 Oct 2026 00:00:00 GMT</pubDate>
      <dc:creator>The AudioForge team</dc:creator>
      <description>Parse the chapter into a script, check who says each line, give every character a voice, then generate and export. Four steps, one chapter at a time.</description>
      <category>Guides</category>
      <category>Getting Started</category>
      <category>Director Studio</category>
      <category>Casting</category>
      <media:content url="https://audioforge.ai/images/blog/gen/turn-a-chapter-into-a-full-cast-audiobook-d5cb8eca-1600.webp" medium="image" />
      <content:encoded><![CDATA[<p>You turn a chapter into a full-cast audiobook in four steps: parse the text into a script, check who says each line, give every character a voice, then generate the audio and export it as one file. You work one chapter at a time, and nothing you have already produced has to be redone when you fix a line.</p>
<p>AudioForge is a production tool that turns a manuscript into a multi-voice audiobook, with a distinct voice for every character. The steps below are the same ones shown in <a href="/help">the help center</a>, with what to look for at each stage.</p>
<p>Below: what you need to start, how the script is made, how casting and direction work, and how the finished chapter comes out.</p>
<h2 id="what-do-you-need-before-you-start">What do you need before you start?</h2>
<p>A chapter of your manuscript and a free account. You create a book, then add text in whichever way suits you.</p>
<ul>
<li>Paste a chapter straight in.</li>
<li>Upload a chapter as a .docx or .txt file.</li>
<li>Import a whole manuscript as .docx, .txt or PDF. It is split into chapters, which you can rename, reorder, split or join before anything else happens.</li>
</ul>
<p>Each chapter becomes its own audio file. That is why serials are a natural fit: you can produce a chapter as soon as it is written.</p>
<h2 id="how-does-a-chapter-become-a-script">How does a chapter become a script?</h2>
<p>The parser reads your prose and writes it out as a screenplay. Every line gets two labels: who speaks it, and how it should be delivered. A nervous aside and a shouted warning from the same character end up with different directions.</p>
<p>The parser is not always certain. When it cannot tell who said a line, the line carries an Unsure tag, and &quot;Next uncertain line&quot; takes you from one to the next. Checking those lines is the most valuable few minutes you will spend, because a wrong speaker is much easier to fix in the script than to notice in the audio.</p>
<h2 id="how-do-you-cast-the-voices">How do you cast the voices?</h2>
<p>You pick a voice for the narrator and for each character from the Voice Library. Casting is saved for the whole book, so a character who appears in chapter one sounds the same in chapter forty.</p>
<p>Two things help with a long series:</p>
<ul>
<li>Mark voices you like as favourites so you can find them again.</li>
<li>Add invented names to the book&#39;s pronunciation glossary once, so they are said the same way every time.</li>
</ul>
<h2 id="how-do-you-direct-a-line">How do you direct a line?</h2>
<p>You edit it. In the Director Studio any line can be changed: the speaker, the delivery, the text itself, or the pause after it. What is in the script is what gets voiced, so a correction on the page is a correction in the audio.</p>
<p>You do not need to direct every line. Read through a tense scene, adjust the deliveries that matter, and leave the rest. Edits save automatically, and undo and redo work as you would expect.</p>
<h2 id="how-do-you-get-the-finished-audio">How do you get the finished audio?</h2>
<p>You generate the chapter and download one file. Generation runs in the background, so you can leave the page and a notification tells you when it is done.</p>
<div class="blog-table"><table>
<thead>
<tr>
<th>Step</th>
<th>What you do</th>
<th>What happens</th>
</tr>
</thead>
<tbody><tr>
<td>Parse</td>
<td>Add the chapter</td>
<td>The text becomes a script with a speaker and a delivery on every line</td>
</tr>
<tr>
<td>Check</td>
<td>Go through the Unsure lines</td>
<td>Each line ends up with the right speaker</td>
</tr>
<tr>
<td>Cast</td>
<td>Choose voices</td>
<td>The cast is saved for the whole book</td>
</tr>
<tr>
<td>Generate</td>
<td>Start the chapter</td>
<td>Every line is voiced and stitched, with your pauses, into one MP3</td>
</tr>
</tbody></table></div>
<p>Listen to the result. If a line sounds wrong, change it and regenerate. Only the lines you changed are produced again, and everything else is reused.</p>
<h2 id="the-bottom-line">The bottom line</h2>
<p>A full-cast chapter is four steps: parse, check, cast, generate. The parser does the heavy lifting and flags what it is unsure about, so your time goes into decisions rather than recording. Start with a single chapter, listen to it, and fix individual lines until it sounds the way you hear it. You can <a href="/">try it with one chapter</a> for free during early access.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Where can you publish an AI-narrated audiobook?</title>
      <link>https://audioforge.ai/blog/where-to-publish-an-ai-narrated-audiobook/</link>
      <guid isPermaLink="true">https://audioforge.ai/blog/where-to-publish-an-ai-narrated-audiobook/</guid>
      <pubDate>Mon, 05 Oct 2026 00:00:00 GMT</pubDate>
      <dc:creator>The AudioForge team</dc:creator>
      <description>Spotify and Kobo accept AI-narrated audiobooks with a disclosure. ACX, the route to Audible, still requires a human narrator. Here is each store's rule.</description>
      <category>Publishing</category>
      <category>Distribution</category>
      <category>Spotify</category>
      <category>Audible</category>
      <media:content url="https://audioforge.ai/images/blog/gen/where-to-publish-an-ai-narrated-audiobook-f26ca1e3-1600.webp" medium="image" />
      <content:encoded><![CDATA[<p>You can publish an AI-narrated audiobook on Spotify and Kobo today, as long as you say that the narration is synthetic. You cannot upload one to Audible through ACX, which still requires a human narrator. Apple Books and Google Play are less clear cut: both run AI narration programs of their own, and neither states a rule for audio made elsewhere.</p>
<p>Rules in this area change quickly. Every claim below links to the store&#39;s own page and reflects what that page said in October 2026, so follow the link before you plan a launch around it.</p>
<p>The question matters most if you produce the audio yourself. AudioForge is a production tool that turns a manuscript into a multi-voice audiobook, with a distinct voice for every character. You download the finished files and decide where they go, which means the stores&#39; rules decide your options.</p>
<p>Below: the short answer in a table, what each store asks for, how to disclose the narration, and where else the audio can go.</p>
<h2 id="which-stores-accept-ai-narration">Which stores accept AI narration?</h2>
<p>Two say yes in writing, one says no, and two only describe programs of their own.</p>
<div class="blog-table"><table>
<thead>
<tr>
<th>Store</th>
<th>AI narration made elsewhere</th>
<th>What it asks for</th>
</tr>
</thead>
<tbody><tr>
<td>Spotify</td>
<td>Accepted</td>
<td>Select the digital voice narration option when you upload</td>
</tr>
<tr>
<td>Kobo</td>
<td>Accepted</td>
<td>List the narrator as a synthesised voice</td>
</tr>
<tr>
<td>Audible, through ACX</td>
<td>Not accepted</td>
<td>A human narrator</td>
</tr>
<tr>
<td>Apple Books</td>
<td>No published rule</td>
<td>Ask your distributor before you rely on it</td>
</tr>
<tr>
<td>Google Play Books</td>
<td>No published rule</td>
<td>Ask support before you rely on it</td>
</tr>
</tbody></table></div>
<h2 id="what-do-spotify-and-kobo-ask-for">What do Spotify and Kobo ask for?</h2>
<p>Both ask you to say plainly that the voice is synthetic.</p>
<p>Spotify&#39;s <a href="https://support.spotify.com/us/authors/article/digital-voice-narration/" rel="noopener">help page on digital voice narration</a> says it accepts audiobooks narrated this way. When you upload through Spotify for Authors, you select the option &quot;This audiobook uses digital voice narration&quot;, and Spotify adds a short sentence to the book&#39;s description so listeners know. One limit: Spotify says it does not currently share digitally narrated audiobooks with its referral partners.</p>
<p>Kobo Writing Life&#39;s <a href="https://kobowritinglife.zendesk.com/hc/en-us/articles/10563450280475-AI-Narration-and-Audiobooks" rel="noopener">page on AI narration</a> says Kobo accepts it too. The narrator has to be listed as a synthesised voice, next to the author. Kobo does not ask for exclusivity, so the same audiobook can be on sale elsewhere.</p>
<h2 id="does-audible-accept-ai-narration">Does Audible accept AI narration?</h2>
<p>Not if you upload the audiobook yourself. ACX is the service independent authors use to reach Audible, and its <a href="https://help.acx.com/s/article/what-are-the-acx-audio-submission-requirements" rel="noopener">audio submission requirements</a> state that a submitted audiobook must be narrated by a human unless otherwise authorized. Unauthorized text-to-speech, AI or automated recordings are prohibited.</p>
<p>That may change. The same page says Audible is working to accept text-to-speech content from other publishers and creators, and will share timing later. Until it does, treat Audible as closed for an audiobook you produced with AI voices. The rule is explicit, so do not try to slip one through.</p>
<h2 id="what-about-apple-books-and-google-play">What about Apple Books and Google Play?</h2>
<p>Both sell AI-narrated audiobooks, but the pages they publish describe their own tools. Apple offers <a href="https://authors.apple.com/support/4519-digital-narration-audiobooks" rel="noopener">digital narration</a> to independent authors and small publishers, produced from an ebook file. Google Play Books runs an <a href="https://support.google.com/books/partner/answer/10013009" rel="noopener">auto-narrated audiobooks program</a> that does the same for an ebook already on sale there.</p>
<p>Neither page states a rule for audio narrated with other AI voices. Audiobooks usually reach Apple Books through a distributor, and distributors set their own conditions. One large distributor, for example, accepts digital narration <a href="https://voicessupport.inaudio.com/en/articles/3219456" rel="noopener">only from providers it has approved</a>.</p>
<p>Before you count on either store, ask the distributor or the store&#39;s support in writing whether they will take your files and how they want the narration labelled.</p>
<h2 id="how-should-you-disclose-ai-narration">How should you disclose AI narration?</h2>
<p>Say it in the place each store gives you, and in your own words as well.</p>
<ol>
<li>Select the store&#39;s digital or synthetic narration option when it has one.</li>
<li>Credit the narrator as a synthesised voice, never under an invented human name.</li>
<li>Mention it in your description, so listeners who care can choose.</li>
</ol>
<p>Never submit AI narration as human narrated. Distributors spell this out in their terms, and it is the one mistake a clear disclosure cannot fix afterwards.</p>
<h2 id="where-else-can-the-audio-go">Where else can the audio go?</h2>
<p>Anywhere you control. With AudioForge the audio files are yours, as the <a href="/ip-policy">IP policy</a> sets out, so you can release chapters to patrons on Patreon, post them on YouTube, or sell the audiobook from your own site.</p>
<p>That suits serial fiction well: a chapter a week, in audio, for readers who already follow the story. Each chapter exports as its own file, and <a href="/help">the help center</a> shows the steps from manuscript to download. Stores can come later, once their rules are clear for your book.</p>
<h2 id="the-bottom-line">The bottom line</h2>
<p>Publish where the rule is written down. Today that means Spotify and Kobo, each with a clear disclosure, plus any channel you run yourself. Audible stays closed to AI-narrated uploads through ACX until it says otherwise, and Apple Books and Google Play need a direct question before you rely on them. Decide on stores after you have heard a chapter: producing one is <a href="/">free during early access</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Why do AI audiobooks sound flat, and what fixes it?</title>
      <link>https://audioforge.ai/blog/why-ai-audiobooks-sound-flat/</link>
      <guid isPermaLink="true">https://audioforge.ai/blog/why-ai-audiobooks-sound-flat/</guid>
      <pubDate>Mon, 05 Oct 2026 00:00:00 GMT</pubDate>
      <dc:creator>The AudioForge team</dc:creator>
      <description>Most AI audiobooks use one synthetic voice for every line. A voice for each character and a direction for each line is what makes them worth hearing.</description>
      <category>Craft</category>
      <category>AI Narration</category>
      <category>Full Cast</category>
      <category>Direction</category>
      <media:content url="https://audioforge.ai/images/blog/gen/why-ai-audiobooks-sound-flat-456581b5-1600.webp" medium="image" />
      <content:encoded><![CDATA[<p>AI audiobooks sound flat when one synthetic voice reads the whole chapter, start to finish. Nothing tells that voice who is speaking or how a line should feel, so a whispered threat and a shouted warning come out the same. The fix is not a better single voice. It is a cast, and a direction for every line.</p>
<p>Ask authors what they think of AI audiobooks and you hear the same words: flat, one-dimensional, dull. Listeners notice within a minute, and the book is judged before the story has a chance. The verdict is deserved, but it is a verdict on one way of making audio, not on the idea.</p>
<p>Below: what a single voice cannot do, what changes with a cast, how the work is done, and how to judge the result yourself.</p>
<h2 id="what-can-a-single-voice-not-do">What can a single voice not do?</h2>
<p>It cannot show who is speaking. On the page, a reader knows from the tags, the paragraph breaks and the rhythm of the scene. They hear each character differently in their head, and the narration in between has its own calmer register.</p>
<p>Hand all of that to one voice and the structure collapses. Two characters arguing become one person talking to themselves. The narrator&#39;s dry aside arrives with the same energy as the line before it. Thoughts are indistinguishable from speech. Every word is pronounced correctly, and the scene still does not land.</p>
<p>A human narrator solves this by acting: shifting pitch and pace between characters, dropping their voice for the narration, leaning into the tense lines. A text-to-speech voice cannot, because all it is given is words.</p>
<h2 id="what-changes-when-every-character-has-a-voice">What changes when every character has a voice?</h2>
<p>Three things change at once: who speaks, how they speak, and what you can fix.</p>
<ul>
<li><strong>Every character gets a distinct voice.</strong> The listener no longer works out who is talking from context, because the voice tells them. The narrator has a voice of their own.</li>
<li><strong>Every line gets a direction.</strong> A line marked nervous is delivered nervously, and a line marked as a whisper is whispered. The same character can be furious in one paragraph and exhausted in the next.</li>
<li><strong>Every line can be fixed on its own.</strong> When a delivery misses, you change that line and regenerate it, not the chapter.</li>
</ul>
<div class="blog-table"><table>
<thead>
<tr>
<th></th>
<th>One voice for everything</th>
<th>A directed cast</th>
</tr>
</thead>
<tbody><tr>
<td>Who is speaking</td>
<td>Left to dialogue tags</td>
<td>Heard in the voice</td>
</tr>
<tr>
<td>Emotion</td>
<td>The same for every line</td>
<td>Set line by line</td>
</tr>
<tr>
<td>A line that sounds wrong</td>
<td>Regenerate and hope</td>
<td>Change that line alone</td>
</tr>
</tbody></table></div>
<p>This is what audio drama producers have always done. What kept it out of reach for an independent author was the cost of a studio, a cast and an engineer for a sixty-chapter serial.</p>
<h2 id="how-is-a-full-cast-audiobook-made-from-a-manuscript">How is a full-cast audiobook made from a manuscript?</h2>
<p>The chapter becomes a script first, and the script is what gets voiced. AudioForge is a production tool that turns a manuscript into a multi-voice audiobook, with a distinct voice for every character, and the work runs in four steps.</p>
<ol>
<li><strong>Add a chapter.</strong> Paste it or upload it. Each chapter becomes its own audio file.</li>
<li><strong>Parse it into a script.</strong> Every line is tagged with who speaks it and how it should be delivered. Lines the parser was unsure about are flagged for you to assign.</li>
<li><strong>Cast the voices.</strong> The narrator and each character get a voice, saved for the whole book, so a character sounds the same in chapter one and chapter forty.</li>
<li><strong>Generate and export.</strong> The lines are voiced, stitched with the pauses you placed, and downloaded as one file.</li>
</ol>
<p>The parsing step is the one single-voice tools skip, and it is where most of the difference comes from. <a href="/help">The help center</a> walks through each step.</p>
<h2 id="how-do-you-know-if-it-is-good-enough">How do you know if it is good enough?</h2>
<p>Listen before you decide. Scepticism about AI narration is reasonable, and an argument will not settle it. A sample will.</p>
<p>Play the full-cast sample on <a href="/">the home page</a> and wait for the moment two characters speak to each other. Compare it with the last single-voice AI audiobook you gave up on.</p>
<p>Then try a chapter of your own. It will not be perfect on the first pass. The parser can be unsure who said a line, and a delivery can miss. That is why uncertain lines are flagged, and why a single line can be redone without touching the rest. During early access it costs nothing to find out, and you keep every right to the text and the audio.</p>
<h2 id="the-bottom-line">The bottom line</h2>
<p>Flat AI narration is a production choice, not a limit of the technology. One voice reading a whole chapter cannot tell characters apart or change its delivery, so it sounds dull. Give every character a voice and every line a direction, and the same book sounds like a performance. Hear it on your own chapter before you judge.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
