esc
  • WorkflowsPages
  • Case studiesPages
  • Machine Learning FoundationsLearn
  • AI EngineeringLearn
  • AI Guardrails & Red TeamingLearn
  • UI/UXLearn
  • Design SystemsLearn
  • Production System DesignLearn
  • Book a callContact
  • Download ResumeContact
Let’s talk

I’ll build the agent for it.

Typography: Shared Text Rules for a Design System

Learn how a design system picks a few typefaces, builds one type scale, and uses it so every screen's text is consistent and easy to read.

In short

Typography in a design system means picking a few typefaces and one type scale, then using them so the text on every screen is consistent and easy to read.

14 min readFree

What you will learn

Almost every screen in a product is full of text. People read names, labels, prices, and instructions. When each designer picks their own font and size, the text starts to look messy and is hard to scan. Typography in a design system is the set of agreed rules for typefaces, sizes, weights, line heights, and spacing. These rules make text look consistent on every screen. In this lesson you will learn how to pick a small set of typefaces, build a type scale, and use type to show what matters most.

Key words

Typography
The rules for how text looks and how it is arranged on a page or screen.
Typeface
A family of letter designs that share one look, such as Roboto.
Weight
How thick or thin the letters look, such as regular or medium.
Type scale
A set of named text styles that the whole product reuses.
Role
The job a piece of text does, such as heading, body text, or caption.
Line height
The vertical space from one line of text to the next line.
Letter spacing
The space between letters. Designers also call it tracking.
Hierarchy
The order of importance that a reader sees on the page.

How do you choose a small set of typefaces?

A design system starts by deciding which typefaces the product will use. The goal is readable text that does not fight for attention. Material Design's guidance suggests choosing a readable typeface and using several styles from one family, so content looks consistent without distraction.

The system should limit the set on purpose. Every extra typeface adds more shapes, weights, and sizes that designers and developers must manage. Google's Android guidance names Roboto as the standard typeface on Android. A team does not need to copy that choice, but it shows what one clear default looks like.

  • One main typeface

    Use one typeface for most text. It keeps the product calm and makes the scale easy to follow.

  • A second face only with a reason

    Add a second typeface only when it has a clear job, such as bold display headlines. Do not add one just because it looks nice on one screen.

  • A short approved list

    Write down the approved typefaces and their uses. Anyone who wants a new one should ask the design system owners first.

Choosing fonts is only part of the job. The system also needs to say what each typeface is for and which sizes it uses. Design Systems Surf puts it simply: For typography to work across a product, visual decisions need to be formalized. That's why every system, big or small, should define a few key parameters: which fonts are used and what font sizes map to which roles.

Pairing means using two typefaces together. One common pattern is a display face for headlines and a text face for paragraphs. Pairing can work well, but it adds work. Fortnightly's custom type scale shows the idea, because it uses a combination of two fonts across its type scale.

Fallback fonts are the backup plan for text. A fallback font is a second typeface the screen uses when the first one cannot load, for example on an older device or a slow connection. Your system should name the fallback in advance, so the text still looks close to the design when the main font is missing.

How do you build a type scale?

A type scale is the heart of typography in a design system. It is a short list of text steps, and each step has its own size, line height, and weight. A type scale is the set of text sizes an interface uses, each a step with its own size, line height and weight. Designers pick from the list. They do not invent new sizes on each screen.

Keep the list short. One guide notes that limiting the number of font sizes avoids overwhelming complexity, and typically 6 to 9 steps works well. Another common mistake is adding sizes between the steps. When a designer needs an in-between size, the better move is usually to pick the nearest step.

  1. 1

    Pick a base size

    Start with the size for body text, the text people read most. For web design, 16px is standard and accessible. This is the starting point for the rest of the scale.

  2. 2

    Pick a ratio

    A ratio is the fixed multiplier between one step and the next. Tenet UI, for example, built a modular typography scale using a predictable ratio, a major second at 1.125x.

  3. 3

    Generate the other steps

    Multiply the base by the ratio to get larger steps, and divide to get smaller ones.

  4. 4

    Round and trim

    Round each step to a clean number, and keep only the steps the product truly needs. Many teams find that a few steps cover most screens.

  5. 5

    Map each step to a role

    Give every step a job name, such as Body or Caption. Then write the name next to the size, so the choice is clear when someone builds a screen.

The roles matter more than the numbers. Figma's guide suggests that a designer can first choose a font by its function, or role, then its size. That order keeps the system tied to purpose. A designer asks, "What is this text for?" before asking, "What size should it be?"

How do you name the text roles?

Roles give the scale its meaning. Many systems use a small set of roles. One guide advises that teams choose five to seven text roles, such as Title, Subtitle, Body, Label, Caption. Tenet UI chose semantic roles, Display, Heading, Label, and Body, for the scale. Semantic means the name describes the job, not the look. It also used semantic names instead of traditional H1, H2, and H3 labels for better clarity.

  • Display

    The largest text. Use it for a hero message or a big number on a dashboard. Use it rarely, because too much display text shouts.

  • Heading

    Titles of a page or a section. Headings tell the reader where they are and what comes next.

  • Body

    The main reading text, such as a paragraph or a description. It should be the most comfortable size on the screen.

  • Label

    Short text on buttons, tabs, form fields, and tags. It needs to be clear at a glance.

  • Caption

    Small supporting text, such as a date, a note, or a hint. It must still be readable, so do not make it too small.

Tip

Write the role name in the design file as well as the size. When a teammate sees 'Body' they know the job of the text, even if the size changes on another screen.

Weight, line height, and letter spacing

Size is only one part of a text style. A complete style also sets weight, line height, and letter spacing. A system that sets only sizes will still look uneven, because readers feel the rest of the style too. Tenet UI's approach also links type to a grid, so text lines sit in a steady rhythm.

  • Weight

    Weight sets the thickness of the letters. Material's baseline table, the standard set of default styles, keeps most styles at a regular weight, and it moves some title styles to a medium weight. Title Medium uses Roboto at weight 500 with a size of 16 and a line height of 24. Emphasized styles in Material are a higher weight and other minor adjustments compared to the baseline styles.

  • Line height

    Line height is the space between lines. Bigger text usually needs more room around each line, but the exact amount is a judgment call. In the Material table, Display Large has a size of 57 and a line height of 64.

  • Letter spacing

    Letter spacing, or tracking, adds or removes space between letters. A guide on semantic typography notes that designers should adjust spacing for improved legibility based on the type scale and the case of the text. Large display text often looks better a little tighter. Small text often needs a little more room.

Tip

Write all five parts for each style: font, size, weight, line height, and letter spacing. If one part is missing, each designer will fill it in a different way.

Worked example: Material Design 3 and an inbox row

Material Design 3 is Google's design system, and its type scale is a clear model to study. It has one scale with two sets of styles. It has 15 baseline and 15 emphasized type styles, and both sets follow the same scale from Display Large to Label Small. The five roles are Display, Headline, Title, Body, and Label. Each role has three sizes, Large, Medium, and Small.

Google's developer notes add a useful warning. A product will likely not need all 15 default styles from the Material type scale. A new team can start with a smaller set and add styles only when a screen truly needs them.

The example below is an illustration, not a copy of Gmail's private style names, which are not listed in the sources for this lesson. It shows how the Material roles would fit a familiar inbox row.

  1. 1

    Look at what the row contains

    A Gmail inbox row blends three things: sender name, subject line, and snippet text. The snippet is the short preview of the message body. The sender usually comes first in the row, and it is often the first thing your eye sees.

  2. 2

    Give each line its own role

    The sender name is the most important line for scanning, so it fits a Title role. The subject line explains the message, so it fits a Body role with a little more weight. The snippet is the supporting preview, so it fits a smaller Body or Label role. Material's own table lists Title Medium at 16 with weight 500, which is a sensible start for a sender name.

  3. 3

    Use the sizes as a map

    One glossary maps the same base size to several names. In that glossary, base 16 is Material's titleMedium and bodyLarge, while sm 14 is titleSmall, bodyMedium, and labelLarge. A team can pick the names that match each line and keep the sizes fixed.

  4. 4

    Add the unread state with care

    In many inboxes, an unread message's subject appears in bold. That is a weight change, not a new size. It shows how one style can change state without adding a new style.

  5. 5

    Check the scan

    Read the row quickly. The sender, subject, and snippet should be easy to tell apart. If all three look the same, the row becomes a wall of text. Good roles make the row easy to scan in one glance.

Tip

When you study a real product, list the text roles on one screen. Ask what each line is for. If two lines share a style, check whether that choice is on purpose.

How do you use type for hierarchy and readability?

Type shows hierarchy. The reader should see the most important text first, then the next, and so on. Typography Hierarchy, a technical guide, makes the point that typography hierarchy is a structured system of text styles that organizes written content according to importance, readability, and context. Roles should follow how important the content is, not how the designer likes it.

  • Accessible sizes

    Some users set their device to larger text. Material uses scalable units so that type sizes enable large type modes for accessibility. Your system should let text grow rather than forcing it to stay small.

  • Dynamic text, not clipped text

    When text can grow, cutting it off hides information. Material advises that for the best user experience, use dynamic type instead of relying only on smaller type sizes or allowing truncation of larger-size text.

  • Readable line length

    A line of body text that runs across a very wide screen is tiring to read. Keep body text in a column that is comfortable to follow, and let the layout add margins instead of stretching the words.

  • Contrast

    Text must stand out from its background. The Color lesson covers the values and contrast rules. For type, check that each role stays readable on every surface where it appears.

  • Few sizes

    Too many sizes make a screen noisy. Material notes that too many type sizes and styles at once can wreck any layout. A short scale keeps the hierarchy clear.

Responsive behavior means text adapts when the screen changes size. Breakpoints are the screen widths where the layout changes, such as phone to tablet. Establish a scale per breakpoint, and make it usable at varying hierarchy levels, by element, component, region, and page. Designers often see the biggest changes in large display sizes. Quite often the biggest variances in scale between devices will happen at the larger display sizes.

Material's approach keeps the roles the same across devices. Material 3 tokens, which are named settings that store a design value such as a size, allow scaling across devices while preserving relative hierarchy. In plain words, the sizes can change on a large screen, but the heading still looks more important than the body text.

Tip

Keep the role names the same on every screen size. Change only the sizes. Engineers and designers can then trust that a Heading is a Heading on a phone and on a desktop.

Common mistakes to avoid

  • Too many sizes

    A team adds a size for each new screen. Over time the product has many near-identical steps that no one can tell apart.

  • Styles chosen by taste

    A designer picks a size because it looks nice in one mock-up. The system should decide by role, not by mood.

  • Sizes without line height

    A text style with a size but no line height can look cramped in one place and loose in another.

  • Fixed pixels only

    On the web, fixed pixel sizes do not follow the user's browser setting. One guide notes that rem is used for most typography, as it scales with the root element, the top-level element of the page, and respects user browser settings.

Check your understanding

Quick check

A team's app has 14 different font sizes and three similar-looking grays for body text. Users say the screens feel messy and are hard to scan. Which typography decision would you apply first, and what would it look like?

Quick check

A recipe app uses one headline size on phones and tablets. On a tablet the headline wraps onto two lines and pushes the ingredients off the first screen. The team wants a fix that stays inside the system and adds no new one-off sizes. What should they add?

Key takeaways

Typography in a design system is a shared set of rules. It limits the typefaces to a small, deliberate set. It builds one type scale with a short list of steps. It maps each step to a role such as Display, Heading, Body, Label, or Caption. It sets weight, line height, and letter spacing for each style. It uses those roles to show hierarchy, keeps text readable at larger sizes, and adapts the sizes across breakpoints while the roles stay the same.

Tip

Next time you open a product, list the text roles you can see. If you can name them, the system is working. If you cannot, the scale may need clearer rules.

Sources

How is this lesson?

Last updated on 17 November 2026

Learn with me

Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.