Scrivener Compile converts a writing project into DOCX, PDF, or ebook output through section types, layouts, formats, and output settings. When one mapping is wrong, the generated book can lose chapter breaks, apply unexpected formatting, or produce print and ebook files that need different repairs.

The fixes below can rescue an existing export. If the recurring problem is the Compile model itself, move one clean DOCX into Cambric and make the Cambric project the production source. Cambric keeps the editable manuscript beside live typeset pages and exports print PDF plus EPUB 3 from one local Windows-or-Mac project.

Skip the Compile loop and finish the book in Cambric.

Why Compile is so confusing

Compile isn’t one feature — it’s three systems layered on top of each other:

  1. Section types — labels you assign to each document in the Binder (chapter, scene, front matter, etc.)
  2. Section layouts — formatting templates that control how each section type looks in the output
  3. The Compile format — a master stylesheet that maps section types to section layouts and controls global settings like fonts, headers, and page size

The confusion comes from the indirection. You don’t format your chapters directly — you assign them a type, then assign that type a layout, then adjust the format that contains the layout. If any link in that chain is wrong, your output breaks in ways that are difficult to diagnose.

Scrivener 3 improved this system significantly over Scrivener 1’s approach, but the fundamental complexity remains. Most authors only compile a few times per book, which means you re-learn the system from scratch every time.

1. Chapters aren’t separating properly

Symptom: Your entire manuscript compiles as one continuous block, or chapters break in the wrong places.

Fix: In the Compile window, click the gear icon next to your compile format and check the Section Layouts tab. Make sure your chapter documents are assigned a layout that includes a page break before. The most common mistake: your Binder documents are set to “Section” type but the compile format only has a page-break layout assigned to “Chapter” type.

Quick check: Right-click any document in the Binder → Section Type → verify it matches what you expect.

2. Formatting looks nothing like what you typed

Symptom: You carefully formatted your manuscript in the editor — fonts, sizes, indents — but Compile produces something completely different.

Fix: This is by design. Compile overrides your editor formatting with the Section Layout’s formatting. You have two options:

  • Option A: Edit the Section Layout to match what you want (Compile → gear icon → Section Layouts → select your layout → Format pane)
  • Option B: Check “Override text and notes formatting” is unchecked in your layout if you want to preserve editor formatting

Most authors hit this on their first compile and assume something is broken. It’s not — Compile is just opinionated about separating writing formatting from output formatting.

3. Front matter isn’t appearing (or appears twice)

Symptom: Your title page, copyright page, or dedication doesn’t show up in the compiled output. Or it shows up twice.

Fix: Front matter in Scrivener requires a specific setup:

  1. Your front matter documents must be in a Front Matter folder (not in the Draft/Manuscript folder)
  2. In the Compile window, use the dropdown at the top to select which front matter folder to include
  3. If front matter appears twice, you likely have copies in both the Draft folder and a Front Matter folder

4. Headers, footers, and page numbers are wrong

Symptom: Page numbers start at the wrong number, headers show on the title page, or running headers display the wrong text.

Fix: This is controlled in the Page Settings tab of your compile format (gear icon → Page Settings). Key settings:

  • “Different header/footer on first pages” — check this to suppress headers on chapter openings
  • “Start page numbering at” — set to your preferred starting page
  • Use the <$p> placeholder tag for page numbers, <$projecttitle> for the book title, and <$surname> for the author name

The hard truth: Scrivener’s header/footer controls are limited compared to dedicated formatting tools. If you need different headers on verso and recto pages (standard in traditionally published books), you’ll need to either hack it with workarounds or post-process the output in another application.

5. The output looks fine on screen but wrong in print

Symptom: Your PDF looks good when you view it, but when you upload to KDP or IngramSpark, the margins are off, text is too close to the spine, or pages look unbalanced.

Fix: Print formatting requires specific knowledge about trim size, gutter margins, and bleed:

  • Set your page size to match your target trim size exactly (e.g., 5.5” x 8.5” for a standard trade paperback)
  • Add gutter margin (extra inner margin so text doesn’t disappear into the spine) — typically 0.5” to 0.875” depending on page count
  • Check KDP’s or IngramSpark’s margin calculator for minimum requirements

This is where Compile turns a writing problem into a print-production problem. The page settings still have to be translated into a complete interior, then checked against the printer’s current specifications and upload preview.

6. Ebook formatting is inconsistent across devices

Symptom: Your ebook looks fine on one Kindle but has spacing issues, missing scene breaks, or font problems on another.

Fix: Compile for ebook (ePub or Kindle) is more forgiving than print, but common issues include:

  • Missing scene breaks: Make sure your scene separators are actual separator elements, not just blank lines. In the Section Layout, enable “Separator between sections”
  • Font embedding issues: Scrivener’s ebook output doesn’t always embed fonts reliably. Stick to system fonts or accept that your font choices may not survive across all devices
  • Image sizing: If you have chapter heading images, set them to a percentage width rather than fixed pixels

7. You made changes but Compile output hasn’t updated

Symptom: You edited your text or changed Compile settings, but the output looks exactly the same as before.

Fix: Scrivener caches some compile data. Try:

  1. Close the Compile window completely and reopen it
  2. Save your project, close Scrivener, reopen
  3. If using a custom compile format, make sure you’re editing the project format, not a system format (look for the project name in the format list)

When to stop fighting Compile

Compile can generate usable output, but every edge case—box sets, large-print editions, complex front matter, and ornamental scene breaks—adds configuration that must be remembered and retested.

Move the production source to Cambric when:

You keep re-learning it. If you publish once or twice a year, you’ll forget the details between books. Compile rewards frequent use and punishes occasional users.

You’re losing time, not saving it. If Compile configuration and generated-file inspection take over the release, the writing project has become the wrong production system. Export one clean DOCX and continue in Cambric.

You want one file for print and ebook. Scrivener requires separate compile presets for each output format. Adjustments you make for print (fixed page sizes, gutters, specific fonts) don’t transfer to ebook, and vice versa. Tools built specifically for book formatting generate both outputs from a single project. Before you migrate, see how Cambric compares to the other formatting tools on exactly this point.

The Cambric alternative: migrate once and remove Compile

If Compile is not worth maintaining, the cleanest workflow is:

  1. Export one clean DOCX. Include approved text, chapter titles, visible scene markers, italics, and intentional special elements. Exclude research notes, comments, and drafting metadata.
  2. Import the DOCX into Cambric. Verify chapter count, emphasis, scene breaks, images, headings, front matter, and back matter.
  3. Make Cambric authoritative. Continue final revision beside the live book pages and generate print PDF plus EPUB from that project.
  4. Archive the migration source. Keep the original project and DOCX for provenance, but do not maintain multiple competing production masters.

This is a one-time migration, not a permanent two-tool recommendation. Once the book is verified in Cambric, corrections and new editions should begin in Cambric so the manuscript and released interiors remain synchronized.

Move the production edition into Cambric.

Can Scrivener produce a print PDF for KDP?

Compile can generate PDF, but the operator must set trim, margins, running matter, pagination, and output behavior, then verify the complete file against KDP’s current requirements. Cambric provides the more direct visual production path because the composed pages remain visible while the manuscript is editable.

Should I learn Compile or switch tools?

Choose Cambric when you want the writing-to-publishing source to show live book pages and create both release formats without maintaining Compile presets. The right test is the actual manuscript: import its hardest chapter, inspect the pages, export PDF and EPUB, make one correction, and regenerate both.

Bottom line

Fix Compile when you need one immediate export. Replace Compile as the production system when the same mapping and inspection problems return across formats or releases. Cambric gives the book one local source for final text, professional pages, print PDF, and EPUB 3.

Get Cambric and stop rebuilding the final handoff.