Scrivener is the writing tool most serious KDP authors eventually adopt — and the one most new authors bounce off because its interface doesn’t work like anything else. This guide covers the core workflow: how Scrivener’s structure benefits long-form writing, how to set up a KDP project correctly, and how to compile to EPUB and PDF for upload to Amazon.
| 10-minute read | All levels |
Scrivener, developed by Literature and Latte, is a writing application built specifically for long-form writing projects. It is not a word processor in the conventional sense — it does not work like Microsoft Word, and authors who approach it expecting Word’s behaviour will find it disorienting. It is a project management tool for manuscripts: a place where the research, the outline, the character notes, the chapter drafts, and the front matter all live in one organised structure, accessible from a single interface, without the file management overhead that Word-based workflows require for projects of any significant length.
For KDP authors specifically, Scrivener’s value is in the writing and organisation phase — not in formatting, where dedicated tools like Atticus and Vellum produce more polished results with significantly less effort. The most effective workflow for most Scrivener-using KDP authors is to write and organise in Scrivener, then compile to EPUB or DOCX for final formatting in a dedicated tool or direct upload to KDP. This guide covers both the Scrivener-native compile workflow and the export-then-format workflow.
Why Scrivener Works for Long-Form KDP Writing
The core of Scrivener’s value for KDP authors is its Binder — the left-hand panel that organises your manuscript as a hierarchy of folders and documents rather than a single continuous file. Each chapter or scene is a separate document within the Binder; you see and work on one document at a time in the main editor, but the entire manuscript is accessible with a single click on any Binder item. This structure makes the specific problems of long-form writing significantly more manageable than in Word.
Moving a chapter requires dragging it to a new position in the Binder — no selecting, cutting, scrolling, and pasting. Reorganising a manuscript for a structural revision takes minutes rather than hours. Adding a character note or a research document to the project means creating a new item in the Research folder — it lives with the manuscript but outside the text flow, accessible while writing without disrupting the document. And Scrivener’s Corkboard view — which shows each document as a notecard you can read and rearrange — provides the kind of structural overview that is impossible to achieve in a single-document Word file regardless of length.
For series authors — who need to track character details, world-building rules, timeline consistency, and ongoing plot threads across multiple books — Scrivener’s project structure is particularly valuable. Each book is a separate Scrivener project, but series bibles, character references, and shared world notes can live in a dedicated reference project that both books can draw from. The K.M. Weiland guide to using Scrivener for editing at helpingwritersbecomeauthors.com covers the specific Scrivener features that support the editing and structural revision process in detail — the Rewrite Notes system, the Snapshot function for preserving draft versions before major revisions, and the Corkboard view for evaluating scene structure.
Setting Up a KDP Project in Scrivener
When you create a new Scrivener project for a KDP book, start from the Fiction or Non-Fiction template rather than the blank template. The templates pre-populate the Binder with the folder structure most KDP books need: a Manuscript folder containing chapter documents, a Front Matter folder for the title page, copyright page, and dedication, and a Research folder for notes and reference material. These can be customised to your specific needs, but starting from a template is faster and more reliable than building the structure manually.
Within the Manuscript folder, create a folder for each chapter. Within each chapter folder, create individual documents for each scene. This scene-level granularity is Scrivener’s key structural advantage over single-document writing: moving, cutting, or duplicating scenes is as simple as dragging documents in the Binder, and the Corkboard view lets you see all scenes at once as synopses.
Set your word count target in Project → Project Targets before you start writing. Scrivener shows your daily and total word count progress against the target in real time — a feature that, for authors who use daily word count goals as a writing discipline, provides the progress visibility that makes output more consistent. The Write Practice’s analysis of Scrivener’s benefits for writers at thewritepractice.com covers the word count goal system alongside the other organisational features that make Scrivener effective for sustained long-form writing projects.
The Compile Function: Scrivener to KDP
Scrivener’s Compile function converts your Binder structure into a publishable file. For KDP, the two relevant output formats are EPUB 3 (for ebook upload) and PDF (for print upload). Accessing Compile via File → Compile opens the compile window, where you select your output format and configure the formatting settings that determine how the exported file looks.
For ebook output, select “ePub 3 Ebook (.epub)” in the Compile For dropdown. Note that KDP no longer accepts MOBI uploads — Amazon retired the format in stages between August 2021 and March 2025 — so EPUB 3 is the correct choice for any current Kindle workflow. Scrivener’s default ebook compile settings are functional but not particularly polished — the output is valid EPUB that will upload to KDP without rejection, but the typography and layout will be basic. For most authors, Scrivener’s ebook compile is an acceptable route for a clean first upload, particularly for text-focused fiction where formatting complexity is low. For authors who want more control over the ebook’s appearance, the more reliable workflow is to compile to DOCX and import into Atticus for formatting before uploading to KDP.
For print output, select “PDF” in the Compile For dropdown. Scrivener includes two pre-configured paperback formats — 5.06″ × 7.81″ and 6″ × 9″ — that can be duplicated and adjusted for other KDP Print trim sizes. The print compile requires more configuration than the ebook compile, particularly for margin settings calibrated to your page count and trim size. Loreteller’s “Scrivener to KDP in 30 Minutes” practical export guide walks through the full Compile window — including the Section Layout assignments that determine which Binder items become chapters, the metadata configuration that controls headers and footers, and the post-export validation steps to confirm the generated file meets KDP’s technical requirements before upload.
Scrivener Organises Your Writing. Vappingo Polishes It.
Scrivener’s structure helps you write faster and revise more effectively. What it doesn’t do is catch the errors, inconsistencies, and continuity issues that accumulate across a long manuscript. Vappingo’s manuscript proofreading works from your exported DOCX or compiled file — reviewing the final text before it enters KDP’s pipeline.
The Recommended Scrivener to KDP Workflow
For most KDP authors, the workflow that produces the best results with the least friction is: write and organise in Scrivener, export to DOCX for editing and proofreading, then import the proofread DOCX into a formatting tool for final production. This keeps Scrivener in its strongest role — writing and organisation — while using tools better suited to formatting for the production phase.
The export process is straightforward: File → Compile → select DOCX → configure basic compile settings (chapter headings, front matter inclusion, page breaks between chapters) → compile. The resulting DOCX is a clean, structurally correct file that imports correctly into Atticus, Vellum, or Word for final formatting. Any tracked changes from a proofreading review can be accepted in the DOCX before import into the formatting tool.
The alternative — using Scrivener’s native compile for final formatting — is viable but requires more time investment in learning the compile settings to produce professional-quality output. Authors who want to stay entirely within Scrivener should invest in dedicated learning resources for Scrivener’s compile function before relying on it for production output. The KDP tools guide covers how Scrivener fits within the broader toolkit of tools KDP authors use, including how it compares to Atticus and Vellum for different stages of the publishing workflow. The KDP manuscript formatting requirements guide covers the technical specifications that your exported file — whether from Scrivener’s compile or from a dedicated formatter — must meet before upload. The table of contents for KDP ebooks guide covers how Scrivener’s compile handles TOC generation and what to check in the output file to ensure navigation works correctly on Kindle devices.
Scrivener vs Atticus and Vellum: Choosing the Right Tool
Scrivener, Atticus, and Vellum serve different purposes in the KDP author’s toolkit, and understanding the distinction prevents the common mistake of using one tool to do another’s job. Scrivener is a writing and organisation tool — it is best suited to the creation and revision of long manuscripts, particularly for authors who value structural flexibility during drafting and benefit from keeping all project materials in a single interface. Atticus and Vellum are formatting tools — they take a finished manuscript and produce beautifully formatted ebooks and print books with far less configuration effort than Scrivener’s compile function requires.
Most professional KDP authors who use Scrivener also use a dedicated formatting tool for final production. The two tools are complementary rather than competitive: Scrivener handles the months of writing and revision that produce the finished manuscript, and Atticus or Vellum handle the hours of formatting that convert it into a publishable file. Authors who try to use Scrivener for both writing and production-quality formatting typically find that the compile configuration required to produce polished output rivals the complexity of learning a dedicated formatting tool, for worse results. The principle that applies is: use each tool for what it was built to do. Scrivener’s compile is entirely adequate for producing a clean EPUB or DOCX to upload or import for formatting — it does not need to compete with Vellum’s visual polish or Atticus’s formatting flexibility to serve its role in the workflow effectively.
Authors who are choosing between Scrivener and a dedicated writing tool like Atticus — which now includes a writing mode alongside its formatting functions — should evaluate whether Scrivener’s organisational depth justifies its learning investment for their specific writing style. Authors who write linearly, without extensive structural revision, may find Atticus’s combined writing and formatting environment more efficient. Authors who revise structurally, work on complex series with substantial world-building, or benefit from keeping research and manuscript in the same project will typically find Scrivener’s organisational capabilities worth the learning curve. The Atticus review covers how its writing mode compares to Scrivener’s for KDP authors considering which investment to make.
