Word Count in Scrivener: Scenes, Drafts and Compiled Manuscripts
Blog / BOOKS
Scrivener offers several word-count views because a project can contain much more than a manuscript. A scene's count, a project target, and the length of the compiled draft are different measurements. Choose the one that matches the task instead of assuming that every visible total describes your finished book.
Start with the document in the editor
When you are editing one scene or chapter, look at its word count in the editor footer. This is useful for comparing scene lengths or checking a short excerpt. Confirm that the editor is showing the intended document rather than a combined view of several Binder items.
A scene count helps answer a narrow revision question: did this dialogue become longer after the edit? It does not tell you how many words are in every chapter of the novel. Keep your measurement at the same scope before and after revising, particularly when you split one scene into two documents.
Distinguish planning targets from finished length
Writing targets are useful while drafting, but their purpose is progress tracking. A session target answers how much you intend to write during a period of work. A manuscript target answers how long you intend the project to become. Neither proves that your exported submission contains exactly the same material.
Suppose you draft 800 new words, then delete 250 words of repetition elsewhere. The manuscript becomes 550 words longer, even though your drafting effort included 800 new words. These illustrative numbers explain why writing output and net document growth are different ideas. Decide which one you want to track before comparing sessions.
Measure the manuscript, not all project material
A Scrivener project may contain research, character sketches, unused scenes, and front matter. For a manuscript-length check, inspect which documents belong to the draft and which are included in compilation. The software's organization is valuable precisely because you can keep supporting material without treating all of it as submitted prose.
For example, a 64,000-word story plus 6,000 words of research notes is not automatically a 70,000-word submission. If the notes are not part of the exported manuscript, counting them would misrepresent what the reader receives. Use your project's inclusion choices consistently and keep notes separate from the material you intend to send.
Check the compiled output before sending
Compilation settings can affect the final content. Titles, front matter, or excluded documents may cause the compiled file to differ from an editor-side count. Compile to the format requested by the agent, publisher, or recipient, then check that output with the receiving format's word-count feature.
If two counts differ, inspect content inclusion before blaming parsing. Does the exported file contain chapter headings? Did a scene fail to compile? Are notes or front matter included? A missing chapter matters much more than a small difference caused by a hyphenated word. Resolve structural differences first, then compare word boundaries if needed.
Keep a lightweight revision record
Record the draft version, the compilation scope, and the final exported count. Repeat the same procedure after substantial revisions. This makes your numbers comparable without turning writing into constant statistics checking. Literature & Latte's official guide describes several available views; consult the guide and the manual for your platform when menu names differ between editions.
Frequently asked questions
Is a project target the same as my final word count?
No. A target is a planning measurement. Check the compiled manuscript and its included content for a submission count.
Can I check an individual scene?
Yes. Scrivener provides document-level counts, including the editor footer described in its official guide.