How Do Authors Format Ao3 Fanfiction For Mobile Readers?

When I format for people reading on phones I keep things lean and scannable. Short paragraphs, one-speaker-per-line dialogue, and clear scene breaks are the basics I always follow. I also put trigger/content warnings and a short summary at the top so mobile readers know what to expect without hunting through notes.

I avoid complicated layout: no tables, no large embedded images, and very limited use of bold or weird fonts. Em dashes and ellipses are fine, but long parenthetical thoughts get cut or broken into their own tiny paragraphs. Before publishing I preview on an actual phone and make tweaks — if I stumble while reading my own line, others will too. That quick mobile test, plus consistent chapter sizes and simple separators like '***', keeps things friendly for handheld reading and makes the story feel tidy even on a cramped screen.

My phone and I have a complicated love affair with long fics — I read on the bus, in bed, and sometimes while waiting for my pasta to finish, so I format everything with those tiny screens in mind. First, short paragraphs are my religion: break blocks of description into bite-sized pieces. A paragraph that’s only two to five lines on desktop reads like a novel on mobile; anything longer becomes a wall. I put each line of dialogue on its own line and avoid nested dialogue tags or long parenthetical asides. For scene breaks I use a simple centered '***' or a single em dash line; those translate perfectly across browsers and look clean in reader mode. I also keep chapter lengths reasonable — think 1,000–3,000 words for binge readers who don’t want to scroll forever between bathroom breaks.

I treat the author’s notes and summaries like signposts: concise and up front. A short, clear summary and visible content/trigger warnings at the top save readers time and make the experience less jarring on a phone. Inside chapters, I avoid heavy formatting: minimal bolding, sparing italics, and no huge images or embedded media that force slow loads. Links are fine but I never hide crucial context behind them because tapping back and forth on mobile is annoying. I also skip fancy alignment, tables, or preformatted text — those can break responsively and create horizontal scrolling. If I want a heading, I either type a short ALL-CAPS line or a simple underlined title made with hyphens; readable, consistent, and no weird rendering quirks.

Practical testing is the secret sauce. I always use AO3’s preview on my phone (both Chrome and Safari, depending on my tablet or phone) and check how paragraphs, separators, and italics feel while actually reading. If a sentence tripped me up while previewing on tram light, I rewrite it to be punchier. I also write in a plain-text editor or a notes app on my phone, which helps me avoid hidden formatting and makes copy-paste into AO3 cleaner. Lastly, I think of mobile readers’ context: people skim more, multitask more, and get interrupted. So I aim for clear anchors — chapter titles, time stamps, or little scene-setting lines — that let someone drop back in without re-reading three pages. It makes the whole ride smoother and keeps more folks coming back for the next chapter.