For printed body text, start at 12 points. For body text on a screen, start at 16 pixels and try 19. Headings go larger than that, and text read from farther away goes larger again.
Treat these numbers as starting points. Fonts differ, and so does the distance between the reader's eyes and the page. Below you get the conversions, the size of headings against body text, and a quick way to test your choice.
Points and pixels in one minute
Printed documents and word processors use points. Web pages use pixels. The two units are linked. The MDN page on CSS lengths says one inch equals 96 pixels and one point equals 1/72 of an inch. So one point is about 1.33 pixels.
That makes 12 points equal to 16 pixels. The table shows a few more conversions.
| Points | Pixels (rounded) |
|---|---|
| 10 | 13.3 |
| 11 | 14.7 |
| 12 | 16 |
| 14 | 18.7 |
| 18 | 24 |
Use points when you work in a word processor. Use pixels or relative units when you build a web page. If a tool shows only one unit, use the table to switch.
Starting sizes for paper and screen
Government guidance on accessible documents asks for a minimum size of 12 points. Treat that as the starting minimum. A handout read at a desk can stay at 12. A handout read standing up, or passed around a room, is easier at 14.
On screen, browsers usually start body text at 16 pixels. MDN calls that a common default and adds that readers can change it. One government design system sets body text at 19 pixels on both small and large screens. It pairs that with a 25-pixel line height and keeps small supporting text at 16 pixels.
Pick one size for all body text and keep it. Switching sizes between paragraphs looks like a mistake.
Documents printed in extra-large type follow different rules. See how to print a document in large type.
How reading distance changes the answer
The farther away the reader, the larger the letters need to be. A phone sits close. A laptop sits at arm's length. A notice on a wall is read from a few steps back. The same size feels different at each distance.
Fonts add a twist. Two fonts at 12 points can look different in size, because their letter heights vary. Compare them on the page.
So test at the real distance. Run this checklist before you share anything.
- I opened or printed the page the way the reader will see it.
- I read it from the distance the reader will use.
- I did not have to lean in to read the body text.
- Dates, times and places are the same size as the rest, or larger.
- When unsure, I went one size up.
Here is a worked example. A teacher prints a one-page trip note for families. She sets the body at 12 points, the headline at 18 points and the date line at 14 points. Then she holds the page at arm's length. The date line is easy to find, and the body is readable. She tries 11 points for the body and sees the difference at once, so she keeps 12.
Text on a wall needs the most room to grow. The article on posting notices on a wall covers that case.
Sizing headings against body text
Headings need to stand out from body text. Size is one signal. Weight and the space around the heading are others.
The same government design system gives a useful scale. Here are its numbers.
| Style | Large screens | Small screens |
|---|---|---|
| Largest heading | 48 px | 32 px |
| Section heading | 36 px | 27 px |
| Subheading | 24 px | 21 px |
| Body text | 19 px | 19 px |
| Small body text | 16 px | 16 px |
On large screens, headings run from about 1.3 to 2.5 times the body size (24, 36 and 48 against 19). Body text stays at 19 pixels on a phone. Only the headings shrink.
A heading one point larger than body text barely shows. Make the jump clear. Then apply real heading styles instead of only enlarging the text. The article on using headings explains how.
Letting readers change the size
WCAG 2.2 asks that text can be resized, without assistive technology, up to 200 percent without loss of content or functionality. In plain terms, a reader who enlarges your page should still see everything. Nothing should be cut off or overlap.
On a web page, relative units help. The design system's type scale page says its code uses em or rem units so that type resizes better when zoomed or magnified. MDN describes rem as relative to the root element's font size. A common browser default is 16 pixels, and readers can change it.
Your part is simple. Do not lock sizes in a way that blocks scaling. Check the page at 200 percent. For the reader's side of this, see how to zoom a web page.
The Easy-Read Editor lets you change the text size and view the result next to your original text. Use it to compare two sizes on your own wording.
Common mistakes
- Picking a size from your own screen. You sit close, and your readers may not.
- Shrinking the type to fit one more page. Cut words first.
- Using small print for dates, times and places. Those are the lines readers must find.
- Giving every line the same size, so nothing looks like a heading.
- Comparing fonts by point number alone.
- Fixing sizes in a way that stops text from scaling.
FAQ
Is 12 points enough for a handout?
It is the minimum in government guidance on accessible documents. Try 14 if people will read standing up or from a distance.
Should I use points or pixels?
Use points in a word processor. Use pixels or rem on a web page. The conversion table above helps you switch between them.
Why does text look smaller in some fonts?
Letter heights differ between fonts, so the same point size can look larger or smaller. Check the page by eye.
What size works on a phone?
Body text can stay at 16 to 19 pixels, as the design system above does. Hold the phone at a normal distance and read. The guide to readable text on a phone goes further.
Sources
Each page below was opened and read on the date shown. Where a fact comes from one of them, the guide says so.
- Publishing accessible documents (GOV.UK) Checked November 19, 2026
- Type scale (GOV.UK Design System) Checked November 19, 2026
- length CSS type (MDN Web Docs) Checked November 19, 2026
- Understanding Success Criterion 1.4.4: Resize Text (W3C WAI) Checked November 19, 2026
This guide gives general information about readability. See the Disclaimer. To report a mistake, use the Corrections page.