Workflow

Turn Fanfiction into Audio

Fanfiction is dialogue-heavy, character-driven and enormous in volume — which makes it the best-suited fiction in the world for audio, and the least served by tools that give you one narrator reading everything.

Why this works here

Every character sounds like themselves

The reason fanfic is read rather than heard is that a single narrator flattens exactly what readers came for: the dynamic between two specific characters. Casting them separately restores it, and it takes minutes rather than a recording session.

Prose with dialogue tags works as-is

Fanfic is not formatted as a script. CastDub reads quoted speech with tags like "she said quietly" and turns them into character assignments, so you can paste a chapter straight from your document without reformatting anything.

Long works stay consistent

A hundred-thousand-word fic is dozens of rendering sessions. Character cards mean chapter forty sounds like chapter one, which is the failure mode that kills most long podfic projects.

It fits how fandom actually publishes

Export a mixed file for a podfic post, stems if you want to score it, or subtitles if you are making a video version for a platform that rewards captions. Nothing about the output assumes a professional pipeline.

Voices that suit this kind of work

Cass

Cass

Seventeen and furious about it, in a good way

femaleteenen-USteenmodern
Ezra

Ezra

Visual-novel love interest with a two-second pause before honesty

maleyoung-adulten-USvisual-novelsoft
Lumen

Lumen

VTuber persona: cute on top, deadpan underneath

femaleyoung-adulten-USvtuberanime
Koji

Koji

Rival character: clipped, competitive, secretly loyal

maleteenen-USanimerival
Sable

Sable

Noir detective narrating her own bad decisions

femaleadulten-USnoirsmoky
Wren

Wren

Bedtime-story narrator, slow and warm, never wakes anyone up

femaleadulten-USnarrationwarm
Ashford

Ashford

Velvet-voiced villain who apologises before he ruins you

maleadulten-GBvillainsmooth
Tess

Tess

Australian lead with a flat, dry delivery

femaleyoung-adulten-AUaccentdry

Browse the whole library →

How to do it

  1. Paste a chapter

    Prose, not script. Quoted dialogue with attribution tags is exactly the format auto-casting is built for.

  2. Check the speaker detection

    Attribution in prose is ambiguous more often than in scripts. Scan the assignments once before rendering — it is faster than fixing them after.

  3. Cast the narrator and the leads

    The narrator carries the prose and should be clearly separated from every character. Cast them first, then the two or three characters who carry the fic.

  4. Save character cards

    Do this before chapter two, not after chapter twenty. Cards are what make a long work possible.

  5. Direct the beats that matter

    Fanfic runs on specific emotional payoffs. Mark those lines and leave the rest neutral; that contrast is what readers came for.

  6. Export chapter by chapter

    Publish in chapters the way the fic is published. It also means a revision only costs one chapter.

Why fanfic and audio fit each other

Podfic — fanfiction recorded aloud — has existed for as long as fandom has had audio hosting, and it has always been limited by the same thing: recording takes as long as listening, plus editing. A 10,000-word fic is roughly an hour of finished audio and several hours of work, performed by one person doing every voice.

The demand has never been the problem. Fanfiction is unusually dialogue-dense, built around relationships between two or three specific characters, and consumed in exactly the contexts audio serves — commuting, chores, before sleep. It is arguably better suited to audio than most published fiction, and it is under-served because production is manual.

Casting the characters separately does something a solo podficcer cannot: it makes a two-person scene actually sound like two people. That is the specific thing readers are there for, and it is the thing a single narrator necessarily loses.

Prose is harder to cast than script

Screenplays label every speaker. Prose does not. It uses attribution tags, and then drops them once a rhythm is established, so a page of back-and-forth dialogue may have no names at all after the first two lines. Human readers track this effortlessly; automatic detection does not.

In practice this means the speaker-assignment pass is where your attention goes. Long unattributed exchanges, three-way conversations and any scene where a character is referred to by an epithet rather than a name are the reliable trouble spots. Scanning the assignments takes a couple of minutes and saves re-rendering.

There is a writing-side fix worth knowing: if you are writing the fic yourself and intend to make audio from it, keeping attribution slightly more explicit than prose style demands costs the reader almost nothing and removes the problem entirely.

The etiquette that keeps this welcome

Fandom's norms around transformative work are informal but strongly held, and the arrival of generated audio has made people justifiably nervous. Three habits keep you on the right side of them. Ask the author before podficcing their work, credit them in the post, and disclose that the voices are generated.

The disclosure point matters more than people expect. Communities that would happily listen to a generated podfic react badly to discovering it was generated after the fact, and the reaction is about honesty rather than about technology.

The hard line, again, is voice cloning of real performers. It is prohibited here, it is the thing rights holders actually pursue, and a fandom that gets a reputation for it loses the tolerance that lets transformative work exist at all.

Practical scale

Think in chapters, not in works. A chapter is a publishable unit, a re-renderable unit and a listening-check unit, and organising the project this way keeps a long fic from becoming unmanageable.

Budget by runtime rather than word count. English prose runs at roughly 150 words per minute of finished audio, so a 5,000-word chapter is about thirty-three minutes. That number, not the word count, is what your plan's monthly minutes are measured against, and it is the calculation most people get wrong on their first long project.

Where to post it, and what to expect

Podfic has its own distribution habits, and they are worth following. Archive of Our Own accepts podfic as a work with the audio hosted elsewhere and linked; the audio itself usually lives on a general file host or a podcast feed. Tumblr and Discord servers are where it actually gets heard, and a Reddit fandom thread will occasionally carry one further than any of them.

Expect a smaller audience than the text version, and expect a more committed one. Podfic listeners tend to follow specific ships and specific podficcers rather than browsing, which means tagging accurately matters more than volume. One well-tagged chapter posted where the fandom already talks will outperform ten posted into a void.

Give it a proper description: the fandom, the ship, the length in minutes, whether the voices are generated, and a credit to the author with a link. The length in minutes is the field people actually use to decide, and almost nobody includes it.

What it costs

Free

$0 / month

Enough to finish a short scene and hear what your script sounds like cast.

  • 10,000 characters every month — the quota resets, it is not a one-time trial
  • 2 cast members per project
  • 5 minutes of finished audio
  • Exports carry a short CastDub watermark
Start free

Studio

$29 / month

For serialised work: long-running dramas, audiobooks, dubbing pipelines.

  • Unlimited cast members per project
  • 200 minutes of finished audio a month
  • Line-by-line emotion control
  • Multitrack and stem export (one WAV per character)
  • 3 voice clone slots
Choose plan

Team

$69 / month

For a studio where a writer, a director and an editor touch the same project.

  • 5 seats, shared projects and shared character cards
  • 500 minutes of finished audio a month
  • 10 voice clone slots
  • Priority rendering queue
Choose plan

Full comparison →

Frequently asked questions

Is this legal?

Fanfiction sits in a tolerated grey area that varies by rights holder, and converting it to audio does not change its legal status either way. What does change is visibility: audio and video versions travel further than text and attract more attention. Non-commercial, clearly transformative work in a fandom that tolerates it is the established norm; monetising it is where people get into trouble.

Can I clone a canon actor's voice?

No. This is the most common request on this page and the answer is absolute. Cloning a performer who played a character is a publicity-rights problem and a policy violation, and it is the single fastest way to get a podfic taken down. Cast a voice with a similar register instead — it is legal, it works, and nobody minds.

How do I get permission from the author?

If you are podficcing someone else's fic, ask. Many authors have a blanket transformative-works statement in their profile; where there is not one, a short message is normal courtesy and almost always answered. Credit the author prominently in whatever you post.

What about explicit content?

Adult fiction between adult characters is within our terms. Sexual content involving characters written as minors is not, regardless of source material or canon ages, and accounts generating it are closed.

How long does a chapter take?

Rendering is fast. The real time goes into checking speaker assignments and listening to the result. For a 4,000-word chapter, expect around half an hour of actual attention the first time and much less once your cards are set up.

Which plan fits a long fic?

Creator handles most single-fic projects at a few thousand words per chapter. A hundred-thousand-word work spread over months will want Studio for the extra minutes and unlimited cast.

Cast your first scene tonight

Paste a script, let CastDub assign a voice to every character, and export a finished drama.

Create for free

No credit card. Free plan renews every month.