Use a small set of formats consistently.
The rich-text toolbar supports paragraphs, second- and third-level headings, bold, italic, bullet lists, numbered lists, blockquotes, and scene breaks. Pasted content enters as plain text, so review its structure after pasting.
Keep the chapter title in the chapter title field rather than repeating it as a Markdown heading inside the body. Use H2 and H3 for sections within the chapter.
- Paragraph: Use for the main narrative or explanation.
- H2 and H3: Use for a clear section hierarchy inside a chapter.
- Lists: Use when sequence or comparison matters more than prose.
- Blockquote and scene break: Use sparingly to mark a quoted passage or a deliberate narrative transition.
Change the book without rebuilding it.
Add, rename, remove, and reorder chapters from the editor outline. Generate a selected chapter when only one part needs a new draft. Removing a chapter is a structural decision, so check version history or duplicate the project first when you may need the earlier arrangement.
A conflict warning stops one device from silently replacing another.
Every project carries a revision number. If another tab, device, or collaborator saves a newer revision before your current edit, the workspace asks you to resolve the conflict instead of overwriting the newer work without notice.
When this happens, read both versions, copy any unsaved passage you need to keep, refresh the project, and apply the intended change to the current revision. Avoid editing the same chapter in two tabs when possible.
Restore, branch, reuse, or share the manuscript.
Open Project tools from the manuscript workspace. Version history lists saved revisions that can be restored. Duplicate creates an independent project with its own chapter IDs and history. Save as template keeps the outline and chapter structure for another book.
| Need | Tool | Result |
|---|---|---|
| Undo a large saved change | Version history | Restore an earlier project revision. |
| Try a different direction | Duplicate | Create a separate copy without changing the original. |
| Reuse a proven structure | Save as template | Make the outline available when starting another project. |
| Get another person's help | Collaborate | Invite an editor who can change the project or a viewer who can only read it. |
Create a safe checkpoint before a risky edit.
Wait for the current save to finish, open version history to confirm the latest revision exists, then duplicate the project before a major restructure, full rewrite, or experimental generation. Name the copy for the decision you are testing, not just Copy 2.
Related help for the next step
Getting started with your first book project
Choose a book format, create a useful outline, draft at the right pace, and know what to review before you export.
Import documents, web pages, and source notes
Bring a PDF, DOCX, public web page, or pasted text into a project without losing sight of rights, extraction limits, or structure.
Export PDF, EPUB, DOCX, or a KDP preparation package
Choose the right output, set front matter and formatting, complete book metadata, and understand exactly what the KDP ZIP does not do.