A printed proof arrives and the spine title is off-centre by a couple of millimetres — visibly drifting onto the front cover, or vanishing onto the back. The cover artwork looked right on screen. The maths went wrong somewhere. In nearly every case, the wrong number went into a single multiplication: the spine width.
This note explains how the calculation actually works, the three numbers that go into it, and the four ways indie authors most often get it wrong before they upload.
The three numbers
Spine width comes from one piece of arithmetic. You need three numbers to compute it.
- Page count. The exact final page count of the interior PDF you intend to upload. Not your draft. Not your Word document. The final, paginated, exported PDF — including front and back matter, title page, copyright page, dedication, blank pages and any back-matter advert.
- Paper type. Whether the interior prints on white paper or cream paper, and whether the interior is colour or black and white.
- Paper bulk per page. The measured thickness of one page of the chosen paper, in inches.
The formula is:
spine_width = page_count × bulk_per_page
KDP publishes the per-page bulk figures for its three standard paper choices.
The KDP paper bulk table
The numbers are small. The differences between them are smaller still — but enough to push a centred title off-centre at any non-trivial page count.
| Interior | Per page (in) |
|---|---|
| Black and white on white paper | 0.002252 |
| Black and white on cream paper | 0.002500 |
| Premium colour on white paper | 0.002347 |
A 250-page paperback on white paper has a spine of 250 × 0.002252 = 0.563 in. On cream paper, the same book is 0.625 in — slightly under a sixteenth of an inch wider. A cover sized for one paper and uploaded against the other prints with the spine title drifting onto the front cover.
Three worked examples
To make the formula concrete, three common scenarios.
A 240-page novel on cream
A novel at 6 × 9 in, exported at exactly 240 pages, interior on cream paper.
spine_width = 240 × 0.0025 = 0.60 in
Full cover width = (2 × 6) + 0.60 + 0.25 = 12.85 in.
Full cover height = 9 + 0.25 = 9.25 in.
A 400-page non-fiction title on white
Non-fiction at 6 × 9 in, 400 pages, black-and-white interior on white paper.
spine_width = 400 × 0.002252 = 0.9008 in
Full cover width = (2 × 6) + 0.9008 + 0.25 = 13.15 in.
A 120-page premium colour photo book
A photo book at 8.5 × 8.5 in, 120 pages, premium colour on white.
spine_width = 120 × 0.002347 = 0.2816 in
Full cover width = (2 × 8.5) + 0.2816 + 0.25 = 17.53 in.
The spine is thin enough at 0.28 in that spine text is technically allowed (the 79-page minimum is met) but reads as cramped. Some authors choose a wordless spine at this thickness anyway.
The 79-page rule
KDP does not allow spine text on books under 79 pages, regardless of paper. The spine is too thin to print legible type — the band of paper isn't wide enough for the ink to register cleanly, and a smudged or misregistered spine looks worse than no title.
If your book is under 79 pages and you want a spine title, the options are:
- Pad the book to 79 pages or more with front matter, back matter or intentional blank pages.
- Move to a paper type that produces a thicker spine at the same page count — cream is thicker than white per page.
- Accept a wordless spine. A clean colour band along the spine, without text, reads as a deliberate choice. The book sits on a shelf as a thin coloured marker — appropriate for chapbooks, novellas, photo books and short non-fiction.
Why covers misprint
The maths is simple. The mistakes are predictable. The four common ones.
Wrong page count
The cover was sized for a 280-page draft. The interior was rewritten and the final export came out at 296 pages. Cover spine width is 0.7 in (sized for 280); actual book spine is 0.74 in. The cover wraps the book and the spine title sits 0.04 in off-centre — visibly drifting onto the front cover.
Cause: computing the cover too early.
Prevention: export the interior first, record the final page count, compute the cover against that number.
Wrong paper assumption
The cover was sized assuming black-and-white on white (0.002252 in per page). The interior was uploaded as black-and-white on cream (0.0025 in per page). A 300-page cover is 0.6756 in spine; the actual book is 0.75 in. Spine title off by 0.07 in.
Cause: picking the paper at upload time, after the cover is already sized.
Prevention: decide on the paper before computing the spine, and stick with it through both files.
The clean-number fudge
The author rounds the spine width to a convenient figure — "let's call it 0.7 in" — for design tidiness. The actual computed width is 0.6756 in. The cover wraps the book and the spine title prints with a few hundredths of an inch of drift.
Cause: small rounding errors look harmless until the proof arrives.
Prevention: use the exact computed number, to four decimal places if needed. The printer respects the precision.
Cover and interior briefed separately
A cover designer was given the trim, page count and paper at one moment. The interior was finalised later. The page count drifted. The cover was never re-briefed.
Cause: the cover was briefed before the interior was final.
Prevention: the order is always interior first, then cover — and the cover designer needs the final page count from the exported PDF, not an estimate.
The spine safe zone
Even with the right spine width, type sitting too close to the fold can be trimmed or distorted. KDP recommends keeping spine text at least 0.0625 in (1.59 mm) inside each edge of the spine area.
For a 0.6 in spine, that leaves 0.475 in of usable text height — enough for a 10–12 pt typeface set vertically. For a 0.3 in spine, the usable height drops to 0.175 in. Spine type on thin spines lives in a narrow band, and small typefaces that look fine on screen become hairline at print scale.
A working rule: if the computed spine width is under 0.4 in, set spine type at 8 pt minimum, or skip it. If the spine is over 0.6 in, 10–12 pt reads cleanly. Anything thicker than 1.0 in supports a normal display weight or even a small ornament alongside the type.
A practical workflow
The reliable sequence that prevents most spine errors:
- Finalise the manuscript and lock the interior layout decisions.
- Export the interior PDF.
- Read the exact final page count from the export — not your draft estimate.
- Pick paper type and stick with it.
- Compute spine width: page count × bulk per page from the KDP table.
- Compute full cover dimensions: (2 × trim width) + spine width + 0.25 in, by trim height + 0.25 in.
- Lay out the cover at exactly those dimensions.
- Centre the spine title using the exact computed spine width, with at least 0.0625 in of margin on each long edge.
- Export the cover as a flattened PDF.
- Upload both files to KDP.
If the page count changes after step three, restart at step three with the new number. The temptation is to skip the rebuild because the difference is small. The shelf will see the difference.
Where Folio Format fits
Folio Format keeps the spine width computed live from the manuscript's actual page count and paper choice. When the interior changes, the spine recomputes; when the paper changes, the spine recomputes; when the cover is exported, the spine width carried into the file is the final number, not an estimate. The arithmetic above still applies — Folio Format runs it for you, and refuses to export a cover whose spine doesn't match the interior it ships with.
Last checked 22 May 2026. Always confirm current Amazon KDP and IngramSpark specifications before uploading final files. Folio Format is designed to help users export KDP-ready files and catch common publishing issues before upload; it makes no claim about platform acceptance.