BlogUI/UX

Type Scales for Product UI: Why Marketing Scales Break Apps

Big, dramatic type scales look great on landing pages and fall apart in dashboards. Here's why designers make this mistake and how to build a scale that fits an app.

Denny Pratama

09 Nov 2026 · 6 min read · UI/UX

Type Scales for Product UI: Why Marketing Scales Break Apps

A lot of type scales I see in design files come from a landing page. Someone picks a ratio, say 1.5, starts at 16px and generates a ladder: 16, 24, 36, 54, 81. It looks confident and clean in the type specimen.

Then it gets applied to an app, and the app feels wrong. Headings shout over the data. Cards have to grow to fit their titles. Nothing sits close enough in size to show a quiet difference between two kinds of information.

This is a common mistake, and I think it's worth understanding why it happens, because the fix is not complicated.

01Why marketing scales don't transfer

A marketing page has few elements and one job: get attention, then guide the eye down a path. Big jumps in size are useful there. The contrast is the point.

A product screen has the opposite problem. It has lots of elements, and most of them are the same kind of thing: labels, values, table cells, helper text, buttons, tags. The hierarchy is subtle, and users scan it repeatedly rather than read it once.

A scale with big steps gives you very few useful sizes in the range where an app lives, roughly 11px to 20px. In that range, a 1.5 ratio gives you maybe two sizes. You need more than that.

02Why it happens

I think there are three reasons, and I've felt the pull of all of them as a designer.

  • Scale generators are everywhere. Pick a ratio, get a ladder. It feels principled, so you trust it.
  • We start from the homepage. The marketing site is often designed first, and its type styles become the "brand" styles that get copied into the product.
  • Big type is easy to make look good. A large heading in a nice typeface looks designed. Careful 13px label styling doesn't photograph well, but it's what makes an app usable.

03Start from the small end

For product UI, I'd flip the process. Decide the small sizes first, because that's where most of the screen lives, and add large sizes later if you need them.

Here's a hypothetical set of tokens for a dashboard:

  • Caption: 12px, for timestamps, helper text and table footnotes
  • Small: 13px, for table cells and dense lists
  • Body: 14px, for default UI text and form inputs
  • Large body: 16px, for descriptions and longer reading
  • Heading S: 18px, for card and section titles
  • Heading M: 24px, for page titles
  • Heading L: 32px, for rare things like an empty-state hero or a big metric

The steps here are small at the bottom and larger at the top. That's deliberate. A strict ratio would not give you this, and that's fine. The scale exists to serve the interface, not the other way round.

Keep the number of sizes low

Seven sizes is plenty. Every extra size is another decision for whoever builds the screen, and more chances for near-duplicates like 14px and 15px that nobody can tell apart.

If two sizes differ by one pixel, merge them.

04Use weight, colour and spacing before size

In dense UI, size is the blunt tool. Often you can make hierarchy clearer without changing size at all.

  • Weight: a 14px label in medium weight reads differently from 14px regular body text.
  • Colour: secondary text in a muted tone steps back without shrinking. Just keep contrast above WCAG's 4.5:1 for normal-size text, since muted greys are where designers often slip below it.
  • Spacing: grouping related items closer together and separating groups does a lot of hierarchy work for free.

Say a table has a name column and an email column. Same size, but the name is medium weight in the primary colour and the email is regular in the muted colour. That's enough. No need for a 16px and a 13px.

05Details that make a scale hold up

Line height by role

One line-height value for everything is a common shortcut. Tight line height suits headings and single-line labels. Body text that wraps needs more room. Define line height per style, not globally.

Numbers need attention

Dashboards are full of numbers. Many fonts offer tabular figures, where every digit has the same width, so columns of numbers align and don't jitter when values change. In CSS that's font-variant-numeric: tabular-nums. If your typeface supports it, turn it on for tables and metrics.

Use relative units

Developers will often implement type in rem rather than px, so text respects the user's browser font setting. That is worth asking for. When you hand off, give both values, like "14px / 0.875rem", so there's no guessing. If you're building with AI tools, check that the generated CSS didn't hard-code pixel sizes in places.

Check on real content

A type scale looks fine with "Lorem ipsum" and "Revenue." It looks different with a 40-character project name or a long customer email. Test the scale with ugly content before calling it done. The same goes for empty and sparse screens, where oversized type can look strange; I touched on that in the empty states breakdown.

06A quick test for your own scale

Open a real, busy screen and squint. Can you tell the page title, the section titles, the primary data and the secondary data apart? If yes, the scale is probably working.

Then ask:

  1. Is anything bigger than it needs to be just because the scale had a slot for it?
  2. Are there two sizes I can't tell apart?
  3. Is the smallest text still readable and above contrast minimums?
  4. Does the same role always use the same style?

If you're checking AI-built screens, that last one matters a lot. Generated UI tends to invent sizes screen by screen, which is one reason I keep a review checklist handy.

07The short version

Marketing scales are built for drama. Product scales are built for quiet, repeated scanning. Start with the small sizes, keep the count low, let weight, colour and spacing carry hierarchy, and test on real content.

You'll end up with a scale that looks less impressive in a specimen and works far better in the app.

08Frequently asked questions

How many font sizes does a product UI actually need?

Most product interfaces work with five to seven sizes. That usually covers a small caption, body, a slightly larger body or label, and two or three heading levels. If you keep adding sizes, you are probably solving a hierarchy problem with size when weight, colour or spacing would do.

What is the minimum body text size for a dashboard?

There is no official WCAG minimum font size. In practice, 14px is a common floor for dense product UI and 16px is safer for long reading. Check real screens, because a font with a small x-height can look smaller than its number suggests.

Should I use a modular scale ratio like 1.25 or 1.5?

A ratio is a fine starting point for headings, but don't force the small end to follow it. Product UI needs several sizes packed close together, so I'd pick the small sizes by hand and use a ratio only for the larger steps.

UI/UX

Denny Pratama

Product designer in Indonesia. Since 2018 I’ve designed SaaS products, dashboards and marketing sites, and now I build my own designs too.

About me