How To Format Completed Novel On Scrivener For Publishing And Submission

Formatting a completed novel in Scrivener requires utilizing the Compile feature to transform your modular manuscript into a standardized industry layout. By mastering metadata compilation, front matter organization, and typography overrides, you can export flawless files for traditional agent submissions or direct-to-consumer self-publishing platforms.

Preparation and Compiling Prerequisites

Transitioning your manuscript from a creative sandbox to a linear, market-ready document requires strategic pre-formatting checks. Before triggering the export sequence, you must ensure your project binder structure separates narrative content from non-printing notes, and your text styling adheres to baseline publishing conventions.

• Essential Equipment & Tools: Scrivener 3 (macOS or Windows), an active word processor (Microsoft Word, LibreOffice, or Apple Pages) for final validation, and a clear stylesheet guide for your target publishing medium.
• Mandatory Prerequisite Standards: Standard Manuscript Format requires 1-inch margins, double spacing, 12pt Times New Roman or Courier font, first-line indentations of 0.5 inches, and no extra carriage returns between paragraphs.
• Estimated Timeline & Scope: A meticulous clean-up of styles, section layouts, and metadata takes roughly one to two hours for a standard 80,000-word novel.

Step-by-Step Compilation and Export Execution

Step 1: Clean and Standardize Binder Typography

Review your binder to ensure that every scene and chapter uses a unified base font style rather than an erratic patchwork of copied web text or mixed document imports. Highlight your entire text inside the editor, right-click, and select "Convert Formatting to Default Style" to strip away rogue inline formatting.

Warning: Using direct inline formatting throughout your chapters will override your compiler settings. Always rely on Scrivener styles like "Body Text" and "Heading" so the compiler can globally adjust sizing and spacing at export.

Step 2: Configure the Compile Format Window

Press Control-Alt-S (Windows) or Option-Command-E (macOS) to open the Compile panel. Select your output format from the left sidebar, such as "Manuscript (Times)" for agent submissions or "Paperback" for self-publishing print-on-demand.

1. Choose your output target dropdown menu located at the bottom of the Compile overview panel, setting it to Microsoft Word (.docx), EPUB, or PDF depending on your distribution goal.
2. Expand the central section layout table in the Compile window to verify which binder folders and text documents are marked with a checkmark for inclusion.
3. Assign the correct "Section Type" to each binder folder tier, mapping folders to act as "Part" or "Chapter" breaks and sub-documents to act as "Text" scenes.

Step 3: Assign Section Layouts and Page Breaks

Click the gear icon or edit the section layouts to define how headings and scene breaks render on the final exported page. Configure your chapter titles to automatically enforce a "Page Break Before" rule so that every major division starts at the top of a fresh page.

Pro-Tip: Insert a custom separator icon (such as three asterisks or a hash symbol) in the Separators pane of the compiler to maintain clean scene transitions without relying on manual blank lines that can break during conversion.

Step 4: Assemble Front and Back Matter Folders

Create dedicated folders outside your manuscript manuscript folder in the binder specifically labeled "Front Matter" and "Back Matter." Populate these folders with title pages, copyright notices, dedication pages, and author bios, then map them in the compiler metadata tab to merge seamlessly into the final output.

Technical Compilation Parameter Specifications

Troubleshooting Common Scrivener Formatting Failures

• Root Cause: Double indents appearing in the exported Word document. Actionable Fix: Ensure that you have not combined manual Tab spaces at the start of your paragraphs with an active paragraph indentation rule inside the Compile format designer.
• Root Cause: Chapter titles missing or displaying text blocks instead of bold headings. Actionable Fix: Check the Section Layouts pane in the compiler and confirm that the binder documents designated as chapters have the title prefix checkbox enabled and mapped to a designated heading style.
• Root Cause: Inconsistent font sizes across chapters after exporting. Actionable Fix: Select all text in your binder, clear formatting overrides via the editor menu, and reapply your primary body style before reopening the compile interface.
• Root Cause: Orphaned section headings appearing at the very bottom of a compiled PDF page. Actionable Fix: Adjust your CSS or compile-time paragraph protection settings to enforce "keep with next" rules on all designated heading styles.

Frequently Asked Questions

How do I remove scene separator lines or symbols during compilation?

Navigate to the Separators tab within the Compile overview window and select the specific divider type used between your scenes. Change the dropdown menu setting from your custom symbol or line break to "Empty Line" or clear the field entirely to ensure a smooth, uninterrupted transition.

Can I include my manuscript word count automatically in the compiled document?

Yes, you can insert dynamic metadata placeholders, such as the dollar-sign token for word count, inside your custom title page or header settings. The compiler will calculate the exact active word count of all checked items in your manuscript binder at the moment of export.

Why are my paragraph indents disappearing in the exported EPUB file?

Ebooks rely on CSS stylesheets rather than fixed physical page measurements. Ensure your EPUB compilation settings use relative measurements like em-spaces for paragraph indentation rather than absolute point values or manual tab spaces.

How do I format running headers with my book title and page numbers?

Open the Page Settings or Header/Footer tab inside the Compile format designer. Use the available token insertion buttons to place your manuscript title on one side of the header and the automated page number field on the opposite side.

Perfect your manuscript's presentation today by running a test compile and refining your structural metadata in Scrivener. Download our comprehensive checklist to fast-track your next publishing or submission milestone.