typesetting.ai

How wide is a book spine?

Published 4 min read

By the typesetting.ai editorial team

A book's spine width is page count multiplied by the thickness of one sheet of the paper it is printed on. That is the entire calculation. There is no minimum beyond the printer's own, no rounding convention, and no design judgement in it.

The only thing you need to know is which number to multiply by, and that depends on what the pages are made of.

The multipliers

Amazon publishes a per-page thickness for each paper stock it offers:

Paper Inches per page
Black and white on white 0.002252
Black and white on cream 0.0025
Premium colour on white 0.002347

Cream is the thickest, which surprises people who assume the difference is purely cosmetic. It is not: the same manuscript on cream paper produces a visibly fatter book.

What that looks like

The same book, at four lengths, on each stock:

Pages White Cream Premium colour
80 0.180″ 0.200″ 0.188″
150 0.338″ 0.375″ 0.352″
250 0.563″ 0.625″ 0.587″
300 0.676″ 0.750″ 0.704″
400 0.901″ 1.000″ 0.939″

At 300 pages the difference between white and cream is about a sixteenth of an inch. That is invisible on a shelf and fatal in a cover file: submit a wrap-around cover built for white paper and print on cream, and every element on the spine shifts by that much — usually enough to pull spine text onto the front face.

Below 80 pages there is no spine text

Amazon's wording is that spine text is printed on books with more than 79 pages. Eighty is the first page count that qualifies; seventy-nine is not.

A cover with spine text on a shorter book is rejected, not silently corrected. Worth knowing before you design a cover around a spine title, because a seventy-page poetry collection is exactly the sort of book that runs into it.

At the low end the spine is barely there anyway: eighty pages of white paper is 0.180″, about the thickness of two stacked credit cards. Text at that size has nowhere to go.

The full cover is one flat sheet

A paperback cover is not three files. It is one image: back cover, spine and front cover side by side, with bleed on the outside edges.

For a 300-page 6 × 9 book on cream paper:

width  = 6″ + 0.750″ + 6″ + 0.125″ + 0.125″  = 13.000″
height = 9″ + 0.125″ + 0.125″                =  9.250″

Two trim widths, plus the spine between them, plus an eighth of an inch of bleed on the left and right edges only — the joins between the panels are interior and get none. Height is the trim height plus bleed top and bottom.

Bleed is the margin of error for the trimming blade. Anything that should run to the edge of the finished book has to extend into it, because the cut lands within about a sixteenth of an inch of where it was aimed, and a background that stops exactly at the trim line will show a white sliver on some copies.

The order this has to happen in

Spine width depends on page count. Page count is not something you decide — it is an output of the interior, which depends on your trim size, type size, leading and where chapters open.

So the sequence is fixed:

  1. Format the interior.
  2. Read the final page count off it.
  3. Calculate the spine from that number.
  4. Build the cover.

Doing it in any other order means guessing the page count, and a guess that is twenty pages out on cream paper puts the spine 0.05″ off — enough to be visibly crooked on a finished book.

This is also why changing the interior after the cover is done is more expensive than it looks. Adding a two-page dedication to a 300-page book moves the spine by five thousandths of an inch, which does not matter. Cutting a chapter and losing eighteen pages moves it by nearly a twentieth, which does.

One more thing

Round nothing until the end. The multipliers go to six decimal places for a reason — 0.0025 and 0.002 are only a rounding apart and produce a spine 0.15″ too narrow on a 300-page book, which is a rejected cover.

Checked against the source

The requirements on this page are published by the organisations below, not by us. We last read them in September 2026 and compared them against what the tool produces. If a requirement has changed since, the source is right and we are wrong — tell us and we will fix it.