{"course":{"slug":"design-foundations","title":"Design, before Any Software","url":"https://addaly.com/learn/design-foundations","level":"beginner","track":"create"},"lesson":{"slug":"type-rendering-on-screen-and-paper","title":"Why 10pt is fine in print and terrible on screen","url":"https://addaly.com/learn/design-foundations/type-rendering-on-screen-and-paper","position":60,"of":74,"minutes":8,"answer":"Print builds a 10pt letter from hundreds of dots while a screen builds it from about ten pixels, so screen minimums are larger (16px body.","keyIdea":"Print builds a 10pt letter from hundreds of dots while a screen builds it from about ten pixels, so screen minimums are larger (16px body, and exactly 16px on form inputs because iOS auto-zooms below that) and font smoothing declarations change stroke weight rather than sharpness."},"body":{"format":"markdown","text":"## The resolution gap\n\nA commercial press lays ink at something like 2,400 dots per inch. A standard-density screen has 96 pixels per inch, and a high-density phone has the equivalent of two or three hundred.\n\nSo a 10-point letter in print is built from hundreds of dots in each direction and can carry fine serifs, hairline strokes and delicate curves. The same letter at 10 pixels on a 1x screen has about ten pixels of total height, of which perhaps five are the x-height. There is no room for a hairline. There is barely room for a stem and a counter.\n\nThat is the whole reason screen minimums are larger than print minimums, and it is why advice imported from print typography (9pt captions, high-contrast faces, tight leading) produces unreadable web pages.\n\n**Working minimums:** 16px for body text on screen, 12px absolute floor for anything, against 9 to 10pt comfortably readable in print and 7pt as the floor for legal small print.\n\n## The iOS zoom trap\n\nA concrete consequence that catches people constantly. On iOS, Safari automatically zooms the page when a user taps into a form input whose font size is below 16px. The layout jumps, the user loses their place, and zooming back out is manual.\n\nThe fix is to set inputs at 16px or larger. Not a rounding error: exactly 16 or above:\n\n```css\ninput, select, textarea { font-size: 16px; }\n```\n\nThis single rule removes an irritation that appears on a large share of forms on the web.\n\n## Hinting and antialiasing\n\n**Hinting** is a set of instructions inside the font telling the rasteriser how to snap stems onto the pixel grid at small sizes, so that two stems that should be the same width do not end up one pixel and two. It mattered enormously at 96dpi. At device pixel ratios of 2 and 3 it matters much less, because there are enough pixels that a slight misalignment is invisible.\n\n**Antialiasing** fills the edge pixels with intermediate values so curves do not look like staircases. Two kinds exist: greyscale, and subpixel, which uses the separate red, green and blue elements within each pixel to gain three times the horizontal resolution. Subpixel rendering produced visibly sharper text at 1x and produced colour fringing if the screen's subpixel order differed or the screen was rotated. Apple removed subpixel antialiasing from macOS in Mojave, because high-density displays made it unnecessary.\n\nOne practical note. The declaration `-webkit-font-smoothing: antialiased` is widely copied into stylesheets as a fix. What it actually does on macOS is force greyscale antialiasing, which makes text visibly **thinner** than the default. On a light background that often looks worse, not better. On a dark background it partly offsets the halation thickening from the colour block, which is sometimes a genuine reason to use it, but apply it knowing that it is a weight change, not a sharpening.\n\n## What you cannot control\n\nA longer list than most designers expect:\n\n- The operating system's rendering engine, which differs between Windows, macOS, Android and Linux.\n- Whether the user has increased their default font size, which they are entitled to do and which your layout must survive.\n- Browser zoom level.\n- Screen density and subpixel arrangement.\n- Whether a web font loaded at all, and what the fallback did to the layout while it did not.\n\nThe design conclusion is to build with margin rather than with precision. A layout that only works at exactly 16px with exactly one typeface at exactly 100% zoom is a layout that breaks for a substantial number of real readers.\n\n## The font loading moment\n\nOne last screen-specific concern. While a web font downloads, the browser shows either nothing or the fallback face. `font-display: swap` shows the fallback immediately and swaps when the font arrives, which is almost always the right choice: invisible text is worse than text that changes.\n\nThe swap produces a visible reflow if the fallback has different metrics, and that jump is exactly what `size-adjust` and `font-size-adjust` in an `@font-face` block exist to reduce. Matching the fallback's x-height to the web font's makes the swap nearly invisible, which is the x-height arithmetic from the type block doing practical work."},"check":{"question":"A designer copies a caption style from a print layout (9pt, a high-contrast serif, tight leading) onto a web page and finds it nearly unreadable on a standard-density laptop. Which explanation is most complete?","options":[{"text":"Serif faces are unsuited to screens, and the caption should be set in a sans-serif at the same size.","correct":false,"tempting":"Repeats a blanket claim about serifs rather than identifying the resolution that makes this particular face fail."},{"text":"9pt is below the 12px absolute floor for screen text, so no typeface or spacing choice could rescue it at that size.","correct":false,"tempting":"Correctly identifies that the size is too small while ignoring that the face's hairlines fail well above that floor."},{"text":"At around 96 pixels per inch there are too few pixels to render hairline strokes, so the face's thin strokes drop out and the tight leading merges the lines.","correct":true},{"text":"Print measurements in points do not translate to CSS pixels, so the caption is rendering at roughly two-thirds of its intended size and needs converting at 96dpi first.","correct":false,"tempting":"Raises a genuine unit conversion that would enlarge the text slightly without addressing why the strokes themselves disappear."}]},"prev":{"slug":"thumb-reach-and-one-handed-use","title":"Where a thumb can actually go","url":"https://addaly.com/learn/design-foundations/thumb-reach-and-one-handed-use"},"next":{"slug":"empty-error-and-loading-states","title":"The five screens nobody designs","url":"https://addaly.com/learn/design-foundations/empty-error-and-loading-states"},"authorship":"Founder and series editor: Dr Mustafa Mun. Written by AI models to a written standard. Source and assessment review continues. Academic review invited.","review":{"status":"Draft, open for academic review"},"cite":"Addaly (2026) 'Why 10pt is fine in print and terrible on screen', in Design, before Any Software. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/design-foundations/type-rendering-on-screen-and-paper (Accessed: 21 November 2026).","licence":{"name":"CC BY-NC-SA 4.0","url":"https://creativecommons.org/licenses/by-nc-sa/4.0/"},"reader":{"schema":1,"title":"Why 10pt is fine in print and terrible on screen","courseTitle":"Design, before Any Software","module":{"index":6,"slug":"real-screens-and-surfaces","title":"Real screens, real thumbs, real paper"},"answer":null,"keyIdea":"Print builds a 10pt letter from hundreds of dots while a screen builds it from about ten pixels, so screen minimums are larger (16px body, and exactly 16px on form inputs because iOS auto-zooms below that) and font smoothing declarations change stroke weight rather than sharpness.","hero":{"kind":"plate","image":null,"alt":null,"caption":null},"blocks":[{"t":"h2","id":"the-resolution-gap","runs":[{"text":"The resolution gap"}]},{"t":"p","runs":[{"text":"A commercial press lays ink at something like 2,400 dots per inch. A standard-density screen has 96 pixels per inch, and a high-density phone has the equivalent of two or three hundred."}]},{"t":"p","runs":[{"text":"So a 10-point letter in print is built from hundreds of dots in each direction and can carry fine serifs, hairline strokes and delicate curves. The same letter at 10 pixels on a 1x screen has about ten pixels of total height, of which perhaps five are the x-height. There is no room for a hairline. There is barely room for a stem and a counter."}]},{"t":"p","runs":[{"text":"That is the whole reason screen minimums are larger than print minimums, and it is why advice imported from print typography (9pt captions, high-contrast faces, tight leading) produces unreadable web pages."}]},{"t":"p","runs":[{"text":"Working minimums:","b":true},{"text":" 16px for body text on screen, 12px absolute floor for anything, against 9 to 10pt comfortably readable in print and 7pt as the floor for legal small print."}]},{"t":"h2","id":"the-ios-zoom-trap","runs":[{"text":"The iOS zoom trap"}]},{"t":"p","runs":[{"text":"A concrete consequence that catches people constantly. On iOS, Safari automatically zooms the page when a user taps into a form input whose font size is below 16px. The layout jumps, the user loses their place, and zooming back out is manual."}]},{"t":"p","runs":[{"text":"The fix is to set inputs at 16px or larger. Not a rounding error: exactly 16 or above:"}]},{"t":"code","lang":"css","label":"CSS","text":"input, select, textarea { font-size: 16px; }"},{"t":"p","runs":[{"text":"This single rule removes an irritation that appears on a large share of forms on the web."}]},{"t":"h2","id":"hinting-and-antialiasing","runs":[{"text":"Hinting and antialiasing"}]},{"t":"p","runs":[{"text":"Hinting","b":true},{"text":" is a set of instructions inside the font telling the rasteriser how to snap stems onto the pixel grid at small sizes, so that two stems that should be the same width do not end up one pixel and two. It mattered enormously at 96dpi. At device pixel ratios of 2 and 3 it matters much less, because there are enough pixels that a slight misalignment is invisible."}]},{"t":"p","runs":[{"text":"Antialiasing","b":true},{"text":" fills the edge pixels with intermediate values so curves do not look like staircases. Two kinds exist: greyscale, and subpixel, which uses the separate red, green and blue elements within each pixel to gain three times the horizontal resolution. Subpixel rendering produced visibly sharper text at 1x and produced colour fringing if the screen’s subpixel order differed or the screen was rotated. Apple removed subpixel antialiasing from macOS in Mojave, because high-density displays made it unnecessary."}]},{"t":"p","runs":[{"text":"One practical note. The declaration "},{"text":"-webkit-font-smoothing: antialiased","code":true},{"text":" is widely copied into stylesheets as a fix. What it actually does on macOS is force greyscale antialiasing, which makes text visibly "},{"text":"thinner","b":true},{"text":" than the default. On a light background that often looks worse, not better. On a dark background it partly offsets the halation thickening from the colour block, which is sometimes a genuine reason to use it, but apply it knowing that it is a weight change, not a sharpening."}]},{"t":"h2","id":"what-you-cannot-control","runs":[{"text":"What you cannot control"}]},{"t":"p","runs":[{"text":"A longer list than most designers expect:"}]},{"t":"ul","items":[[{"text":"The operating system’s rendering engine, which differs between Windows, macOS, Android and Linux."}],[{"text":"Whether the user has increased their default font size, which they are entitled to do and which your layout must survive."}],[{"text":"Browser zoom level."}],[{"text":"Screen density and subpixel arrangement."}],[{"text":"Whether a web font loaded at all, and what the fallback did to the layout while it did not."}]]},{"t":"p","runs":[{"text":"The design conclusion is to build with margin rather than with precision. A layout that only works at exactly 16px with exactly one typeface at exactly 100% zoom is a layout that breaks for a substantial number of real readers."}]},{"t":"h2","id":"the-font-loading-moment","runs":[{"text":"The font loading moment"}]},{"t":"p","runs":[{"text":"One last screen-specific concern. While a web font downloads, the browser shows either nothing or the fallback face. "},{"text":"font-display: swap","code":true},{"text":" shows the fallback immediately and swaps when the font arrives, which is almost always the right choice: invisible text is worse than text that changes."}]},{"t":"p","runs":[{"text":"The swap produces a visible reflow if the fallback has different metrics, and that jump is exactly what "},{"text":"size-adjust","code":true},{"text":" and "},{"text":"font-size-adjust","code":true},{"text":" in an "},{"text":"@font-face","code":true},{"text":" block exist to reduce. Matching the fallback’s x-height to the web font’s makes the swap nearly invisible, which is the x-height arithmetic from the type block doing practical work."}]}],"check":{"question":[{"text":"A designer copies a caption style from a print layout (9pt, a high-contrast serif, tight leading) onto a web page and finds it nearly unreadable on a standard-density laptop. Which explanation is most complete?"}],"options":[{"text":[{"text":"Serif faces are unsuited to screens, and the caption should be set in a sans-serif at the same size."}],"correct":false,"tempting":[{"text":"Repeats a blanket claim about serifs rather than identifying the resolution that makes this particular face fail."}]},{"text":[{"text":"9pt is below the 12px absolute floor for screen text, so no typeface or spacing choice could rescue it at that size."}],"correct":false,"tempting":[{"text":"Correctly identifies that the size is too small while ignoring that the face’s hairlines fail well above that floor."}]},{"text":[{"text":"At around 96 pixels per inch there are too few pixels to render hairline strokes, so the face’s thin strokes drop out and the tight leading merges the lines."}],"correct":true,"tempting":null},{"text":[{"text":"Print measurements in points do not translate to CSS pixels, so the caption is rendering at roughly two-thirds of its intended size and needs converting at 96dpi first."}],"correct":false,"tempting":[{"text":"Raises a genuine unit conversion that would enlarge the text slightly without addressing why the strokes themselves disappear."}]}],"order":[0,3,2,1],"why":null},"prev":{"slug":"thumb-reach-and-one-handed-use","title":"Where a thumb can actually go","minutes":8},"next":{"slug":"empty-error-and-loading-states","title":"The five screens nobody designs","minutes":9}}}