Atticus PDF Missing Chapters or Letters: How to Check Export Completeness Before Uploading to KDP

If you’ve proofread every chapter inside Atticus and exported with full confidence, only to find Atticus PDF missing chapters or letters once you actually open the file — or worse, once a physical KDP author’s proof lands on your desk — you’re not losing your mind, and you’re not alone. You scroll through your manuscript inside Atticus, everything is there, chapter headings intact, and you export. Then the PDF you uploaded, or the paperback that arrives, is quietly short a chapter, or a single letter has vanished from a heading you’ve checked a dozen times. This isn’t a hypothetical. It’s happened to debut authors who caught it only because they ordered a proof before hitting Publish.

Quick answer
Short answer: This is two different bugs wearing the same disguise. A missing chapter is usually a rendering/export glitch that re-exporting often (not always) fixes — one author watched their exact missing chapter reappear on a second export with no other changes. A missing single letter, especially in an italicized or stylized heading, points to a font-glyph problem tied to a specific typeface rather than a content-loss issue, and retyping the word doesn’t reliably fix it. Neither failure mode is covered by Atticus’s official export troubleshooting, which focuses on exports that fail to generate at all, not exports that generate incompletely. The only dependable defense is checking the actual exported file, page by page, against your own chapter count before you upload it.

Before going further into why this happens, it helps to actually watch someone work through a full Atticus print export, because the completeness check lives in the same Print preview screen most authors glance at and move past too quickly.

This walkthrough from Publish with Andy shows the exact export-and-review step this article is about: generating the PDF, then scrolling through it page by page to confirm the table of contents, chapter breaks, and headings all rendered the way the editor showed them.

Why Would an Entire Chapter Disappear From the PDF When It’s Still in Atticus?

Because the PDF export is a separate compile step that can silently drop content even when the source document in the editor is completely intact. One debut novelist described exactly this on r/KDP: “Chapter Two is missing in the print version and in the PDF I uploaded to Amazon, but mysteriously it’s in my latest Atticus version.” They only found out because they ordered an author’s proof.

The rendering/update-timing pattern

A separate, longer thread of complaints links the problem to software updates. One user reported exporting their book “after a few changes” and noticing the page count was “around twenty pages short” because the export “had ignored an entire chapter.” Crucially, they exported a second time with no further edits, and the chapter was back. That detail matters: it points to a transient fault in the compile/render step itself, not a permanent loss of content in the document, which is consistent with what the novelist above also experienced.

The custom-template trigger

In the same discussion thread, one author traced their version of the bug to a specific action: editing a custom theme after starting, specifically changing the trim size. That’s a plausible mechanical trigger — changing page dimensions mid-project can force Atticus to recalculate pagination across the whole manuscript, and a recalculation step is exactly where a chapter could get skipped on one pass and included on the next.

Why Would Only a Single Letter Go Missing in a Chapter Heading?

Because this looks like a different failure mode entirely: a font-glyph or kerning issue tied to a specific typeface and style combination, not a content-deletion bug. On r/selfpublish, an author reported that the letter “K” dropped out of a chapter heading reading “the Shucking Knife,” both in the printed proof and in the exported PDF — and that retyping the word didn’t fix it.

The font and italics clue

Two commenters on that same thread independently asked the same question: whether the heading was set in the Crimson Text font, and whether it was italicized. That’s a reasonable hypothesis rather than a confirmed cause, since nobody in the thread (including Atticus) confirmed a root cause, but it lines up with how PDF font embedding works in general: a specific glyph in a specific weight or style of an embedded font can fail to render or extract correctly if the font file’s character set has a gap, while the surrounding, non-italicized text in a different, more complete font renders fine. This is genuinely a different bug category from the missing-chapter problem above, and it deserves a different check.

Visible Content Loss vs. Invisible Text-Extraction Loss: Two Different Problems to Check For

A chapter that’s visibly gone from the page count is a layout problem you can catch by scrolling. A letter or word that renders fine on screen but doesn’t exist in the PDF’s underlying text layer is a text-extraction problem you can only catch by searching or selecting text — and the reverse is also possible: a character can be genuinely missing from the rendered page itself, as in the “K” report above, which is a visible loss with a font-level cause rather than a structural one. Treating every report as “the same missing chapter bug” is exactly the kind of overgeneralization worth avoiding, since the fix path is different for each.

Does Re-Exporting Actually Fix a Missing Chapter?

Often, based on the reports available, but not reliably enough to skip checking the new file. In the thread above, re-exporting restored the missing chapter with no edits to the manuscript itself, and a commenter on the novelist’s post gave the same practical advice: “You can just upload the revised one. This works best as you have not yet published.” Both point to re-export-and-recheck as the working first move, not a permanent fix you can trust blindly going forward.

Why “it worked once” isn’t the same as “it’s fixed”

None of the available reports include a confirmed root-cause explanation from Atticus itself, and the issue has been described across more than one software version, so there’s no basis for promising this won’t recur on your next export. The safer habit is treating every export as unverified until you’ve checked it, not just the first one after you’ve had a problem.

What Atticus’s Own Troubleshooting Page Covers — and What It Doesn’t

Atticus’s official PDF export troubleshooting guide is genuinely useful, but it’s built for a different failure: exports that don’t complete. It walks through missing book titles, chapters over roughly 8,000 words, oversized images, blank or 1,000-plus-word notes, pasted content carrying “foreign coding,” and fonts that “may not support all special characters.” Every one of those causes an export to fail to generate, stall, or error out visibly. None of them describe an export that completes successfully and simply leaves something out silently — which is exactly the gap the reports above fall into, and exactly why checking the finished file matters even when the export itself appeared to work.

The Chapter-by-Chapter Completeness Check, Step by Step

Run this before every upload, not just after you’ve already had a problem:

1. Note your chapter count in Atticus first. Open the chapter sidebar and write down the exact number of chapters, including any unnumbered front/back matter sections you expect to appear.
2. Check the Print preview page count before exporting. Atticus’s Print preview mode shows a page count once it finishes rendering — write that number down too.
3. Export the PDF fresh. Don’t reuse an older export sitting in your downloads folder; generate a new one from the current state of the manuscript.
4. Compare page counts. Open the exported PDF’s properties or just check the last page number against the Print preview number from step 2. A mismatch is your first red flag.
5. Scroll every page, not just chapter starts. Open the PDF in an actual reader and page through it start to finish once. This is slow and that’s the point — a missing chapter is easy to miss if you only check the table of contents links.
6. Zoom in on every heading that uses italics or a non-default font. Based on the letter-loss reports, stylized headings are the highest-risk spot for single-character loss, so give them a closer look than body text.
7. Select and copy a paragraph of text from the PDF. Paste it into a plain text editor. If the pasted text doesn’t match what you wrote, the issue is in the text layer, not just the visual layout.
8. Order the author’s proof or run KDP’s own Print Previewer before approving. Amazon’s upload page explicitly states that its Print Previewer checks your file for formatting errors you need to fix before publication — but that automated check is built to catch formatting-rule violations, not to confirm your chapter count matches what you wrote, so it is not a substitute for steps 1 through 7.

Common Mistakes That Make This Worse

• Trusting the Atticus editor view as proof the export is correct. Every report above started with the author seeing complete content in the editor. The editor view and the exported file are generated by different processes.
• Re-downloading instead of re-exporting. If you click the export button again but the platform just serves you a cached file, you haven’t actually tested anything. Make a small, trivial change (and undo it) if you’re not sure a fresh compile is happening.
• Only checking the table of contents links. A TOC link can still technically exist and jump to the right starting page even if content partway through that chapter got cut — scroll the pages, don’t just click the links.
• Assuming a KDP “file accepted” status means content-complete. KDP’s automated check and manual review are built to catch formatting-standard violations, not to verify your manuscript against your own source file.
• Treating one Reddit report as proof every Atticus user will hit this. These are real, documented cases, not a confirmed defect rate across every version or every account. Check your own file regardless of how common or rare this turns out to be for you.

Frequently Asked Questions

None of this means Atticus is unusable, and plenty of authors export clean files from it every day. But “it looked right in the editor” has already failed more than one author at the worst possible moment — after the file was already uploaded. A page-by-page check of the actual exported PDF, done the same way every time, costs you twenty minutes. Finding out from a reader review that Chapter Two doesn’t exist costs considerably more.