TYPEMATCHSEO
Launch

TYPEMATCH.

V2.1

Browse Directory
700
400
PAIRING ID: FRA-IBM // ETHOS: SERIF + SANS-SERIF

Balancing Fraunces with IBM Plex Sans

Build a contrast-first system where Fraunces leads and IBM Plex Sans keeps long-form content legible.

Display Face

Fraunces

Weight: 700

Body Face

IBM Plex Sans

Weight: 400

This pairing is engineered for teams that need a clear hierarchy without sacrificing brand voice. Fraunces brings variable, soft-serif, personality energy to hero units, pricing sections, and campaign headlines. IBM Plex Sans absorbs the heavy lifting for paragraphs, product storytelling, and UI labels with its corporate, neutral, humanist texture and dependable rhythm. Together they create a typography stack that scales from high-impact landing pages to dense documentation without retooling your CSS tokens.

Typographic Hierarchy & Scale

H1The Quick Fox
H2The Quick Fox
H3The Quick Fox
PThe quick brown fox jumps over...
Dark Context
Aa

High contrast negative space.

Accent
Gg

Legibility on high-chroma.

Pairing Strategy

Balancing Fraunces with IBM Plex Sans

Build a contrast-first system where Fraunces leads and IBM Plex Sans keeps long-form content legible.

This pairing is engineered for teams that need a clear hierarchy without sacrificing brand voice. Fraunces brings variable, soft-serif, personality energy to hero units, pricing sections, and campaign headlines. IBM Plex Sans absorbs the heavy lifting for paragraphs, product storytelling, and UI labels with its corporate, neutral, humanist texture and dependable rhythm. Together they create a typography stack that scales from high-impact landing pages to dense documentation without retooling your CSS tokens.

Fraunces thrives as a headline face thanks to its variable, soft-serif, personality qualities. Use weights 700–900 for crisp editorial lockups.
IBM Plex Sans excels in paragraphs and UI thanks to its corporate, neutral, humanist traits. Keep it between weights 400–600 for optimal readability.
Hierarchy guidance: run a 1:1.4 modular scale and reserve Fraunces for H1–H3 while IBM Plex Sans powers captions, body copy, and data tables.

Best-Fit Use Cases

  • High-growth SaaS landing pages that require variable hero statements with trustworthy product copy.
  • Editorial magazines and thought-leadership hubs where Fraunces can dramatize pull quotes while IBM Plex Sans keeps 1,500-word essays skimmable.
  • Conversion funnels or onboarding flows that need IBM Plex Sans's corporate voice to balance Fraunces's attention-grabbing display.

Accessibility Notes

Maintain a minimum 4.5:1 contrast ratio for IBM Plex Sans body copy and loosen letter-spacing to 0.01em for uppercase Fraunces moments. Pairing different categories demands disciplined color pairing—test both light and dark themes to ensure IBM Plex Sans does not bloom at small sizes.

CSS Implementation Cheatsheet

:root {
  --tm-header-family: 'Fraunces', serif;
  --tm-body-family: 'IBM Plex Sans', sans-serif;
  --tm-header-weight: 700;
  --tm-body-weight: 400;
  --tm-header-tracking: -0.01em;
  --tm-body-tracking: 0em;
}
Heading scale: clamp(2.75rem, 4.5vw, 5.25rem) for H1, clamp(1.5rem, 2.8vw, 3rem) for H2, and keep paragraph size at 1rem–1.125rem with 1.6 line-height.
Component guidance: Buttons inherit Fraunces at 700 for momentum, while forms, tables, and footnotes stay on IBM Plex Sans with 400 weight for predictable kerning.

FAQs

Why does Fraunces make sense as the lead font?

Fraunces owns the emotional register of this system. Its variable, soft-serif, personality profile helps anchor campaign creative, meaning marketing and product teams can reuse the same voice without reinventing the scale.

Where should IBM Plex Sans show up?

IBM Plex Sans is the workhorse. Keep it in paragraphs, long-form editorial, knowledge bases, or anywhere legibility is non-negotiable. Its corporate, neutral, humanist qualities reduce fatigue on dense layouts.

Does this pairing support complex localization?

Yes—both families are available on Google Fonts with generous glyph coverage. Test cyrillic/latin accents early, but most Latin-based locales and UI patterns are fully supported.