🔍 Proofs and print quality

Order the proof. Then read it in daylight

A physical proof is the one check no screen can make for you. Paper is not backlit, ink spreads, and the spine stops being a number in a field and becomes an object you can hold at arm's length.

Preflight: what to check before you upload

Preflight is everything between "the file exists" and "the printer will accept it." Here is the list in the order it matters, and the difference between a rejection you can fix and an acceptance that costs you a print run.

White or cream paper?

Cream is the traditional stock for novels, white for anything with pictures. The choice also changes your spine width, because cream paper is thicker — so it has to be made before the cover is finished.

Color inside the book, and what it costs

A color interior costs a multiple of black-and-white on every copy printed, and an image a shade off neutral counts as color. It moves the lowest price you can sell at, and sometimes decides whether the book is viable.

Paper weight, cover finish, and how the book feels

Weight, opacity and laminate decide whether a book feels considered or cheap in the hand. They are chosen at the printer rather than in the file, and only a proof tells you the truth about them.

The proof came back wrong. Now what?

Nearly every first proof has something wrong with it. This is a triage guide: find your symptom, work out what actually caused it, and fix the file rather than guessing at the printer.

The proof checklist, front to back

A checklist to work through with the printed book in your hands, in the order you would physically inspect it: the outside, the structure, the pages, the details, and the one piece of arithmetic that has to agree.

Checking an ebook before you publish it

A print book gets a proof copy and the ritual that goes with it. An ebook gets neither, so most authors publish a file they have only ever seen in the previewer that made it. Here is the replacement.

Check the listing the way a stranger would

The store page is the last thing between a reader and a sale, and the one page authors never inspect. Open it on a phone, signed out, and read it as though you had arrived from a search.

Proofing on screen or on paper

They are not substitutes. A screen finds anything searchable and anything you can zoom into; paper finds everything physical, and a surprising number of typos. Here is which faults belong where, and the order that wastes the least money.

Checking the spine and the wrap on a real copy

The most common physical fault in a self-published proof is a wrap that landed slightly off. Here is how to inspect it on the copy in your hands, and how to tell a normal cut from a spine built on the wrong number.

Measuring your proof with a ruler

Ten minutes with a ruler catches what reading the proof cannot. Six measurements, the number each one should come to, and how to tell a normal cut from a file that no longer matches the book.

Proofing a hardcover

A hardcover proof tests things a paperback proof cannot reach: whether the wrap is centered on the boards, whether the corners turned cleanly, and whether the artwork beside your spine survived the hinge the cover actually opens on.

Checking a printed book for readability

A reader cannot pinch a paperback to make the type bigger. This is the pass where you read your own proof in ordinary light, at the distance a reader holds it, and find what is genuinely hard to see.

Comparing proofs from two printers

The same files sent to two printers come back as two different books — different thickness, different paper shade, different feel. Most of that is normal. Here is what legitimately differs, and what points at your file instead.

Timing your proofs around a launch date

A launch date slips because the proof schedule was never built backwards from it. Here is the order the blocks have to go in, the dependency most authors miss, and what to do when the days run out anyway.

Checking your fonts are really embedded

An unembedded font is the most common reason a print file is refused, and the one authors are most certain they have avoided. Here is what embedding means, how files lose it, and the thirty-second check that settles it.

Proofing a set of books together

A series has faults no single proof can show you: trim that does not stack, a spine title riding higher on one volume, color drift between print runs. Here are the checks, before the case is made.

Keeping a record of what you checked

A one-page log per proof turns proofing from a panic into a process. What to write down, why the column people skip is the one that saves you, and why the old proofs stay on the shelf.