Web Typography: Fonts, Pairing & Readability
Typography is the largest part of most interfaces — nearly everything a product says, it says in type — and the craft splits into two halves: choosing and combining typefaces well, and setting them so they read effortlessly. The sizing mathematics lives in our type scale guide; this hub is the other half — the craft. The fastest way in is to see a classic pairing in real text.
Choosing is casting
A typeface choice is a casting decision: the face will speak every line the product ever says, in a register readers pick up before they read a word. The guides here cover the choices — pairing faces that contrast without clashing, the serif question as it actually stands on modern screens, display faces that don’t sacrifice readability, and what letterforms signal about a brand. The casting metaphor is doing real work: readers register a typeface’s tone before they read a word of the content, the way a voice registers before the sentence does, and no rewrite undoes that first impression.
Reading is a mechanic
The other half is mechanical and measurable: line length that keeps the eye’s return trip reliable, the difference between legibility — can I decode it? — and readability — does it flow?, type in forms where errors cost most, and the small optical adjustments text needs at small sizes. None of it is taste — most of it has been studied for a century, and the guides report what holds up. The reason the numbers hold is physiological rather than aesthetic: reading happens in jumps and return sweeps, and nearly every measurement in these guides exists to keep those jumps landing where the eye expects.
The practical layer
Between craft and theory sits the working layer every project meets: which Google Fonts genuinely hold up, when a system font stack beats loading anything, how fonts arrive on the page without blocking it, and what variable fonts change. Concrete, current, and covered here — and The Web Typography Checklist compresses the whole hub into a single pre-ship pass.
Where the sizing half lives
This hub deliberately stops where measurement begins. The mathematics of size — scale ratios, heading hierarchies, how many sizes a system needs — belongs to the type scale guide, and how those sizes behave between a phone and a desktop is covered in fluid typography. The split matters in practice: typography that reads badly usually fails on one side only, and knowing whether you are debugging a casting problem or a sizing problem saves rework. Scale Composer holds both halves in one place — a curated set of families for the craft decisions, driven by the same scale that sizes type, spacing and grid — so a pairing chosen here arrives already sized by the system.
Guides in this hub
- Choosing a Display Font Without Wrecking Readability
Display fonts are drawn for large sizes — high contrast, tight spacing, personality. Where they belong on the type scale, and why they fail as body text.
- Font Loading Performance Basics
Font loading performance rests on three levers: fewer font files, smaller files (WOFF2), and font-display: swap — and why a lean type system wins most.
- Font Pairing Rules That Actually Work
Font pairing that works rests on one principle: contrast in class, harmony in proportion. Why near-identical fonts fail, and which classic pairs hold up.
- Letterforms and Brand Voice: What a Typeface Signals
Typeface personality is a register, not a message: what geometric, humanist, grotesque and serif faces signal — and the letterform mechanics behind it.
- Line Length: The 45–75 Character Rule
The optimal line length for body text is 45–75 characters per line, with 66 the classic sweet spot. Why long lines defeat the eye, and the one-line CSS fix.
- Optical Sizes: Why Small Text Needs Different Shapes
Optical size typography: why one outline can't serve 12px and 72px, what the opsz axis adjusts, and how to compensate when a font doesn't carry it.
- Readability vs Legibility: The Difference
Readability vs legibility: legibility asks if characters can be decoded, readability asks if sustained reading flows. The difference routes the fix.
- Serif vs Sans for Body Text on Screens
Serif vs sans serif for body text: why the old screen rule expired, what research really shows, and why size and line height matter more than the choice.
- System Font Stacks: When Not to Load a Font
A system font stack renders each platform's native face: zero font requests, zero font-driven layout shift. What you gain, give up, and when to use one.
- The Best Google Fonts for UI in 2026
The best Google Fonts for UI pass five criteria — small-size legibility, a real weight range, screen x-height, coverage, upkeep — about twelve families.
- The Web Typography Checklist
A web typography checklist of 20 one-line checks — scale, reading comfort, typefaces, details, delivery — each with the concrete number to verify.
- Typography for Forms and Inputs
Form typography rules with reasons: 16px inputs, labels above fields, helper-text floors, monospace for codes — set for verifying, where errors cost money.
- What Are Variable Fonts?
Variable fonts pack a continuous weight range into one file. How the axes work, when one file beats four static cuts, and why font-weight: 457 works.
Judge pairings with your own eyes
Pairing advice only becomes conviction in front of real text: swap the heading and body faces in a live specimen — the Scale Composer’s curated font picker holds ~50 families that survive UI use, and watching a pairing click (or clash) in running text teaches faster than any rule list.