Scrivener’s Compile feature converts your project into a finished document — ebook, PDF, or print file — but it is, by a wide margin, the most complained-about feature in any writing software. Forum threads on Literature & Latte’s own support board describe it as “convoluted and opaque,” “a confusing mess,” and — memorably — requiring “a doctorate in molecular engineering to get right.” One user reported spending a full year trying to learn Compile before giving up entirely.

The frustration is real, and it’s not because you’re doing something wrong. Compile is genuinely complex. Here’s how to fix the most common problems, and an honest look at when it makes sense to use a different tool instead.

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.

The 7 most common Compile problems (and fixes)

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 many authors find Scrivener falls short. Getting print-ready output that passes KDP’s automated checks often requires multiple upload attempts and manual adjustments. The KDP Print Submission Guide has the exact specs, but translating those specs into Scrivener’s Page Settings is trial and error.

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 is powerful enough to produce good output — authors with 20+ books have built reliable compile workflows. But it takes significant upfront investment, and every edge case (box sets, large print editions, complex front matter, ornamental scene breaks) requires more configuration.

Here’s an honest assessment of when Compile might not be worth the effort:

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 need print-ready output. Getting a PDF that KDP and IngramSpark accept on first upload — with correct margins, proper gutter, running headers on the right pages — requires precision that Compile makes tedious. Dedicated formatting tools like Cambric produce print-ready PDFs built to each store’s exact specifications, with automatic widow and orphan control, because that’s all they do.

You’re losing time, not saving it. Scrivener is a fantastic writing tool. But if you’re spending more time compiling than writing, you might be using it beyond its strengths. Many authors write in Scrivener and export a clean .docx to format elsewhere — keeping the writing tool and the formatting tool separate.

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.

The alternative: export from Scrivener, format elsewhere

If you’ve decided Compile isn’t worth the fight, the cleanest workflow is:

  1. Keep writing in Scrivener. It’s still the best tool for structuring long manuscripts, managing research, and organizing scenes
  2. Compile to .docx with minimal formatting. Use a bare-bones compile format — just export clean text with chapter breaks. Don’t fight fonts, headers, or page layout
  3. Import the .docx into a formatting tool. Cambric imports Word documents and preserves chapter structure, italics, bold, and scene breaks — the things Scrivener can reliably export

This two-tool workflow (Scrivener for writing, a dedicated formatter for output) is increasingly common among prolific indie authors. You keep Scrivener’s strengths — the Binder, the corkboard, snapshots, research folders — without suffering through Compile for production-quality output.

FAQ

Can Scrivener produce KDP-ready PDFs?

Yes, but with significant manual effort. You’ll need to set exact trim dimensions, calculate gutter margins based on page count, configure headers and footers, and verify the output passes KDP’s file checks. Many authors report needing 3-5 upload attempts before KDP accepts a Scrivener-compiled PDF. By contrast, dedicated formatting tools produce files built to KDP and IngramSpark specifications out of the box.

Is Scrivener Compile better on Mac or Windows?

The Compile interface is identical on both platforms in Scrivener 3. However, Mac users have the option of compiling to Vellum-formatted output or using Vellum directly, which is Mac-only. Windows users who want a Scrivener-to-dedicated-formatter workflow can export .docx and import into Cambric, which runs natively on both Windows and Mac.

Should I learn Compile or switch tools?

If you publish frequently (4+ books per year) and are willing to invest a weekend learning the system, Compile can work. Build one reliable compile format, duplicate it for each new project, and don’t touch the settings. If you publish less frequently, or if you need polished print output with features like drop caps, ornamental scene breaks, and running headers, a dedicated formatting tool will save more time than it costs.

Can I use Scrivener and Cambric together?

Yes — and many authors do exactly this. Write and organize in Scrivener, compile a clean .docx with chapter breaks, then import into Cambric for professional formatting. You get Scrivener’s writing strengths and production-quality output without ever touching the Compile feature’s advanced settings.