If you read fanfiction or web novels seriously, you know the shape of a long session. Open AO3, find the fic, glance at word-count — 180k — laugh at yourself, settle in. Three hours later your eyes feel like sandpaper, the page is still aggressively white, and you’ve still got chapter 14 of 22 to go.
Most of the tooling built for “dark mode” was designed for short web browsing — emails, articles, GitHub. Sustained-reading audiences (fanfic, web novels, light novels, long-form journalism) have the same eye-strain problem manga readers have, but the standard fixes are even worse here because text contrast matters more than artwork preservation.
Why long text reading is its own problem
Reading 50,000+ words in one session is a different physical load than browsing or watching:
- Constant near-focus. Your eyes’ ciliary muscles hold a single accommodation distance the whole time. They fatigue.
- High-contrast text on bright white. AO3’s default theme, Wattpad’s default theme, Royal Road’s default theme — all are black-text-on-white at 100% screen brightness. That’s the highest-contrast possible combo, which is great for skimming and terrible for a three-hour binge.
- Blue-channel saturation at evening. Default screen white is ~6500K. Late at night this signals “noon daylight” to your visual system — disrupts circadian state and increases perceived glare.
Why most “dark mode” tools fail at long-form text
The mainstream fixes all miss in a different way for sustained text reading:
- AO3 / Wattpad native skins. AO3 has community-built dark skins, but most flip to a high-contrast dark-on-black combo that’s actually worsethan light mode for long sessions — white-text-on-black makes eyes hunt edges (“halation”) on long passages. The best skins soften both sides, but you have to find one yourself.
- OS / browser dark mode. Useful at the OS level but inconsistent inside web reader views. Many sites override.
- Dark Reader and generic dimmers. Dim the whole page including nav, comments and the kudos/comment counters. Text gets flipped to bright on dark, which trades one eye-strain problem for another. Site navigation often breaks subtly.
- Blue-light apps (f.lux, Night Shift). Help systemically but apply to the whole screen, including UI you want crisp. And they have no relationship to the reading site you’re actually using.
What actually works
The principle is the same one that works for manga: replace the flat dim with per-channel tone-mapping, scope it to the reader pane (not the whole site), and layer blue-light reduction on top as a separate axis. Specifically for text reading:
- Warm cream > pure black background. Replace harsh-white with paper-cream. Black text stays black (it’s already black), and now the contrast feels like an actual book instead of a phone flashlight. Most fanfic readers report this is the single biggest change.
- Tune blue light independently. Daytime: leave it. Evening: bump to Med. Late night: High. The reduction is biased toward highlights (the bright cream background) so the text strokes don’t get muddied.
- Keep the nav & comments at full brightness. You still want to see the comment count, kudos button, next-chapter link. Scope the filter to the actual reading container, not the page chrome.
- Increase the reader font size. Smaller, separate fix. Every reading site has a font-size control buried in settings; use it. Eyes work less hard on 16–18px than they do on AO3’s default 13px.
For PDFs and scanned books
The same principle works on Chrome’s built-in PDF viewer and on image-based scanned-book viewers like Archive.org’s BookReader. Both render content as images inside a viewer container — exactly the pattern MochiDim’s built-in manga selectors handle. Enable it on the site and the warm dim applies to every scanned page.
Read longer. Read kinder.
Long-form reading — manga or text — is exactly the use case screens are worst at and tools are mostly under-built for. The fix isn’t a darker page; it’s a warmer one, scoped to the actual reading container, with blue light handled as a separate axis. Whether you’re finishing a 22-chapter slow-burn or a 60-chapter shounen marathon, the principle is the same.
If you want the tooling part handled by an extension that actually understands both manga reader sites and the generic case, MochiDim is the one we make. Same one-time pricing as the rest of the studio. No tracking inside the extension.
If this was useful
The extensions we make solve this end-to-end.
One-time payment, lifetime license, no tracking inside the extensions. The studio that wrote this article.