How to read web novels offline.
A practical guide to downloading web novels onto your phone for real offline reading — the kind that survives airplane mode, basement gyms, and a subway tunnel that lasts seven minutes too long.
The best feature of any reading app is whether it works when the network doesn't. That sounds dramatic until you've sat through the third subway dead-zone in a row, watching a chapter loading spinner where there used to be a sentence. Or your seat neighbour quietly browsing a downloaded library while your reader app shows a polite "you're offline" screen.
The web novel ecosystem — Royal Road, WebNovel, NovelFull, AllNovel, NovGo — is a website-shaped ecosystem. It's built around chapter pages, comment threads, and rating widgets. None of that helps you on a flight. To read web novels offline you need to take the text out of the browser and put it on your phone, in a reader designed for it.
Here's how to actually do that — what works, what doesn't, and what to look for in a reader that won't quietly betray you the moment you switch off Wi-Fi.
Why offline reading still matters
"Just stream it" is fine for video. It's a bad idea for a 1.4-million-word novel you're mid-arc on. The places people read the most — commutes, planes, trains, beds — are exactly the places where signal is intermittent and bandwidth is metered. Three concrete reasons offline still matters in 2026:
- Reliability. A downloaded chapter is not subject to your carrier, the source site, or whether some ad network is having a bad day. Open the app, open the chapter, the words are there.
- Speed. Offline rendering is instant. No HTTP, no cold cache. You tap chapter 47 and it appears.
- Privacy. Every "online" page view is a row in someone's analytics database. A locally-stored chapter is read silently.
And the obvious one: airplane mode. If you read on flights, on subways, in elevators, in basements, in cabins — offline isn't a nice-to-have. It's the product.
The wrong ways to "save" a web novel
People try a few approaches before they find a real offline reader. Most break in subtle ways:
Browser "Save Page" / Reading List
Safari's Reading List, Chrome's Read Later, Firefox's Pocket integration. These save one page at a time, often in HTML form, with the original site's CSS and ads baked in. They handle one chapter, badly. They don't handle 600.
PDFs from "novel dump" sites
Tempting, often pirated, almost always stale. The novel updated last week; the PDF was generated last year. PDFs also reflow badly on a phone — you'll spend more time pinching than reading.
Screenshots
Yes, people do this. No, it's not searchable, syncable, or sane.
Generic ebook readers (with manual EPUB compilation)
Moon+ Reader, KOReader, FBReader. Excellent apps. They were built for EPUBs, not for a web novel that grows by three chapters a week. To use them you'd compile EPUBs yourself with a separate tool, and re-compile every time the novel updates. The setup is real work and goes stale fast.
All of these are workarounds. You want the app you read in to also be the app that downloads.
The right way: a real offline reader
A purpose-built offline web novel reader does three things the workarounds can't:
- Understands novel structure. Title, author, chapter list, ordering, cover. Not "a saved page" — a saved novel, with chapters as first-class objects.
- Downloads in batches. One tap to queue 200 chapters. The download runs in the background; you can already start reading chapter 1 while chapter 200 is still in flight.
- Updates incrementally. Next time you open the novel, the reader checks the source for new chapters and offers a one-tap "download missing" action. No re-running a tool, no rebuilding an EPUB.
This is the category that includes open-source readers (LNReader, Tachiyomi-style forks for novels) and our own Arc Reader. They differ in style and source breadth, but the offline model is the same. Pick whichever feels right — offline support is table stakes; the differentiation is in how the reading itself feels.
We make Arc Reader. The walkthrough below is written for it specifically because it's the one we know cold — but the principles transfer. Look for: real local storage (not cache), batch downloads, background updates, no-account default.
Walkthrough: 700 chapters in under a minute
Concretely, on a fresh install of Arc Reader, here's the path from I have a novel URL to I'm reading offline on a plane:
- Install Arc Reader. App Store or Google Play. Open the app. Tap "Start as guest" — no account needed.
- Paste a novel URL. From Royal Road, WebNovel, NovelFull, AllNovel, or NovGo. The novel URL, not a chapter URL — though either works.
- Wait one second. Arc Reader fetches the title, author, cover, and the full chapter list. You see a real novel object, not a saved page.
- Pick a download range. "All chapters", "Latest 50", or a custom slice. Hit Download.
- Start reading immediately. Once the first 10% of your batch is in, the app surfaces a "Start now" prompt. Chapter 1 opens in the offline reader while chapters 2-700 finish in the background.
- Switch to airplane mode whenever. The reader doesn't notice. There's nothing to load — it's all on your device. More on how downloads work.
On a decent Wi-Fi connection, a 700-chapter novel finishes downloading in two to four minutes, depending on the source. You can close the app; it keeps working in the background. Cellular downloads are off by default — toggle them in settings if you'd rather.
Storage, bandwidth, and updates
A few practical numbers, because they matter:
- Storage. A typical chapter is 30-80 KB of text. A 700-chapter novel is roughly 30-50 MB. Even an aggressive reader with 20 novels in heavy rotation tops out around 1 GB — less than a single podcast episode.
- Bandwidth. Downloading 700 chapters is tens of megabytes total. The same as 30 seconds of HD video. The Wi-Fi-only default exists less because it has to and more because there's no reason to pay for cellular when you don't need to.
- Updates. Most web novels update once or twice a week. The "check for new chapters" pass on a novel takes a fraction of a second; the actual download of new chapters is invisible. You'll never wait for it.
Reading the same novel on iPhone and Android
If you carry a phone for work and a tablet for reading, or you switch between an iPhone and an Android, you want one library that knows where you are in every novel. Arc Reader does this once you register an email account: library, progress, highlights, and bookmarks merge both ways — the most recent change always wins. Premium subscriptions restore across platforms with one tap.
The downloads themselves are per-device, by design. If you've downloaded a novel on your phone and open it on your tablet, the tablet does its own download — faster than the first time, because the reader already knows the chapter list.
FAQ
Will my downloaded chapters expire?
Not in Arc Reader. Once a chapter is downloaded, it stays on your device until you delete it. Cancelling Premium doesn't change anything that's already on disk.
Can I read books that aren't on Royal Road or WebNovel?
Arc Reader's first-class sources are Royal Road, WebNovel, NovelFull, AllNovel, and NovGo. The in-app browser handles a wider tail of smaller sources — you read inside the app, and chapters auto-cache as you go.
Does offline mode break TTS?
No. Native text-to-speech runs on-device, so it works on a downloaded chapter with no network. More on TTS reading.
What about translation? Can I translate a chapter offline?
Initial translation needs network — but once a chapter is translated, it's cached. Subsequent reads are offline. More on inline translation.
Paste. Download. Read.
Real offline. No accounts, no ads. iOS and Android.