Skip to content
UX Atlas
Plate FND·031 · UI foundationGrid C2 · Rev. 2026-08-14

Type Scale

A fixed set of sizes derived from one ratio, so type decisions become selections rather than inventions.

UI foundationCraft conventionFoundational

Definition

A type scale is an ordered set of font sizes generated from a base size and a ratio. Restricting the interface to these sizes produces consistent relationships and removes a recurring decision.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this plate
  1. 1Definition
  2. 2A working interface scale
  3. 3Practical constraints
  4. 4Keeping a scale usable
  5. 5In practice
  6. 6Local chart
  7. 7Sources
  8. 8Continue from here

Reach for this when

  • Setting up typography tokens.
  • Reviewing a product with inconsistent text sizes.
  • Building responsive typography.

Common mistakes

  • Too many steps.
  • Pixel-based sizing that ignores user preferences.
  • Line height chosen separately from size.
  • Treating the generated scale as fixed, when the useful scale is the subset the product actually needs.
Atlas39 / displayAtlas31 / page titleAtlas25 / sectionAtlas20 / leadAtlas16 / bodyAtlas14 / secondaryAtlas12 / meta
A 1.25 ratio scale from a 16px base. Steps are distinguishable without being dramatic, which suits dense interfaces.

A working interface scale

Base 16px, ratio 1.25, rounded to whole pixels. Roles are indicative, not prescriptive.

TokenSizeLine heightTypical role
text-xs12px16pxMetadata, table captions, legal text.
text-sm14px20pxSecondary text, dense table cells, form hints.
text-base16px24pxBody text. Never smaller for sustained reading.
text-lg20px28pxLead paragraphs, card titles.
text-xl25px32pxSection headings.
text-2xl31px38pxPage headings.
text-3xl39px46pxDisplay, used sparingly.

Practical constraints

  • 16px is the practical floor for body text. Smaller sizes trigger zoom on iOS form inputs and fail readability for many users.
  • Round to whole pixels for interface sizes. Fractional sizes render inconsistently across platforms.
  • Six to eight steps is usually enough. More steps means indistinguishable neighbours and arbitrary choices.
  • Pair each size with a line height in the scale, so the two are never chosen independently.
  • Define the scale in rem so it respects the user's browser font size setting.

Keeping a scale usable

Do

  • Keep the number of steps small enough that each has an obvious job.
  • Use a tighter ratio for interface text than for marketing pages.
  • Set the body size first and build the scale around it.
  • Round to values that render cleanly, and keep the rounded number.

Do not

  • Add a step because one screen needed something between two existing ones.
  • Use the same scale for a dense table and a landing page hero.
  • Let the ratio decide when the resulting size is obviously wrong.

In practice

  1. i.

    Different scales for marketing and product

    Design systems

    Marketing surfaces often use a larger ratio for drama while the product uses a tighter one for density. Both derive from the same base, which keeps them recognisably related.

  2. ii.

    Eleven steps, four in use

    Scale inflation

    A documented scale of eleven sizes had four in real use and seven appearing once each. The unused steps were not a resource, they were an invitation to inconsistency.

Local chart

FND·031 · Region II · Grid C2

This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  1. [1]

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Short definition

The one-paragraph version, for when that is all you need.

Related concept

Connected closely enough to change how you apply this.