Scrivener is a comprehensive writing tool developed by Literature & Latte for long-form writing projects including novels, screenplays, academic papers, and non-fiction works. Unlike standard word processors that treat documents as continuous pages, Scrivener uses a ring-binder metaphor where text is broken into manageable sections that can be composed in any order and viewed through multiple organizational interfaces. The software's core philosophy centers on flexibility—whether you outline meticulously before writing or discover structure through drafting, Scrivener adapts to your workflow rather than imposing one, making it the preferred tool for writers who need to manage complex, research-heavy projects with non-linear composition needs.
What This Cheat Sheet Covers
This topic spans 20 focused tables and 235 indexed concepts, 117 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: Binder Organization and Structure
The Binder is the spine of every Scrivener project — a hierarchical sidebar that holds your manuscript, research, notes, and trash in one place. Understanding how folders, documents, and the three root folders interact is the foundation of working efficiently in Scrivener.
| Feature | Example | Description | |
|---|---|---|---|
Draft folder containing: Chapter 1 Scene 1-1 Scene 1-2 Chapter 2 | • Left sidebar hierarchy displaying all documents, research, and structural elements • the primary navigation and organizational system for the entire project | ||
Draft → Part I → Chapter 1 | • Root folder where manuscript content resides • all items here are included in compile output by default • originally called "Manuscript" in older versions | ||
Research → Character Notes Research → Photos Research → PDFs | • Root folder for reference materials alongside writing • supports PDFs, images, web pages, and text files • not included in compile unless explicitly referenced | ||
Deleted scenes and notes | • Root folder for deleted items • can be restored or permanently removed • not compiled and isolated from active project | ||
Individual scene or section | • Basic writeable container • can hold any amount of text • displayed with a page icon • the building blocks of your manuscript | ||
Chapter 3 (containing 5 scenes) | • Organizational containers grouping documents hierarchically • can contain text themselves or act purely as structure • shown with folder icons | ||
Indented scenes under chapter | • Documents nested beneath parent folders or documents • create hierarchical depth • easily reordered via drag-and-drop | ||
Flag icons for status, book icons for chapters | • Visual cues applied to any binder item via Documents > Change Icon • dozens of built-in icons plus custom images and emoji • immediately recognizable in complex projects | ||
View only Chapter 5 and its scenes | • Temporarily focuses the binder on a selected folder and its contents, hiding everything else • breadcrumb trail shows location • reduces distraction in long projects | ||
Novel → Part → Chapter → Scene | • Nested structure allowing unlimited depth • folders can contain folders • drag-and-drop reordering maintains hierarchy | ||
Act I (containing chapters) | • Specialized folder type treating its contents as a group • behaves like a folder but can have distinct compile settings |