Labs · Try your book
Your book, on a phone,
turning real pages.
Drop a novel txt and it lands inside the phone simulator on this page: encoding detected, chapters recognized, then real pagination with page-turn animation, paper and night themes, adjustable type. The first three chapters sample right here — the whole book reads in the app.
Drop a txt here, or click to choose
.txt (UTF-8 / GBK / UTF-16 auto-detected) · up to 64MB
The whole book parses locally in your browser — nothing uploads, nothing persists. Refresh and it's gone.
The demo phone is empty
Drop a txt in, or hit “Try our sample book” below
What's real in the demo
The parsing chain is the same one our book checkup tool runs: byte-order marks, BOM-less UTF-16 by byte pattern, strict then near UTF-8, strict then near GB18030 — decode evidence, not file extension. Chapter recognition ports the rule core of the app's txt importer, hardened against real library files: 第N章/卷 families, bare numeric headings, Chapter N with Roman numerals, prologue and epilogue markers, with download-site tables of contents dropped as dense duplicate groups.
The pagination is the phone simulator's actual page engine — fixed-width CSS columns measured against the viewport, so page counts respond to type-size changes the way a reader app's do. The end-of-sample page lists what the same file can do after an app import: branching continuation, per-chapter audiobook, comic albums.
What the demo doesn't do
It only samples: first three chapters (or the first 15,000 characters when no chapter structure is found), no reading-position memory, nothing survives a refresh. It won't sync your file into the app either — install, re-import the same txt, and progress starts fresh. Extreme heading styles recognize worse than the app's full importer, and epub stays app-side: a half-done browser unpacker would mislead more than this page's honest refusal.
FAQ
Why only the first three chapters?
The demo phone is a hands-on sample, not a reading app. Keeping the window at three chapters keeps a 30MB tome from flooding the page with DOM, and it keeps the promise honest: the full book — with progress memory, branching continuation and audiobook — reads in the app. The page tells you exactly where the sample window ends.
Does my file get uploaded?
No. The file is read, decoded and chaptered entirely in your browser; nothing leaves your machine and nothing persists — refresh the page and the book is gone. That's also why the demo can't remember your reading position.
The chapters look wrong — one giant chapter, or split at odd places.
Chapter detection ports the core rules of a production importer (第N章 families, numeric headings, Chapter N, prologue markers). Rare heading styles can defeat it — the app's full importer covers more shapes and supports manual splitting. If no chapters are detected, the demo samples the first 15,000 characters as a single chapter and says so.
Are the page turns real pagination or a scroll trick?
Real pagination: the text is laid out in fixed page-width columns, so pages break where the type actually breaks — change the font size and the page count re-measures. The turn animation is the slide mode from our phone-simulator engine; taps on the left and right edges flip, the middle toggles the reading chrome.