# Readability: Set Text Rules Once So Every Screen Is Easy to Read

> How font size, line height, line length, weight and hierarchy make text comfortable to read, and how to write those choices into your type rules.

**In short:** Readability depends on font size, line height, line length, weight and hierarchy, and a design system writes those choices into its type rules once for every screen.

From "Design systems", a free course by Venkat R. Murty: https://designervenkat.online/learn/design-systems/readability

## What you will learn

Readability is how easily people can read and understand the text on a screen. Some of it comes from the words, but a lot comes from type choices: how big the letters are, how far apart the lines sit, how wide each line runs, how thick the strokes look, and how well the text stands out from its background. In a design system, you set these text rules once, write them down, and reuse them, so every screen stays comfortable to read instead of depending on one designer's eye.

By the end of this lesson you will know the type settings that drive readability, sensible starting values for body text, headings and captions, how a clear type scale and good structure help people scan a page, and how to test these rules and write them into your guidelines.

- **Readability:** How easily people can read and understand text on a screen.
- **Character:** One letter, number, space or mark in a line of text.
- **Font size:** How big the letters are. On screens it is often measured in pixels (px), the tiny dots that make up the display.
- **Line height:** The vertical space from one line of text to the next. Designers also call it leading.
- **Line length:** How many characters fit on one line. Designers also call it the measure.
- **Font weight:** How thick or thin the letter strokes look, such as regular or bold.
- **Letter spacing:** The gap between letters. Designers also call it tracking.
- **Type scale:** A short, agreed list of text sizes, where each size has a job.
- **Hierarchy:** The visual order that shows a reader which text matters most.
- **Scannable:** Easy for a reader's eye to skim quickly and find what they need.
- **Caption:** Small text that explains an image or adds a short note.
- **Type guideline:** The written rule that says which text style to use and what its settings are.

## What four settings drive readability?

Four settings do most of the work: font size, line height, line length, and weight with letter spacing. Each one can make text easy or hard to read on its own, and they also affect each other. A large font in a very long line can still be tiring, and a comfortable line length can still feel cramped if the line height is too tight. Learn the four settings together, not one at a time.

### How does font size affect readability?

Font size is the setting most people notice first. Body text is the main reading text, the paragraphs a reader works through. Its size sets the base for the whole type system. Some guides suggest <cite index="4-4">Material Design specifies 16px body; Apple's HIG recommends 17px</cite>, so roughly 16 to 17 pixels is a common starting point for web body text.

Some sources allow smaller text, so the floor is debated. One guide suggests <cite index="11-9">avoiding going below 12px for body content</cite>, while another says <cite index="11-10">Never let body text drop below 16px on web interfaces.</cite> Pick a minimum, write it down, and use it everywhere. Size should also hold steady on small screens. <cite index="19-8">Scaling everything down by the same percentage often makes body text too small.</cite> Keep the body size stable and let the headings shrink more.

### How does line height affect readability?

Line height, or leading, is the vertical gap from one line of text to the next. When the gap is too small, <cite index="9-3">Too tight line height causes text to feel cramped</cite>. When it is too large, <cite index="9-3">Too loose line height breaks cohesion and slows reading</cite>. The eye needs enough air to find the start of the next line without effort.

For body text, a common range is <cite index="8-3">about 1.4 to 1.6</cite> times the font size. Headings can sit tighter, around <cite index="8-3">1.1 to 1.3</cite>. Write line height as a plain number, such as 1.5, rather than a fixed pixel amount. A number <cite index="8-11">scales with the font size of each element, while a fixed pixel value has to be recalculated every time the size changes.</cite>

### How does line length affect readability?

Line length, or the measure, is how many characters fit on one line. Lines that are too short create many breaks, and <cite index="2-6">Shorter than 50 characters = Too many line breaks, disrupting reading flow.</cite> Lines that are too long make reading harder, and <cite index="9-5">overly long lines reduce readability</cite>. A reader's eye must travel far to the right, then find its way back to the left for the next line.

Guides do not agree on one exact range, so your team should pick one and document it. One source gives <cite index="5-1">45-75 characters per line</cite> as optimal. Another gives <cite index="1-18">40 to 60 characters per line (including spaces)</cite> for English body text. Accessibility guidance for a well-known web standard suggests <cite index="4-8">line length no more than 80 characters</cite>. The ranges mostly overlap, which is why 45 to 75 is a good working band.

Narrow screens need shorter lines. One guide lists <cite index="5-7">Desktop: 50-75 characters · Tablet: 40-60 characters · Mobile: 30-50 characters</cite>. Your rules can give one range per device type.

> **Tip:** Set the width of the text column in characters, not in a fixed number of pixels. That way the measure stays about the same when the font size changes.

### Font weight and letter spacing

Font weight changes how strong the strokes look. A common pattern is to use bold for the main heading and regular weight for body text. One guide shows exactly that pattern, with <cite index="10-4">bold for your main heading (like 'About Us') and regular weight for body text.</cite> One guide advises limiting a page to a maximum of three font weights, for performance reasons.

Letter spacing is the gap between letters. For body text, <cite index="10-9">you don't need much letter spacing—keep it normal.</cite> Headlines and small text can be adjusted a little. <cite index="13-8">While capitalizing body text is generally not a good idea from a readability perspective</cite>, uppercase can help separate short headings or labels. Good rules also leave room for readers who stretch the spacing. Accessibility guidance asks that <cite index="4-14">your page doesn't break when a user overrides line height to 1.5×, paragraph spacing to 2×, letter spacing to 0.12×</cite>, which is a useful test for any text rule.

## Sensible defaults for each text role

Not every piece of text needs the same settings. Set one default for each role, then let the rare exception be documented on its own. Here are three starting points you can adapt.

- **Body text:** This is the text people read most, so it gets the most stable settings. Start near 16px, with line height around 1.5, regular weight, normal letter spacing, and a line length of about 45 to 75 characters. The reason is simple: long passages need calm, even spacing.
- **Headings:** Make headings clearly bigger than body text and a little heavier. Use tighter line height, around 1.1 to 1.3, because <cite index="8-4">large headings with 1.5 line height look disconnected</cite>. Headings are short, so they do not need the open spacing that paragraphs do.
- **Captions and hints:** Keep these small, often 13 to 14px, and never let them become the main reading size. <cite index="5-8">Small text: 1.5-1.7</cite> is a common line height range, which keeps tiny words from crowding together.

## How do hierarchy and scanning work?

Good type helps people scan. A scannable page lets a reader skim the headings and labels, then stop at the part they need. Users need to <cite index="5-4">quickly scan and understand information without strain</cite>, and the type rules are what make that possible. Hierarchy is the tool that makes scanning work. A reader should be able to tell, at a glance, what is a title, what is a sub-point, and what is the body.

### How do you build a clear type scale?

A type scale is the short, agreed list of sizes your product uses. You start with a base size for body text, then choose how the other sizes step up or down. <cite index="12-1">To establish a type scale for your project, start by defining a base font size and a modular ratio that fits your audience and platform.</cite> Keep the list short. Many teams use only a handful of steps, so each one stays easy to tell apart.

The steps must differ enough to be noticed. <cite index="13-5">A difference of only one or two points in type size won't create enough contrast to make the hierarchy apparent to most users.</cite> Designers also say that <cite index="13-10">every design should include three levels of hierarchy: heading, subheading, and body text.</cite> Use size, weight and spacing together so each level is clear.

### Alignment and paragraph structure

Alignment is the edge that text lines up against. Left-aligned text is the safe default for reading. Fully justified text, where both edges are forced straight, can leave uneven gaps between words, and accessibility guidance says <cite index="4-8">text not fully justified (no text-align: justify)</cite>. Paragraph spacing also helps scanning. One guide advises that <cite index="8-3">paragraph spacing roughly equal to one line of text</cite> works well, while another suggests <cite index="4-8">paragraph spacing at least 1.5× the line height</cite>. Either way, the gap between paragraphs must be visible.

> **Tip:** Keep paragraphs short, and start a new heading whenever the topic changes. A reader who skims can then land on the right part of the page in a few seconds.

**Quick check:** A settings page uses headings only one point larger than the body text, all in bold, and paragraphs sit with no gap between them. Users say they cannot find the section they want. What is the best first fix?

A. Make the body text bold too, so the whole page looks equally important
B. Increase the difference between heading sizes, keep body text regular, and add space between paragraphs
C. Justify every paragraph so the left and right edges line up neatly
D. Shrink the headings to match the body text, so nothing looks out of place

**Answer:** B. Scanning depends on clear differences. Bigger steps between headings, regular body text and visible paragraph gaps let the eye find each section. Bold everywhere removes the contrast, and matching sizes removes the hierarchy.

## Worked example: a news article page

Imagine a news story page, the kind you might see on a large news site or a publishing platform. The numbers below are a teaching example that shows how the rules work. They are not measurements taken from any real site. Follow the steps to see how a page moves from hard to read to comfortable.

1. **Measure the starting point:** The body text is 12px with a line height of about 1.1. The text runs across a full-width desktop column about 1400px wide. Each line holds far more than 75 characters, so the eye struggles to find the start of the next line.
2. **Raise the body size:** Change the body text to 16 to 18px. One guide recommends <cite index="7-2">16-18px body text, 1.5x line height, and 45-75 character line lengths</cite>, so that range is a sound place to begin.
3. **Open up the line height:** Set the line height to 1.5 times the font size. That sits inside the <cite index="8-3">1.4 to 1.6</cite> range that many guides give for body text.
4. **Narrow the column:** Limit the text column so each line holds about 65 characters, inside the <cite index="5-1">45-75 characters per line</cite> band. The empty space beside the column is useful. It frames the text and gives the eye a clear place to rest.
5. **Set paragraph and heading rules:** Add a visible gap between paragraphs and keep headings larger with tighter line height. Use the same body style in every article template, so readers learn one rhythm.
6. **Check the phone version:** On a narrow screen, keep the body text at 16px and let the column reflow. <cite index="19-7">Body text should never go below 16px / 1rem</cite>, so the text should not shrink to fit.

What changes for the reader? The text is larger and easier to pick out. Each line is short enough to follow, and the extra space between lines lets the eye land on the next line without effort. The page does not ask the reader to fight it. A quick before-and-after test with a few readers, reading the same story for a minute each, will show the difference clearly.

## How do you test readability?

A rule that looks good in a design file can still fail on a real page. Testing shows whether your settings hold up with real words, real images and real screens. A type rule is only a good rule once it has survived this kind of check.

### Test with real content on real devices

Start with real content. Short placeholder text hides problems that long articles reveal, such as long links, headlines that wrap onto three lines, or captions that run into the body. <cite index="16-12">Preview your scale at approximately 320, 375, 768, and 1280 CSS pixels, then drag slowly between those widths.</cite> These widths cover a small phone, a large phone, a tablet and a desktop.

Then test the settings people actually use. <cite index="16-13">Also test browser zoom and larger default text settings.</cite> Check that <cite index="16-14">content remains readable and usable without unexpected horizontal scrolling.</cite> If a reader must sideways scroll to finish a sentence, the rule has failed.

> **Tip:** Ask three or four people to read a full article on their own phone. Ask them to tell you where they lost their place. Their answers will show problems a design file hides.

### How do you write readability into the type guidelines?

A test result helps once it becomes a rule. Document each text style with its values and the reason behind them, so new designers and product teams can use the rules without asking you. <cite index="10-13">Include specific examples like, 'Heading 1: 36px, bold, Line Height: 1.4' and 'Body Text: 16px, regular, Line Height: 1.5'.</cite> Use this four-step process.

1. **List the text roles:** Name each job a text style does, such as body, caption, heading one and heading two. <cite index="12-8">Use a consistent scale for sizing and organizing headings, body text, and labels.</cite>
2. **Write the minimum sizes:** Set the smallest allowed size for body text, such as 16px on the web, and say that body text should not shrink on phones. Give the minimum for every role, not only for body text.
3. **Write the line length limits:** Give a character range for each device type, such as 45 to 75 characters on desktop, and explain how the column width is set. Tell the team which range applies to which screen.
4. **Record the exceptions:** Say when a text style may break the rule, such as a large pull quote, and set a limit. <cite index="18-7">Escape hatches, with clear limits, so a legitimate exception doesn't become a new pattern.</cite>

> **Tip:** Write the reason beside each value. A designer who knows why line height 1.5 helps body text is less likely to override it on a whim.

## Put it together

Readability is a set of connected choices, not one magic number. Size, line height, line length, weight and hierarchy each support the others. When you change one, check the rest. Try the idea on a real problem before you read the answer.

**Quick check:** A team's help center shows body text at 13px with line height 1.1, stretched across a 1400px wide desktop column. Users say they lose their place while reading. Which change to the type rules fixes this best?

A. Keep the 13px size, because smaller text fits more on the screen
B. Make the column wider so fewer lines wrap, and keep the line height at 1.1
C. Raise body text to about 16px, set line height near 1.5, and limit the column to roughly 45 to 75 characters
D. Make every line bold so the text stands out and is easier to follow

**Answer:** C. Small text, tight lines and a very long measure all work against the reader. Raising the size, opening the line height and narrowing the column together fix the lost-place problem. Wider columns and bold text make the first problem worse or add no help.

Keep these three mistakes in mind when you review a screen. First, tight line height in a wide column. Second, too many near-identical text sizes. Third, rules written down but never tested on a phone. Each one can be caught with the steps you have just read.

## Sources

- [Shopify Partners blog: Typography in UI Design](https://www.shopify.com/partners/blog/typography)
- [Medium: The Perfect Text Readability Recipe (Design Bootcamp)](https://medium.com/design-bootcamp/the-perfect-text-readability-recipe-science-backed-typography-for-better-ux-7c8bf190df85)
- [Accessible Typography: Font Size, Line Height and Readability (2026)](https://accessibilitychecking.org/accessible-typography-guide/)
- [FontHubs: UI Typography Guide](https://www.fonthubs.com/en/knowledge/ui-typography)
- [Adoc Studio: Typography Best Practices 2026 Guide](https://www.adoc-studio.app/blog/typography-guide)
- [DeveloperUX: Typography in UX Best Practices Guide](https://developerux.com/2025/02/12/typography-in-ux-best-practices-guide/)
- [Innovialabs: Typography Basics for Web and Interface Design](https://innovialabs.uz/en/blog/typography-basics-for-web-design)
- [Subux: Text line length and height](https://subux.pro/guides/article/text-line-length-and-height)
- [Subux: Responsive design typography](https://subux.pro/guides/article/responsive-design-typography)
- [Figr: Typography System Design, Building Type Scales](https://figr.design/blog/typography-system-design)
- [Medium: What is Type Scale, Complete Guide to Typography Systems](https://medium.com/@allanmuchemi89/what-is-type-scale-complete-guide-to-typography-systems-d03a99000687)
- [Cieden: How do I establish a type scale for my project?](https://cieden.com/book/sub-atomic/typography/establishing-a-type-scale)
- [Toptal: How to Structure an Effective Typographic Hierarchy](https://www.toptal.com/designers/typography/typographic-hierarchy)
- [UCLA Design System: Typography](https://designsystem.brand.ucla.edu/build/v2.1.0/docs/style-guide/typography.html)
- [Webaloha: Website Typography Guide](https://webaloha.co/website-typography-guide/)
- [Get Design Work: Responsive Type Scale guide](https://www.getdesignwork.com/responsive-type-scale/)
- [Getdom Studio: Typography System Guide for Modern UI Builders](https://getdom.studio/blog/typography-system)
