Archive of Our Own is one of the last great text-only places on the internet. No autoplaying video, no algorithmic feed, no app nagging you — just fifteen million works of fic sitting there in clean HTML, tagged with a precision that would make a librarian weep. I love it without reservation.
It also, famously, will not read anything to you. There's no listen button, no audio setting buried in preferences, nothing. The AO3 volunteers maintain the site on donations and stubbornness, and text-to-speech has never been on the roadmap. If you've ever searched "ao3 text to speech" at 1 a.m. with a 120k-word fic open and your eyes giving out, this post is the answer I wish I'd found.
The podfic gap
Fandom's traditional answer to "I want to listen to this fic" is podfic — fans recording themselves reading a work, with the author's blessing, and posting the audio to the archive. When it's good, it's really good. Search the podfic tag and you'll find performers with better mic technique than half of professional audiobook narrators.
But do the math. There are on the order of fifteen million works on AO3. Podfics number in the tens of thousands. A podficcer spends hours recording and editing per chapter, free, for love. That labor can never scale to the whole archive, and it especially can never cover the fic you care about most on any given night: the WIP that updated today. Podfic is a gift. It is not a coverage plan.
So for everything else — which is nearly everything — you need something that generates the audio on the spot, from the page you already have open.
How I listen to AO3 fics
I use CastReader, a free-to-start Chrome extension (works in Edge too). The workflow on AO3 specifically:
- Open any work — a one-shot, a chapter, anything.
- Click the floating button that appears on the right edge of the page.
- It starts reading from the top of the fic, in a natural AI voice, with each word highlighted as it's spoken. The page auto-scrolls to keep pace.
The highlighting is the part I'd fight for. Fic reading isn't passive the way podcast listening is — you drift, you snap back for a good line, you want to see the dialogue punctuation the author sweated over. With the words lighting up in sync, your eyes can check in and out freely and you never lose the thread. It reads less like "playing an audio file" and more like someone moving a finger along the text for you.
Tap any paragraph and the voice jumps there. That's how you skip a recap, replay the scene that just wrecked you, or resume a fic you abandoned mid-chapter on Tuesday.
The AO3-specific details
Long fics are the whole point. AO3 lets you view multi-chapter works one chapter at a time or via the Entire Work button. Both work fine — the reader picks up the full text of whatever view you're in. For a novel-length fic I tend to stay chapter-by-chapter (comments live per-chapter, and kudos-ing mid-listen is a ritual), but Entire Work mode plus listening is the closest thing to pouring the fic directly into your head.
Author's notes and end notes get read as part of the page. Some people skip them with a tap; I usually let them play, because A/Ns at 1.5× speed have a chaotic energy I've grown attached to.
Workskins — the custom CSS some authors use for texting-format fics or fancy formatting — are just styled text underneath, so narration handles them fine. The one genuinely audio-hostile genre is fics that rely on images (screenshot-fic, art-heavy works); no reader can speak a picture. For everything made of words, you're covered.
Speed is personal. Fic readers skew fast — most people I know settle at 1.5× to 2× after a few days. At 1.75×, a 9,000-word chapter runs about twenty minutes, which is how a "just one chapter before bed" fic actually stays one chapter.
Your place survives. Come back to a WIP after a week, tap the paragraph where you stopped, and the voice resumes there. No scroll-skimming through chapter 23 trying to find the line — and no accidentally reading ahead and spoiling the reveal three paragraphs down, which is the specific tragedy this feature exists to prevent.
When you're deciding whether a fic is worth 300k words
Slightly different problem: someone recs you a monster fic, the tags look promising, and you want to know what you're signing up for before committing a week of listening. CastReader's Read & Explain mode is built for exactly this kind of triage — it walks through a page, marks the key beats right on the text in handwriting, and narrates the gist in a couple of minutes. I use it the way I use the "read this to me" reflex on any long page: a fast pass first, the full sit-down if it earns it.
The honest pitch
Nothing here replaces podfic, and nothing should. A human performance of a fic is art on top of art; if the fic you love has one, listen to it and comment.
But the archive is fifteen million works deep and grows by thousands a day, and your eyes only have so many hours in them. For the WIP that updated an hour ago, the rarepair with twelve readers, the 300k slow burn nobody will ever record — generate the audio yourself, follow the highlight, and let the fic carry you through the dishes, the commute, the insomnia. The tab can finally close at night with the chapter actually finished.
Keep going:
- Turn any fanfic into an audiobook — the general case: FFN, Royal Road, and everywhere else fic lives.
- Does Wattpad have text to speech? — the Wattpad version of this exact question.
- How to binge web novels without burning out — for the translated-webnovel and 2,000-chapter crowd.
- Listen to AO3 with CastReader — the feature page, with setup details.
Open the fic in your other tab — you know the one — and press listen. Kudos when you surface.