이 페이지는 아직 한국어로 번역되지 않아서 영어판을 보여 드려요.

워크플로

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.

이 방식이 여기서 통하는 이유

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 can stay consistent

A hundred-thousand-word fic is dozens of rendering sessions and, sensibly, dozens of projects. Characters live inside a project, so consistency comes from choosing the same library characters and personas in each chapter's project and listening to the leads' first lines before you export — drift between chapters 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.

이런 작업에 어울리는 보이스

Ezra

Ezra

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

남성청년미국 영어비주얼 노벨나긋한
Wren

Wren

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

여성성인미국 영어내레이션따뜻한
Ashford

Ashford

Velvet-voiced villain who apologises before he ruins you

남성성인영국 영어빌런부드러운

라이브러리 전체 보기 →

이렇게 하면 돼요

  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. Write down the cast

    Note which library character and persona each role got, before chapter two rather than after chapter twenty. Characters do not carry between projects, so that list is what you rebuild each chapter's cast from.

  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

    One project per chapter, published the way the fic is published. It also means a revision only costs one chapter's export. Listen to each lead's first line before you export, because the same library character is not guaranteed the same voice in a new project.

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. Cloning is not open yet and will never cover them 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 per chapter, and export once. Credits are counted in characters at download: a 5,000-word English chapter is roughly 28,000 characters, a little over half an hour of finished audio. Every export counts the whole project again, so fix and re-listen inside the project — generating costs no credits — and download when the chapter is final. That 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.

비용은 이 정도

Free

US$0 / 월

 

내 대본에 목소리가 붙으면 어떤 소리가 나는지, 돈 한 푼 안 들이고 들어 보세요.

  • 생성과 미리 듣기는 크레딧이 안 빠져요 (24시간에 30줄까지)
  • 다운로드 크레딧 4,500개, 평생 한 번 (완성 오디오 11분쯤)
  • 캐릭터 보이스 40개 전부 — 유료 장벽은 라이브러리가 아니에요
  • 프로젝트당 등장인물 2명
  • 개인·비상업적 용도만

Basic

US$5 / 월

 

라이브러리를 전부 열고, 완성본을 가져가기 시작하는 단계.

  • 캐릭터 보이스 40개 전부
  • 매달 다운로드 크레딧 54,000개 (130분쯤)
  • 프로젝트당 등장인물 5명
  • 상업적 이용 라이선스 포함

Plus

US$19 / 월

 

속도를 직접 잡는 단계. 독백은 늦추고, 말다툼은 몰아치게.

  • 매달 다운로드 크레딧 180,000개 (450분쯤)
  • 대사별 말속도 조절
  • 프로젝트당 등장인물 무제한
  • SRT 자막 내보내기

전체 비교 →

자주 묻는 질문

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. Voice cloning is not open yet, and when it opens this will not be allowed — it 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 against our cloning policy, and it is the single fastest way to get a podfic taken down. Cast a library character 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 you have settled which library characters play whom.

Which plan fits a long fic?

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

오늘 밤, 첫 장면을 캐스팅해 보세요

장면을 붙여 넣고, CastDub가 인물마다 보이스를 붙이게 하고, 완성된 오디오 드라마로 내보내세요.

무료로 만들어 보기

카드 등록 없이. 무료 요금제는 한 번만 주어지는 크레딧이에요.