How to pair fonts in a book

A book’s typography is mostly invisible, and the pairing question is where it stops being so. Two faces that work let the reader forget them. Two that fight put a low hum under every page — the book looks off, and the reader who reports it will say the margins or the cover were the problem.

The discipline is small: one face for the text, one for the display, chosen against each other. What follows is how the choosing is actually done.

Choose the text face first

The text face does ninety-eight per cent of the work, and it is chosen for how it behaves at eleven point across hundreds of pages, not for how it looks in a specimen at sixty. The qualities that matter — even colour, open apertures, a large enough x-height, unrhythmic vowels — and the canonical candidates are covered in choosing a typeface for a novel. The short version: Garamond, Caslon, Bembo, Sabon, Minion, Janson, Baskerville, Palatino, and the modern open-source faces built for the same job — Source Serif, Alegreya, EB Garamond, Charter.

For nonfiction the field widens: technical books, manuals and reports can carry a sans text face, and some should. But a trade nonfiction book — memoir, history, business narrative — is still prose at book length, and the serif convention holds because it was calibrated for exactly that job.

The display face is then chosen against the text face, never first.

What “chosen against” means

Two rules, and they pull in opposite directions on purpose.

Contrast, in role and weight. The display face must be distinguishable at a glance from the text face, or headings look like a printing error in the body. Contrast comes from structure (a geometric sans against a humanist serif), from weight (a heavy face against a book-weight one), or from case and spacing (small capitals, letterspaced caps). One strong contrast is enough.

Agreement, in proportions. Beneath the contrast, the two faces must share a basic skeleton — similar x-heights, compatible widths, comparable colour — or the page reads as two documents. This is why random pairing fails: two excellent faces can disagree fundamentally, and no amount of sizing fixes it.

The test that catches most failures: set a chapter title in the display face above a paragraph in the text face, and squint. If the title looks like it belongs to the page — not the same, not a stranger — the pair works.

Proven pairs

Text face	Display partner	Note
Sabon	Akzidenz-Grotesk	The classic German pairing
Baskerville	Futura	Enlightenment serif against geometric sans
Garamond	Gill Sans	The classic British pairing
Minion	Myriad	Adobe’s workhorse pair
Caslon	Univers	Neutral, dependable, everywhere
Source Serif	Source Sans	Designed together, open-licensed
Alegreya	Source Sans	Warmer text, same free licence

These are not laws, but each has carried thousands of books, and a debut designer learns more from setting a chapter in three of these pairs than from browsing a font menu for an hour.

Two shortcuts. First, one family with weights is a complete answer: a text face with a true bold, set large and letterspaced, carries chapter titles, and the book gains coherence — this is how many contemporary literary designs work. Second, a third face earns its place only when it has a distinct job: a mono for code, a condensed sans for tables and captions in dense nonfiction. A fourth face is almost always one too many.

What nonfiction adds

Nonfiction asks more of the display layer than fiction does: more levels of subheading, sometimes numbered; callouts and boxes; tables; captions. The pair has to survive all of it.

Practical consequences: the display face needs a good bold and enough sizes to build a hierarchy without straining; tables want a face with clear numerals — tabular figures, where every digit takes the same width, so columns of numbers align; and if the book has both an editorial voice and reference matter, the third face (usually the sans) takes the reference half.

Licensing: the part that bites later

Fonts are software, and embedding one in a PDF or an EPUB is copying its outline data into your file. Print-on-demand platforms require embedding — an unembedded font is a rejected file, per the print-ready checklist — and most reading systems embed whatever the EPUB carries.

Which means the licence has to permit it:

• Open Font Licence (OFL) fonts — the Google Fonts catalogue and much of the open-source world — permit embedding and commercial use freely. This is why they are the safe default, and why faces like Source Serif and Alegreya matter beyond their quality.
• Commercial licences usually permit embedding in documents but the terms differ per foundry: desktop licences are not automatically embedding licences, and a licence that covers a print PDF may say nothing about an EPUB. Check before the book is built on the font.
• System fonts — the ones already on your computer — are the commonest trap: “it came with my Mac” is not a licence, and Microsoft’s and Apple’s bundled fonts generally cannot be embedded in a book you sell.

The practical habit: decide the pair, check both licences for embedding and ebook use, then build. Retypesetting a book after an export fails is the expensive order.

---

A good pair is invisible for four hundred pages, which is the entire point: the reader meets the book’s voice, never its wardrobe. The proof is always on the page — set a real chapter in the pair and read it at reading size, which is the only place a pairing can be judged.

Every Nueel design ships with its pair already chosen, matched to the genre it serves and licensed for embedding, so the choice in front of you is between finished designs rather than font files.

Common questions

How many typefaces should a book use?

Two: a text face for the body and a display face for titles and headings. A third for captions, notes or tables is legitimate in nonfiction. Beyond that, the reader starts to register variety without being able to explain it, and a book that looks assembled rather than designed is the usual result.

Do chapter titles need a different typeface from the body?

No. Weight, size, small capitals and letterspacing from the text face itself carry a surprising range of chapter openings, and every classic pair works this way or with one display addition. What a chapter title needs is contrast with the text, and contrast has more tools than a second typeface.

Can I use free Google fonts in a printed book and an ebook?

Yes. Nearly all fonts on Google Fonts carry the SIL Open Font Licence, which permits embedding in documents — including PDFs and EPUBs — and use in print, including commercially. The licence requires you not to sell the fonts themselves. Choose faces designed for the job: a text face for body text, not a display face shrunk down.

What does embedding a font mean legally?

That the font's outline data travels inside your file, so the reader's device does not need it installed. Commercial font licences differ on whether that is allowed and on what terms, and print-on-demand platforms require it for PDFs — so check the licence before building the book on a font, not after the export is rejected.