Why a Point Isn't Always a Point: Typography's Most Confusing Unit

Open any design app and you'll be asked to pick a font size in points. Switch to a browser developer tool and suddenly everything is in pixels. Open InDesign and you might find picas, ems, and the occasional didot lurking in a dropdown. For something as simple as "how big should this letter be?", typography offers a baffling number of answers — and none of them quite agree.

As a recent piece on Vocal Media noted, points are one of those "weird units of measurement" that survive long after the conditions that produced them disappeared. Unlike the metre or the kilogram, the point was never standardised once and for all. It was standardised repeatedly, in different countries, by different industries — and the leftovers of every era are still baked into the software designers and developers use every day.

A short history of a small unit

The point originated in metal type. Printers needed a way to specify the height of a slug of lead, and individual foundries each had their own conventions. By the 18th century the French typographer Pierre Simon Fournier had proposed a standard point, which his contemporary François-Ambroise Didot refined into what became known as the Didot point — roughly 0.376 millimetres. It dominated continental Europe for the next two centuries.

Meanwhile, the English-speaking world went its own way. In the 1880s, American foundries settled on the pica point, defined so that 12 points equalled one pica and 6 picas approximately equalled one inch. That "approximately" is doing a lot of work: the American point came out to about 0.3514 millimetres, close to the Didot but not the same.

Then desktop publishing arrived. When Adobe built PostScript in the 1980s, it needed a clean, computable definition. It rounded the pica point to exactly 1/72 of an inch, or roughly 0.3528 mm. This is the "DTP point" or "PostScript point," and it's what almost every modern app means when it says "pt." The Didot, the Fournier and the old American pica point all still exist on paper — they just lost the software war.

Why points don't measure what you think they measure

Here's the part that trips up nearly every new designer: a 12-point font is not a font whose letters are 12 points tall.

Back in the metal-type era, the point referred to the height of the physical metal body the letter sat on — including the small gap above and below the glyph. The actual printed letter was always smaller than the nominal size, and the ratio varied between typefaces. Digital fonts inherited this convention. The "em square" of a font (the abstract box every glyph is designed within) is what the point size actually scales. The cap height, x-height and ascender height are all proportions inside that box, and every type designer chooses them differently.

This is why Helvetica at 12pt looks noticeably bigger than Garamond at 12pt. They have the same em square, but Helvetica fills more of it. There is no universal way to ask "how tall is this letter on the page?" — only "how big is the invisible box around it?"

Enter the pixel, and the chaos doubles

On screen, the picture gets worse. CSS defines its reference pixel as 1/96 of an inch, which gives the neat conversion 1pt = 1.333px. But that's an idealised pixel. Actual screens have wildly different physical densities — a budget Android phone, a 4K monitor and a Retina iPad all render "16px" using very different numbers of hardware pixels.

To paper over this, modern operating systems introduced device-independent pixels (sometimes called CSS pixels, dp, or pt on iOS — yes, Apple confusingly reused the word "point" for something completely different). Your iPhone's 1pt is not Adobe's 1pt. Apple's point is roughly 1/163 of an inch on older devices, scaled by the device's pixel ratio. It's a coordinate-system unit, not a typographic one.

The result: a developer writing font-size: 12pt in CSS, an iOS engineer writing UIFont.systemFont(ofSize: 12), and a print designer setting body copy at 12pt in InDesign are all producing different physical sizes, even if everything renders "correctly."

Picas, ems, and the other survivors

Points aren't the only oddity. A few siblings worth knowing:

None of these are wrong. They're just artefacts of different industries solving the same problem in isolation, then refusing to throw away the answer when the world changed.

What this means if you actually make things

For Australian designers and developers working across print, web and mobile, the practical takeaways are simpler than the history suggests:

For print, trust the point — but remember it measures the em square, not the glyph. If you need a specific physical letter height (for signage, accessibility compliance, or packaging), measure the cap height of your chosen typeface and work backwards. AS 1428.1, the Australian standard for accessible signage, specifies letter heights in millimetres for exactly this reason.

For web, prefer relative units. rem (root em) and em respect user font-size preferences, which matters for accessibility. Pixel values are predictable but override what the reader has asked their browser to do. Avoid pt on screen — it works, but it's a print unit pretending to be a screen unit.

For mobile, read your platform's documentation carefully. Apple's "points" and Google's "dp" are roughly equivalent abstractions, but the maths underneath differs, and neither has anything to do with the typographic point your designer is using in Figma.

For everyone, when a layout looks wrong, suspect the unit before you suspect the maths. A surprising number of cross-platform bugs trace back to someone assuming "pt means pt."

A unit that refuses to die

The point is, by any rational measure, a bad unit. It's defined differently in at least four standards that are all still in use; it doesn't measure the thing its name suggests; and it has been hijacked by operating systems to mean something else entirely. Yet it persists, because the alternative — convincing every designer, printer and developer in the world to switch to millimetres tomorrow — is unthinkable.

So we live with it. Points are weird, inconsistent and historically contingent. They're also, for better or worse, the language typography speaks. Knowing where the inconsistencies hide is most of what separates a designer who fights their tools from one who understands why the tools are shaped the way they are.

Related on Bleen

Sources