Chapter word targets
Set a target per chapter and how to count it. The current count sits above the editor and a progress bar fills under each chapter in the list.
See chapters →Not paste-and-copy from a chatbot. The AI reads the characters, world and hooks you keep in a story bible, continues from the text before your cursor, counts your chapter target, and exports files your platform accepts.
Free credits on signup · We never train on your writing · Cancel from the account page
Serials are read for structure and pace more than sentences. Chapter targets, consistent lore and a daily word count are what break first — so those are what we built around.
Set a target per chapter and how to count it. The current count sits above the editor and a progress bar fills under each chapter in the list.
See chapters →Characters, places, rules and planted hooks live as cards that attach to every AI request, so a side character does not change names in chapter 100.
See the bible →One shortcut reads the text before the cursor plus the bible and drafts the next paragraph. Insert at cursor, replace a selection or append — or discard it.
See continuation →"Continue this chapter by 600 words", "rename the protagonist everywhere", "make a bible card for the villain" — it reads the documents and edits them, with undo on every action.
See the assistant →Start from chapter-length conventions for Royal Road, Webnovel, Tapas and Korean platforms. Conventions change, so we always tell you to check before submitting.
For serial writers →Per-chapter TXT, DOCX and EPUB. Your manuscript is always your file, and the service never trains on it.
See export →Each step has a guide with the actual order of work. Follow them and you reach a first chapter in weeks, not months.
Regression, LitRPG, fantasy romance — pick one, then the platform where it sells. Chapter length and cliffhanger conventions follow from that choice.
Characters, world, rules and hooks as cards. It is the only way an AI stays consistent past chapter 30, and where you track payoffs.
No prologue. The protagonist is already moving. Use the free first-chapter tool for the opening and finish from the beat sheet.
Press ⌘J when stuck, hand bigger jobs to the assistant, and end every chapter on a reason to tap next.
Generated prose has an even rhythm. Read three times, then run manuscript feedback for flow, plausibility and bible conflicts.
Per-chapter TXT or DOCX. Re-check the platform's AI policy before you submit.
Read the guide →Conventions, not rules. Only ranges confirmed from community reports and contest guidelines are listed.
| Platform | Chapter length | Note |
|---|---|---|
| KakaoPage | 5,000–5,500 Korean chars | Community reports. Wait-for-free model makes cliffhangers essential |
| Munpia | 5,000–5,500 chars | Paid chapters. A 3,000-char minimum appears in some contexts |
| Naver Series | 6,000 chars or more | Floor stated in contest and official-serial guidelines |
| Novelpia | Free-form | Subscription platform; short, frequent chapters are common |
| Royal Road / Webnovel / Tapas | Roughly 1,500–3,000 words | Readers reward consistency more than any exact number |
Conventions shift with every platform update. Count the first chapters of three popular serials on your target platform before you submit.
Only items confirmed from each service's public pages as of September 2026. Anything we could not confirm is marked "unknown".
| Chapter word target | Bible attached automatically | Cursor-aware continuation | Agent you instruct in chat | Korean HWP-compatible export | No-training policy stated | |
|---|---|---|---|---|---|---|
| SparkLore | Yes | Yes | Yes | Yes | Yes | Yes |
| Novela | Unknown | Partial | Partial | No | Unknown | Yes |
| pensiv | Unknown | Yes | Partial | Partial | Yes | Yes |
| TypeTak | Unknown | Yes | Yes | Yes | Unknown | Unknown |
| ChatGPT / Claude chat | No | No | No | No | No | Partial |
"Partial" means a similar feature exists but does not work per chapter or needs manual steps. Check each service's latest documentation.
See detailed comparisons →A few runs per day, short output. Nothing you enter is used for training.
A chapter-shaped opening from a one-line premise.
The first-line hook plus a beat sheet.
Paste your draft; it continues in your voice.
Titles that fit the genre's conventions.
Cards with a wound, a want and a contradiction.
Six beats from setup to ending.
Policies differ by platform and change often. Some platforms and contests restrict AI-generated text or covers, or require disclosure. Use SparkLore for drafting, continuation and revision, rewrite the final text yourself, and check the platform's current policy before submitting.
The bible cards attach to every request, so the AI keeps names, rules and hooks straight without resending whole chapters. The same cards attach at chapter 100.
Generated prose runs even and uses too many connectives. Use the three-pass rewrite guide and manuscript feedback, and write the key scenes yourself.
The free tools run a few times a day without an account, and signing up grants free credits. Credit definitions and prices are on the pricing page, including whether unused credits roll over.
No. Manuscripts, bibles and requests are never used for training. It is stated in the terms and FAQ, and you can export everything at any time.
It can, but we do not recommend it. Chapters read better when you continue in pieces and write the cliffhanger and key scenes yourself. Asking the assistant for "the next 600 words" gives better results than "write chapter 12".
Fill the bible, open on an event, hit the target. We handle the rest beside you.