
Direct Answer: How to Fix KDP "Text Outside the Margin" Rejection
To fix the "Text Outside the Margin" rejection on Amazon KDP, identify the offending page from the KDP Print Previewer, open your source file, and check for 4 common culprits: (1) running headers or page numbers placed less than 0.375” (9.6 mm) from the trim edge; (2) hidden punctuation, spaces, or empty paragraph returns extending beyond the 0.25” outer safe margin; (3) image or table bounding boxes extending beyond margins without full bleed enabled; or (4) insufficient inside gutter margins for your page count. Increase your outer margins to 0.50” and inside gutter to KDP specs, re-export as PDF/X-1a, and re-upload.
1. Anatomy of a Rejection: The 5 Hidden Causes of KDP Margin Errors
Amazon KDP rejects interior PDFs when its automated glyph-coordinate scanner detects any character, rule, or vector element whose bounding box crosses the trim-relative safety threshold—typically 0.25" from trim on all sides, with a larger 0.375"–0.5" requirement inside the gutter. No human reviews the first pass. The script reads embedded font geometry, not what your eyes see on screen.
That single sentence is the entire game. Every "Text Outside the Margin" rejection traces back to a measurable coordinate violation, and every one of those violations is fixable in under ten minutes once you know which of the five causes is firing. Below, each cause is dissected with the exact math KDP's scanner applies.
How the Scanner Actually Reads Your PDF
KDP's intake pipeline runs a two-stage automated analysis. Stage one extracts the MediaBox and TrimBox from the PDF container—these are the physical page dimensions your layout software wrote into the file header. Stage two walks the content stream, reconstructing every glyph's position from the text matrix (Td, TD, Tm operators), the font's embedded width metrics, and any transformation matrices applied to the text object.
The scanner then computes, for each glyph, a bounding rectangle: origin point plus advance width plus descender depth. If any edge of that rectangle falls outside the printable area, the file fails. One stray period in a footer, one tab character pushing a table cell 2pt past the edge, one invisible space in an empty text frame—each is enough to trigger rejection.
Critical detail: The scanner does not read visible ink. It reads character coordinates. A white-on-white character, a zero-opacity text layer, or a hidden annotation still counts. Designers who "hide" a stray character by making it white get rejected just the same as those with visible overflow.
Cause 1: Folios Placed Too Close to the Bottom Trim
Page numbers are the single most common trigger. KDP requires a minimum 0.25" (18pt) margin from trim on all four sides for body content, but folios sit in a zone where designers routinely push boundaries. A folio baseline placed 0.30" from the bottom trim edge looks fine in InDesign's preview. Then the descender of a "9" or the tail of a "g" in "Page 9" extends 0.08" below the baseline, landing at 0.22" from trim—a 0.03" violation that fails the file.
The math: bottom trim edge sits at y = 0. A folio with baseline at y = 21.6pt (0.30") and a 9pt font with 2.2pt descender depth places the lowest glyph pixel at y = 19.4pt, or 0.269". That clears 0.25" by less than half a point. Any rounding error in your PDF export—and Acrobat's PDF/X-1a conversion introduces them—pushes it under.
| Folio Position | Baseline from Trim | Descender Depth (9pt) | Lowest Pixel | Verdict |
|---|---|---|---|---|
| Aggressive | 0.28" (20.2pt) | 2.2pt | 0.249" | FAIL (borderline) |
| Standard | 0.35" (25.2pt) | 2.2pt | 0.319" | PASS |
| Safe | 0.375" (27pt) | 2.2pt | 0.344" | PASS |
| Conservative | 0.5" (36pt) | 2.2pt | 0.469" | PASS |
Fix: set your folio baseline to 0.375" minimum from trim. That gives you 0.094" of clearance below the descender—enough to absorb export rounding, font metric quirks, and the occasional tall numeral.
Cause 2: Running Headers Overflowing the Top or Outer Margin
Running heads carry chapter titles, and chapter titles run long. "Chapter 7: The Complete Guide to Automated Prepress Validation" set in 10pt small caps across a 5.5" text column will overflow. The scanner doesn't care that the header is decorative. It sees glyphs at coordinates beyond the printable box and fails the file.
Two failure modes dominate. First, horizontal overflow: the header string exceeds the text frame width, and the layout software either extends the frame (pushing glyphs into the outer margin) or wraps to a second line (pushing glyphs into the top margin). Second, vertical overflow: a two-line header with generous leading pushes the second line's ascenders above the 0.25" top threshold.
Diagnostic math: top trim edge at y = page height. A 6"×9" page has 648pt of vertical space. A header with first baseline at 0.40" from top (28.8pt below trim) and 12pt leading places the second line's ascenders at 28.8pt − 12pt − 7pt (ascender height) = 9.8pt from trim = 0.136". Well under the 0.25" floor. Rejected.
Fix: Truncate running heads to 40 characters maximum, set them in 9pt or smaller, and verify the header text frame's top edge sits at least 0.375" from trim. Use InDesign's "Story Editor" or Scribus's "Edit Contents" to check for overflow beyond the frame boundary.
Cause 3: Tables and Code Blocks Exceeding Horizontal Width
Non-fiction interiors live and die by tables. A table with six columns, each holding a 12-character data string, needs roughly 6 × 12 × 5.5pt (average character width at 9pt) = 396pt = 5.5". On a 6"×9" page with 0.75" inner and 0.5" outer margins, your text column is 6" − 0.75" − 0.5" = 4.75" = 342pt. The table overflows by 54pt—0.75"—straight into the outer margin.
Code blocks are worse. Monospaced fonts like Courier run 0.6em per character. A 9pt Courier line with 80 characters measures 80 × 5.4pt = 432pt = 6.0". That's wider than the entire page. The scanner flags every character past the 342pt boundary.
| Element | Typical Width | Max Column (6×9, 0.75"/0.5") | Overflow |
|---|---|---|---|
| 6-column data table, 9pt | 396pt (5.5") | 342pt (4.75") | 54pt |
| 80-char code line, 9pt Courier | 432pt (6.0") | 342pt (4.75") | 90pt |
| Wide figure with caption | 360pt (5.0") | 342pt (4.75") | 18pt |
Fix: reduce font size to 8pt (saves 11% width), increase page size to 7"×10" (adds 1" of column), rotate the table to landscape on its own page, or split into two stacked tables. For code, set at 7.5pt Courier (0.45em advance) and wrap at 62 characters.
Cause 4: Invisible Characters in Overflowing Text Frames
This is the cruelest cause because you cannot see it. A tab character at the end of a paragraph, an em space after a period, a carriage return inside an empty frame—each occupies horizontal or vertical space and each generates glyph coordinates the scanner reads.
Common sources: pasted text from Word (carries hidden tabs), copy-pasted web content (non-breaking spaces U+00A0), and auto-generated indexes (trailing tabs after page numbers). A single tab character at 9pt occupies 36pt of horizontal space. Place it at the end of a line already at 330pt width, and the scanner sees a glyph at 366pt—24pt past the 342pt boundary.
Detection: run Preflight in Acrobat Pro with "Show all text" enabled, or export to plain text and search for tab characters (ASCII 9), non-breaking spaces (U+00A0), and zero-width spaces (U+200B). In InDesign, turn on "Show Hidden Characters" (Cmd/Ctrl+Alt+I) and scan every page at 400% zoom.
Detection script (Python, pdfminer.six):
from pdfminer.high_level import extract_pages
for page in extract_pages("interior.pdf"):
for element in page:
if hasattr(element, "get_text"):
text = element.get_text()
if "\t" in text or "\u00a0" in text:
print("Hidden char at", element.bbox)
Cause 5: Symmetrical Margins Swallowing Content in the Gutter
This cause fails files even when every glyph sits inside the outer printable box. KDP requires a larger inner margin (the gutter, on the binding side) than outer margin. For a 300-page book, the minimum gutter is 0.625". For 500 pages, 0.75". For 800 pages, 0.875".
A designer who sets symmetrical 0.75" margins on all sides passes the outer check but fails the gutter check on odd pages (where the gutter is on the left) and even pages (where it's on the right). The scanner computes the gutter-relative coordinate for each glyph and flags any that fall inside the binding zone.
| Page Count | Min Gutter (Inside) | Min Outer | Symmetrical 0.75" Verdict |
|---|---|---|---|
| 24–150 | 0.375" | 0.25" | PASS |
| 151–300 | 0.625" | 0.25" | PASS (barely) |
| 301–500 | 0.75" | 0.25" | FAIL (0.75" = minimum, no buffer) |
| 501–700 | 0.875" | 0.25" | FAIL (0.125" short) |
| 701–828 | 1.0" | 0.25" | FAIL (0.25" short) |
Fix: calculate gutter from final page count, not from a template. Set inner margin to gutter minimum plus 0.125" buffer. For a 400-page book, that means 0.75" + 0.125" = 0.875" inner, 0.5" outer. Asymmetrical margins are mandatory, not optional.
Gutter formula: Inner margin = (page count ÷ 1000) × 0.25" + 0.5", rounded up to the nearest 0.125". For 400 pages: (400 ÷ 1000) × 0.25 + 0.5 = 0.6", rounded to 0.625". Add 0.125" buffer = 0.75" final inner margin.
Every one of these five causes produces the same rejection message. The scanner does not tell you which one fired. Your job is to eliminate all five before upload—because the second rejection costs you 24 hours of review queue time, and the third triggers a manual account flag.
Eliminate Amazon KDP margin rejection errors forever with certified automated typesetting
Never battle cryptic PDF preflight rejections again. BooklierAi automatically encloses all glyphs, headers, and tables inside strict KDP safe zones and generates compliant PDF/X-1a files.
2. The 0.25" and 0.375" Safe Zone Geometry: Exact Boundary Coordinates
Print is not a screen. A PDF page is a fixed coordinate plane, but a bound book is a physical object that gets clamped, jogged, stacked, and sliced by a guillotine weighing 1,800 kg. The blade does not care about your InDesign artboard. It cuts where the machine says it cuts, and the machine is only accurate to a stated tolerance.
KDP's safe zone rules exist because of that tolerance. Every margin number you see in the KDP documentation — 0.25", 0.375", 0.5", 0.625" — is not an aesthetic preference. Each one is a calculated offset derived from trim dimensions, mechanical shift, blade drift, and the physical geometry of the binding method. This section gives you the exact coordinates.
The Trim Line: A Nominal Dimension, Not a Guaranteed One
When you specify a 6" × 9" trim size, you are declaring the nominal finished dimension. A properly produced 6 × 9 paperback measures 6.000" × 9.000" to within a stated tolerance, but individual copies will vary. The trim line on your PDF is a coordinate: x = 0 at the left edge, x = 6.000" at the right edge, y = 0 at the bottom, y = 9.000" at the top. That is the target. The blade lands somewhere near it.
KDP accepts trim variance of ±0.0625" (1.6 mm) on the finished book dimension. This means a "6 × 9" book can legally arrive at 5.9375" × 8.9375" or 6.0625" × 9.0625" and still pass the platform's own quality spec. Your interior file must survive both extremes without clipping a glyph or dropping a folio.
The Mechanical Shift Variance: ±0.125" (3.2 mm)
This is the number most self-publishers never internalize. Industrial perfect binders and saddle stitchers run the printed block through a three-knife trimmer. The block is jogged against a front stop, clamped, and cut on three sides in a single pass.
Three separate error sources accumulate:
- Jog tolerance: the paper stack shifts against the stop by up to ±0.03" depending on stock caliper and humidity.
- Clamp compression: the clamp squeezes the block, and the outermost signatures compress slightly more than the center, producing up to ±0.02" of differential creep.
- Blade drift and back-gauge slop: the guillotine's back gauge repeats to roughly ±0.075" over a full shift.
Sum those and round up, and you get the industry-standard mechanical shift variance of ±0.125" (3.2 mm). In the worst case, the blade cuts 0.125" inside where you drew the trim line. Any ink in that 0.125" band is gone — sliced off and swept into the trim waste bin.
The 0.25" Outer Safe Zone: Exact Coordinates
KDP requires a minimum 0.25" (6.35 mm) margin from trim on the top, bottom, and outside edges. Here is the arithmetic behind that number:
The 0.25" rule is the shift variance doubled. Half of it absorbs the worst-case blade position; the other half is a buffer so that even a shifted cut leaves a visible white margin rather than text kissing the paper edge. A book with text flush to the trim edge reads as amateur — it triggers the "this was not professionally typeset" response in a reader's hand within about 0.4 seconds.
Exact boundary coordinates for a 6" × 9" page at 0.25" outer margins:
| Boundary | Rule | Coordinate |
|---|---|---|
| Left trim (nominal) | x = 0.000" | — |
| Right trim (nominal) | x = 6.000" | — |
| Outside safe-zone inner edge | x = 6.000" − 0.250" | x = 5.750" |
| Top trim (nominal) | y = 9.000" | — |
| Top safe-zone inner edge | y = 9.000" − 0.250" | y = 8.750" |
| Bottom safe-zone inner edge | y = 0.000" + 0.250" | y = 0.250" |
Every glyph, rule, ornament, and image must sit inside that rectangle. Vector art that bleeds past it is a defect, not a design choice, unless you have deliberately set a full-bleed element (which KDP handles separately and which requires extending artwork 0.125" beyond trim, not stopping short of it).
The 0.375" Header/Footer Minimum: Why It Is Larger
Running heads, folios, and footers get 0.375" (9.53 mm) instead of 0.25". The extra 0.125" is not arbitrary. Three reasons stack up:
- Vertical trim has two error sources, not one. The head and foot are cut in the same pass, so a single back-gauge error moves both. But the clamp compression on a 300-page block is measurably larger than on a 60-page block, and the top of the block compresses differently than the bottom. The effective vertical shift runs closer to ±0.10" than ±0.075".
- Folios are small, isolated glyphs. A clipped lowercase descender in a paragraph is survivable. A folio "7" sliced in half is a visible defect on an otherwise clean page, and it repeats 200 times.
- Reader ergonomics. A folio at 0.25" from the edge sits close enough to the paper edge that a thumb holding the book covers it. At 0.375", the number clears the grip.
For a 6 × 9 page, the header baseline should land at y = 8.625" (0.375" down from trim) or lower. The footer baseline at y = 0.375" or higher. If you are running a header rule (a thin horizontal line), the rule itself must sit inside the 0.375" boundary — a rule at 0.30" from trim is a rule that prints broken or missing on roughly one book in eight.
Exhaustive Margin Breakdown by Trim Size
The following table gives exact inner-edge coordinates for the four most common KDP trim sizes. "Outside" applies to top, bottom, and outer edge for body text. "Header/Footer" is the folio and running-head boundary. Gutter values assume a standard 200–400 page count; gutters scale with page count and are covered in a later section.
| Trim Size | Body Outside | Header/Footer | Inside (Gutter) @ 200 pp | Inside (Gutter) @ 400 pp | Live Text Width (200 pp) |
|---|---|---|---|---|---|
| 5.000" × 8.000" | 0.250" (6.35 mm) | 0.375" (9.53 mm) | 0.500" (12.70 mm) | 0.625" (15.88 mm) | 4.250" |
| 5.500" × 8.500" | 0.250" (6.35 mm) | 0.375" (9.53 mm) | 0.500" (12.70 mm) | 0.625" (15.88 mm) | 4.750" |
| 6.000" × 9.000" | 0.250" (6.35 mm) | 0.375" (9.53 mm) | 0.500" (12.70 mm) | 0.750" (19.05 mm) | 5.250" |
| 7.000" × 10.000" | 0.250" (6.35 mm) | 0.375" (9.53 mm) | 0.500" (12.70 mm) | 0.750" (19.05 mm) | 6.250" |
Live text width is the actual measure available for body copy after subtracting outside margin and inside gutter from the trim width. For a 6 × 9 at 200 pages: 6.000" − 0.250" − 0.500" = 5.250". At 400 pages the gutter grows to 0.750", so live width drops to 5.000". That is a 5% reduction in measure — enough to change line breaks across an entire chapter and, if you reflow mid-project, enough to redraw every page.
The Bleed Exception: 0.125" Beyond Trim
Full-bleed images invert the logic. Instead of stopping 0.25" inside trim, bleed artwork must extend 0.125" (3.2 mm) past the trim line on every bleeding edge. For a 6 × 9 page with a full-bleed cover-adjacent image on the outside edge, the image canvas runs to x = 6.125", not x = 6.000". The blade cuts somewhere between 5.875" and 6.125", and the bleed guarantees ink is present at whatever position the cut lands.
Two rules govern bleed, and violating either produces a white sliver:
- Bleed extension is always 0.125", matching the shift variance exactly. Any less and a shifted cut reveals paper.
- Bleed is never used for text. Text in the bleed zone is text you have agreed to sacrifice.
Verifying Your Coordinates Before Upload
KDP's automated preflight checks the PDF's MediaBox against the declared trim size and flags content outside the safe zone, but it does not catch everything. A 0.24" margin will often pass the automated check and still clip in production. Manual verification is your responsibility.
Three checks, run in this order:
- Measure the MediaBox. For a 6 × 9 trim, MediaBox must be exactly 432 × 648 points (6" × 72, 9" × 72). A MediaBox of 434 × 650 means someone left a bleed setting on and your trim is now off by 2 points on every edge.
- Draw a temporary 0.25" / 0.375" guide overlay. In Acrobat, use the Measure tool. In InDesign, use a locked layer with magenta rules at the exact coordinates. Any glyph crossing the rule gets moved.
- Check the folios specifically. Zoom to 400% on page 47. Is the folio baseline at least 0.375" from the bottom trim? On both odd and even pages? The even-page folio is the one that gets missed, because it often sits in a different master page than the odd.
Get the geometry right and the rest of the production pipeline becomes predictable. Get it wrong and every downstream decision — type size, leading, measure, chapter openers — is built on a foundation that will shift by a quarter inch the moment the guillotine drops.
3. Hunting Ghost Elements: Hidden Bounding Boxes, Hard Returns, and Hyphenation
KDP rejected your interior PDF. The error message reads: "Content extends beyond the printable area." You stare at the page. Nothing is there. No text, no image, no line. The page is white. The rejection is real.
This is the most common failure mode in print-on-demand prepress, and it is almost never a visible object. It is a ghost: an empty paragraph mark, a stray anchor point, a text frame whose bounding box exceeds the trim, or a soft hyphen that pushes a descender 1.8 points past the margin. KDP's automated validator does not care about intent. It measures coordinates. If an object's bounding box crosses the threshold, the file fails.
This section is forensic. You will learn to reveal what is hidden, map every object's coordinates, and eliminate the ghosts before they reach the validator.
Revealing Hidden Characters in Microsoft Word
Word hides its structural skeleton by default. Paragraph marks, tabs, spaces, and section breaks are invisible. They are also objects. A paragraph mark carries font size, line spacing, and space-after values. An empty paragraph at 12 pt with 10 pt space-after occupies 22 points of vertical space. On a page with a 0.5" bottom margin (36 points), three empty paragraphs consume 66 points and push the text block past the trim boundary.
Press Ctrl+Shift+8 (Windows) or Command+8 (Mac). Word reveals every non-printing character. The paragraph mark (¶) appears at the end of every line. A tab is an arrow (→). A space is a centered dot (·). A manual line break is a bent arrow (↵). A section break is a double dotted line labeled "Section Break (Next Page)."
Now scroll to the last page of each chapter. You are looking for a single ¶ sitting alone on an otherwise blank page. This is the trailing hard return. It is the most common cause of margin violations in Word-based interiors.
Why the trailing hard return fails: A blank page with one empty paragraph mark still generates a text block. The paragraph's line height (typically 14–16 pt for 11 pt body text) plus its space-after value (often 10 pt) creates a 24–26 pt object. If the page's bottom margin is 0.5" (36 pt) and the paragraph sits at the top of the page, it does not violate the margin. But if the paragraph inherits a "Keep with next" property or a style with 0 pt space-before, it can anchor to the bottom of the previous page's text frame and push the frame's bounding box 24 points below the trim. KDP measures the frame, not the visible glyph. The frame is the ghost.
To fix: place your cursor at the end of the last visible character on the final page of the chapter. Press Ctrl+Shift+8 to confirm you see the ¶. Press Backspace until the ¶ merges with the previous paragraph. Do not press Delete. Backspace removes the paragraph mark and collapses the empty line. Delete removes the character before the cursor, which may be a legitimate word.
Repeat for every chapter. A 12-chapter book with one trailing return per chapter produces 12 ghost pages. KDP's validator flags each one as a separate error.
InDesign Preflight: Building a Custom Profile for Overset and Margin Violations
InDesign's default preflight profile checks for missing fonts and RGB images. It does not check for overset text or objects outside the margin. You must build a custom profile. This takes four minutes and prevents 90% of KDP rejections.
Open Window > Output > Preflight. Click the Preflight Panel menu (the hamburger icon) and select Define Profiles. Click the + button to create a new profile. Name it "KDP 6x9 Interior."
In the left column, expand Text. Check Overset Text. Set the threshold to 1 character. InDesign will now flag any text frame where content extends beyond the frame's bounding box. Overset text is invisible on the page but exists in the file. KDP's validator reads the text stream, not the rendered page. A single overset character triggers a rejection.
Expand Objects. Check Objects Outside Margin. Set the margin values to match your KDP interior: for a 6" x 9" trim with 0.5" outside margins, enter 0.5" for top, bottom, and outside. Enter your gutter margin (typically 0.75"–1.0" depending on page count) for the inside. Click OK.
Now expand Links and Images. Check Missing Links and Modified Links. Expand Color. Check RGB Images and RGB Objects. KDP requires grayscale or CMYK for interior files. An RGB black (0,0,0) converts to a rich black in some RIPs, which can cause registration issues on press.
Click OK to save the profile. Select it from the Preflight Panel dropdown. The panel now displays a live error count. Click any error to jump to the offending object. The bounding box highlights in red.
| Preflight Check | Threshold | Common Ghost Source | Fix |
|---|---|---|---|
| Overset Text | 1 character | Text frame too small for content | Resize frame or reduce type size |
| Objects Outside Margin | 0.5" outside, 0.75" inside | Empty paragraph mark, stray anchor | Delete empty frame or paragraph |
| Missing Links | Any | Image moved after placement | Relink or embed |
| RGB Images | Any | JPEG exported from web | Convert to grayscale in Photoshop |
| RGB Objects | Any | Swatch defined as RGB | Convert swatch to CMYK |
The Mathematics of a Single Hyphen
Hyphenation is not a visual problem. It is a coordinate problem. InDesign's hyphenation engine breaks words at syllable boundaries. The hyphen glyph itself is 2–4 points wide at 11 pt type. If the word before the hyphen ends at 4.48" on a 4.5" text column, the hyphen extends to 4.52". The text frame's right edge is at 4.5". The hyphen's bounding box crosses the margin by 0.02" (1.44 points).
KDP's validator measures the bounding box of every glyph, including hyphens, em dashes, and punctuation. A 1.44-point violation is a violation. The file fails.
Hyphen Overflow Calculation
Text column width: 4.5" (324 pt)
Word "typography" set at 11 pt Minion Pro
Width of "typogra-" = 323.2 pt
Hyphen glyph width = 3.1 pt
Total line width = 326.3 pt
Overflow = 326.3 - 324 = 2.3 pt (0.032")
Margin violation threshold = 0 pt
Result: FAIL
The fix is not to disable hyphenation globally. That creates rivers of white space and loose lines. The fix is to adjust the hyphenation settings so the engine never breaks a word if the resulting hyphen would cross the margin.
Open Edit > Preferences > Hyphenation (Windows) or InDesign > Preferences > Hyphenation (Mac). Set Hyphen Limit to 1. Set Hyphenation Zone to 0p0. Set Minimum Word Length to 6. These settings force the engine to break words only when the hyphen fits entirely within the column.
For finer control, open the Paragraph panel menu and select Hyphenation. Uncheck Hyphenate Capitalized Words. Uncheck Hyphenate Last Word. Check Hyphenate Across Column only if your layout uses multiple columns.
Now run a manual check. Use Type > Show Hidden Characters (Ctrl+Alt+I). Look for hyphens at the end of lines. Zoom to 400%. The hyphen should sit fully inside the text frame's right edge. If it touches or crosses the edge, adjust the tracking of that line by -5 to -10 units. This pulls the word back without affecting the rest of the paragraph.
The Anchor Point Ghost
InDesign anchors are invisible zero-width objects. They attach to a specific character in the text stream. If you delete the character, the anchor remains. It has no visible glyph, but it has a bounding box. An anchor with a 1-point width and 1-point height placed at the edge of a text frame can cross the margin by 0.5 points.
To find anchors: open Window > Utilities > Scripts. Run the Find Anchored Objects script. InDesign highlights every anchor in the document. Delete any anchor that is not attached to a visible object.
To prevent anchors from crossing margins: select the anchored object, open the Anchored Object panel, and set Position to Inline or Above Line. Never use Custom positioning unless you manually verify the bounding box coordinates.
The 3-Point Rule: Before exporting to PDF, run a final check. Set your preflight profile to flag any object whose bounding box is within 3 points of the margin. This buffer catches rounding errors, hyphen overflows, and anchor ghosts that sit exactly on the boundary. A 3-point buffer on a 6" x 9" page is 0.04". It is invisible to the reader and invisible to the validator.
Export Settings That Prevent Ghost Rejection
Your export settings determine whether ghosts survive into the PDF. Open File > Export. Select Adobe PDF (Print). Choose PDF/X-1a:2001 from the preset dropdown. This preset flattens transparency, converts RGB to CMYK, and embeds all fonts.
Click Marks and Bleeds. Uncheck All Printer's Marks. KDP does not want crop marks, registration marks, or color bars. These marks extend beyond the trim and trigger margin violations. Set Bleed to 0" for top, bottom, and outside. Set Bleed to 0" for inside. KDP's 6" x 9" trim does not require bleed unless you have full-bleed images. If you do, set bleed to 0.125" and extend the image to the bleed line.
Click Output. Set Color Conversion to Convert to Destination. Set Destination to Gray Gamma 2.2 for black-and-white interiors or U.S. Web Coated (SWOP) v2 for color interiors. Set Profile Inclusion Policy to Include Destination Profile.
Click Advanced. Set Subset Fonts Below to 0%. This embeds every glyph in every font, including the hyphens and punctuation marks that cause ghost rejections. A 300-page novel with two fonts adds approximately 1.2 MB to the file size. That is a rounding error compared to the cost of a rejected upload.
Export the PDF. Open it in Adobe Acrobat Pro. Run Preflight (Ctrl+Shift+X). Select the PDF/X-1a profile. Check for Objects Outside Trim and Text Outside Trim. Acrobat reports every coordinate violation with a page number and bounding box measurement. Fix each one in InDesign. Re-export. Re-check. The cycle takes 90 seconds per iteration. It is faster than a KDP rejection and a 72-hour manual review.
Ghost elements are not mysterious. They are objects with coordinates. Reveal them, measure them, delete them. The validator has no imagination. It only sees numbers. You should see them too.
4. Fixing Header and Folio Placement: The Top/Bottom Margin Equation
Running heads and folios live in a zone most authors never think about: the space between the trim edge and the first line of body text. Get this zone wrong and the book looks amateur from across a bookstore aisle. Get it right and nobody notices — which is the entire point.
Most manuscripts fail here because the writer confuses two separate measurements that Word and InDesign treat as distinct values. They are not the same number. They are not even measured from the same reference point.
Distance from Page Edge vs. Distance from Body Text
Here is the distinction that trips up 90% of first-time book designers:
- Header margin (Word: "Header from Top"): the gap between the physical top trim edge of the page and the baseline of the running head text. This is measured from the paper's edge.
- Top margin (Word: "Top Margin"): the gap between the physical top trim edge and the first line of body text — usually the first line of a paragraph or the first line of a chapter title.
These two values stack. They do not overlap. If your Header from Top is 0.40" and your Top Margin is 0.80", the running head sits 0.40" down from the trim, and the body text begins 0.80" down from the trim. The clear space between the bottom of the running head and the top of the body text is therefore 0.80" − 0.40" − (header font height) ≈ 0.28"–0.32" for a 10pt header.
That gap is the breathing room. Remove it and the running head crowds the body text like a passenger leaning into your seat on a red-eye flight.
The Minimum Safe Values for a 6×9" Trade Paperback
For a standard 6" × 9" trim size — the dominant format for KDP paperback fiction and most narrative nonfiction — the industry floor for these values is well established. Printers need a minimum of 0.25" of clear space from any trim edge to prevent content from being clipped during the guillotine cut, which has a mechanical tolerance of roughly ±0.0625" (1/16").
But "printable" is not "readable." Here are the working minimums that produce a professional result:
| Setting (Word) | Minimum | Recommended | Measured From |
|---|---|---|---|
| Header from Top | 0.35" | 0.40"–0.45" | Top trim edge |
| Top Margin | 0.75" | 0.80"–0.85" | Top trim edge |
| Bottom Margin | 0.75" | 0.80"–0.90" | Bottom trim edge |
| Footer from Bottom | 0.35" | 0.40"–0.50" | Bottom trim edge |
Note the symmetry: the header zone and the footer zone should mirror each other. If your running head sits 0.40" from the top trim, your folio should sit roughly 0.40"–0.50" from the bottom trim. A book with a 0.30" top header and a 0.60" bottom folio looks top-heavy — the eye reads it as a printing error even if the reader can't articulate why.
TRIM HEIGHT: 9.000" │ ├─ 0.000" ─── TOP TRIM EDGE ────────────────── │ ├─ 0.400" ─── RUNNING HEAD BASELINE ────────── │ (Header from Top = 0.40") │ ├─ 0.800" ─── FIRST BODY TEXT BASELINE ─────── │ (Top Margin = 0.80") │ │ [ BODY TEXT BLOCK ] │ [ ~7.4" of live type ] │ ├─ 8.200" ─── LAST BODY TEXT BASELINE ──────── │ (Bottom Margin = 0.80") │ ├─ 8.550" ─── FOLIO BASELINE ───────────────── │ (Footer from Bottom = 0.45") │ └─ 9.000" ─── BOTTOM TRIM EDGE ───────────────
That diagram is the entire equation. Every value is measured from a trim edge, and the body text block is what remains after subtracting the top and bottom margins from the page height.
Microsoft Word: Where the Setting Actually Lives
In Word, the header and footer distances are not on the same dialog as the margins. This is why so many authors miss them.
- Go to Layout → Margins → Custom Margins.
- In the Page Setup dialog, on the Margins tab, set Top, Bottom, Inside, and Outside margins first.
- Click the Layout tab. Here you will find Header and Footer fields measured from the edge.
- Set Header to 0.40" and Footer to 0.45".
- Check the box labeled "Different odd & even" if you want mirrored running heads (author name on verso, book title on recto).
Word will silently refuse to render a header that overlaps the top margin. If you set Header from Top to 0.70" and Top Margin to 0.60", Word pushes the body text down to accommodate the header — quietly breaking your margin calculation. Always keep Header from Top at least 0.30" smaller than Top Margin. The 0.40"/0.80" pairing satisfies this with 0.40" of clearance.
InDesign: Master Page Guides and the 0.50" Header Line
InDesign gives you explicit control that Word hides. The workflow is guide-based, and once you set it, every page inherits the geometry.
- Open Master Pages (A-Master for body, B-Master for chapter openers).
- With the master selected, go to Layout → Create Guides.
- Set Rows to 2, Gutter to 0, and choose Margins as the fit reference. This creates a horizontal guide at the top margin and one at the bottom margin.
- Drag a new horizontal guide from the top ruler to exactly 0.50" below the trim edge (Y = 0.50"). This is your running head baseline guide.
- Drag a second horizontal guide to 0.50" above the bottom trim (Y = 8.50" on a 9" page). This is your folio guide.
- Place your running head text frame so its baseline snaps to the 0.50" guide. Set the text frame's top inset to 0.
Why 0.50" and not 0.40"? InDesign measures to the frame edge, not the text baseline. A 10pt running head with 12pt leading has roughly 0.10" of internal space above the cap height. Setting the frame at 0.50" places the actual baseline at approximately 0.40" — matching the Word value. This is the single most common InDesign mistake: designers set the frame at 0.40" and the running head prints 0.30" from the trim, dangerously close to the cut line.
Chapter Opening Pages: Drop the Running Head
Every chapter opening page in traditional book typography suppresses the running head. This is not stylistic preference. It is a structural rule with three justifications:
- Visual hierarchy. The chapter title is the dominant element. A running head competes with it for the reader's first glance.
- Redundancy. The running head repeats the chapter title the reader just encountered. Printing "Chapter 4: The Margin Equation" at the top of the page where "Chapter 4: The Margin Equation" appears as a 24pt display title is dead weight.
- White space. Chapter openers traditionally begin one-third to one-half down the page. The running head zone is absorbed into that intentional void.
In Word, apply a Different First Page header to each chapter's first page. In InDesign, create a separate B-Master with no header frame and apply it to the first page of each chapter via Page Attributes → Master Page Override or by using a paragraph style with "Start Paragraph: On Next Page" paired with a master page assignment.
The folio, however, has two acceptable treatments on chapter openers:
| Treatment | Folio Position | Used In |
|---|---|---|
| Drop folio | Bottom center, same 0.45"–0.50" from trim | Most trade fiction and narrative nonfiction |
| No folio | Suppressed entirely | Literary fiction, memoir, art books |
Drop folio is the safer default for KDP. Amazon's print-on-demand system does not require page numbers on every page, but readers and reviewers expect them. A chapter opener with a drop folio reads as intentional; a chapter opener with neither header nor folio reads as a production error to anyone who has handled a professionally typeset book.
The math is simple, but the execution is unforgiving. A 0.05" error in the header zone compounds across 300 pages into a book that looks self-published. Get the four numbers right — Header from Top, Top Margin, Bottom Margin, Footer from Bottom — and the interior disappears into the reading experience, which is exactly where it belongs.
5. The 10-Point Preflight Inspection Checklist Before Uploading to KDP
KDP's print pipeline is not a typesetter. It is a renderer. It takes your PDF, checks a handful of mechanical tolerances, and either accepts it or throws a rejection code. There is no human editor on the other end fixing your gutter. Roughly 60–70% of first-upload rejections trace back to four causes: wrong trim size, missing font embedding, gutter margins that violate the page-count table, and accidental bleed. Every one of those is preventable in under 30 minutes with the checklist below.
Run these ten checks in order. Do not skip ahead. Each one gates the next.
1. Verify Trim Size Matches the KDP Dashboard Selection Exactly
Open your document setup. Confirm the page dimensions equal your KDP selection to the thousandth of an inch. A 6" × 9" book is exactly 6.000" × 9.000" (152.4 mm × 228.6 mm). Not 5.98" × 8.98". Not 6.0" × 9.01". KDP's automated validator measures the media box of page one and compares it against the dashboard value with a tolerance of roughly ±0.005". Drift past that and you get a rejection before the file even renders.
Common failure: Exporting from Word or Google Docs at "Letter" (8.5" × 11") and forgetting to set a custom page size. The dashboard says 6 × 9, the PDF says 8.5 × 11, and the file is rejected in under 90 seconds.
2. Confirm the PDF Is Single Pages in Consecutive Reading Order
KDP expects one page per PDF page. No spreads. No printer's pairs. No imposed signatures. If your InDesign export used "Print Booklet" or your layout tool output facing pages as single PDF pages, the renderer will slice your spread down the middle and produce two half-books. Check page count: a 240-page interior must produce a PDF with exactly 240 pages, numbered 1 through 240 in the page thumbnails panel, matching your manuscript's folio sequence.
3. Check PDF/X-1a:2001 Compliance via Acrobat Pro Preflight
In Acrobat Pro, open Tools → Print Production → Preflight. Select the profile PDF/X-1a compliance. Run it. You want a green check and zero errors. PDF/X-1a:2001 forces four things: all color in CMYK or spot, no RGB or Lab, no transparency, and all fonts embedded. KDP will accept a non-X-1a PDF, but you are gambling on their renderer's tolerance for RGB blacks and live transparency. Don't gamble. Convert first.
4. Verify All Fonts Are 100% Embedded — No Subsetting Dropouts
Run File → Properties → Fonts. Every font listed must show "(Embedded Subset)" or "(Embedded)". If any font shows only its name with no embed status, that font is referenced but not carried in the file. The renderer will substitute a system font. Your 11/15 Minion Pro body text becomes Times New Roman at 11/13.2, and your line count per page shifts by 2–3 lines, throwing your gutter math off across the entire signature.
Subsetting is fine — it strips unused glyphs and keeps file size down. What kills you is a subset that dropped a character you actually used. This happens most often with accented characters, em dashes, curly quotes, and small caps. If your manuscript uses "é" on page 47 and the subsetter dropped it, page 47 renders a blank box.
| Font Status in Acrobat | Verdict | Action |
|---|---|---|
| Embedded Subset | Pass | None |
| Embedded | Pass | None |
| Name only, no status | Fail | Re-export with embedding enabled |
| Type 3 (bitmap) | Fail | Replace font or re-export as outlines |
5. Audit the Inside Gutter Margin Against the Exact Page Count
This is where most self-publishers lose money on reprints. KDP's minimum inside (gutter) margin scales with page count. The table is non-negotiable.
Add 0.125" (3.2 mm) as a safety buffer. A 320-page book needs 0.625" minimum, so set 0.750". Why the buffer? Because KDP's perfect binding clamps the spine, and pages pull inward during trimming. A page that measures 0.625" on screen may effectively lose 0.03–0.05" after binding. Text creeping toward the spine is the #1 complaint in one-star print reviews.
Remember: the gutter is the inside margin, which alternates. On odd (recto) pages, the gutter is on the left. On even (verso) pages, the gutter is on the right. If you set up your master pages correctly, this is automatic. If you set a single margin value across both, you have already failed this check.
6. Verify the Outer Margin Is at Least 0.375" (0.50" Recommended)
KDP's absolute minimum for the outside, top, and bottom margins is 0.25" (6.4 mm). Do not use it. Set 0.375" as your floor and 0.50" as your working value. The reason is thumb clearance. On a 6" × 9" paperback, a reader's thumb occupies roughly 0.35–0.45" of the outer edge when the book is open. Text set at 0.25" from the trim gets covered. Text at 0.50" survives.
For a 6" × 9" page with a 0.50" outer margin, 0.75" gutter, and 0.75" top/bottom, your live text block is 4.75" × 7.5". That's a 1.27:1 ratio — comfortable for 11/15 body text at 65–72 characters per line.
7. Confirm Running Headers Sit at Least 0.375" from the Top Edge
Headers carry the book title, chapter name, or author name. They must clear the trim by 0.375" minimum. Measure from the top trim edge to the baseline of the header text, not the cap height. If your header baseline sits at 0.30", the descenders on "g," "y," and "p" will clip during trimming. Trimming tolerance on KDP's bindery runs ±0.0625" (1.6 mm), so a 0.30" header can become a 0.24" header on a bad day.
8. Check Page Numbers Sit at Least 0.375" from the Bottom Edge
Same rule, opposite edge. Folios (page numbers) must clear the bottom trim by 0.375". If your footer baseline is at 0.35", you are inside the trim tolerance envelope. Move it up. Also confirm folios are suppressed on chapter-opening pages and on front matter (title page, copyright page, dedication) per standard trade convention.
9. Ensure No Bleed Elements Exist Unless "Bleed" Was Selected on the KDP Dashboard
Bleed is the extension of artwork past the trim line so it can be trimmed flush. If you selected "No Bleed" on the KDP dashboard, your PDF must contain zero elements touching or crossing the trim edge. A single decorative rule that ends at 0.001" from the trim is fine. A single rule that crosses it triggers a bleed error and rejection.
If you did select bleed, your page size must be 6.125" × 9.25" (for a 6 × 9 book), with 0.125" of bleed on the outer, top, and bottom edges. Mixed bleed and no-bleed pages in the same PDF is an automatic fail.
Fast test: In Acrobat, toggle View → Show/Hide → Rulers & Grids and set the ruler origin to the trim box. Any object crossing the 0.000" line on a no-bleed file is a fail.
10. Open in Adobe Acrobat, Zoom to 100% Print Size, and Visually Inspect Facing Pages
Automated checks catch geometry. Eyes catch everything else. Set view to Two Page View, enable Show Cover Page in Two Page View, and zoom to 100% (View → Zoom → Actual Size). Then walk the book page by page.
What you are hunting for at 100%:
- Widow and orphan lines stranded at the top or bottom of a page.
- Hyphenated words breaking across a page turn.
- Chapter openers that start on even (verso) pages instead of odd (recto).
- Running headers showing the wrong chapter name after a section break.
- Folios that vanish or duplicate on a spread.
- Images with visible compression banding or a shifted color cast.
- Straight quotes where curly quotes belong.
At 100%, one page turn takes about eight seconds. A 300-page book takes 40 minutes. That 40 minutes is cheaper than a $75 reprint proof plus two weeks of lost launch window.
Run all ten checks. Sign off on each. Then upload. First-time approval is not luck — it is arithmetic you did before KDP's renderer did it for you.

