TYPEMATCHSEO
Launch

TYPEMATCH.

V2.1

Browse Directory
700
400
PAIRING ID: PET-BAS // ETHOS: SERIF + SERIF

Systematizing Petrona & Baskervville

Build a mono-category system where Petrona leads and Baskervville keeps long-form content legible.

Display Face

Petrona

Weight: 700

Body Face

Baskervville

Weight: 400

This pairing is engineered for teams that need a clear hierarchy without sacrificing brand voice. Petrona brings ink-traps, personality, cookery energy to hero units, pricing sections, and campaign headlines. Baskervville absorbs the heavy lifting for paragraphs, product storytelling, and UI labels with its classic, transitional, history 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

Systematizing Petrona & Baskervville

Build a mono-category system where Petrona leads and Baskervville keeps long-form content legible.

This pairing is engineered for teams that need a clear hierarchy without sacrificing brand voice. Petrona brings ink-traps, personality, cookery energy to hero units, pricing sections, and campaign headlines. Baskervville absorbs the heavy lifting for paragraphs, product storytelling, and UI labels with its classic, transitional, history 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.

Petrona thrives as a headline face thanks to its ink-traps, personality, cookery qualities. Use weights 700–900 for crisp editorial lockups.
Baskervville excels in paragraphs and UI thanks to its classic, transitional, history traits. Keep it between weights 400–600 for optimal readability.
Hierarchy guidance: run a 1:1.2 modular scale and reserve Petrona for H1–H3 while Baskervville powers captions, body copy, and data tables.

Best-Fit Use Cases

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

Accessibility Notes

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

CSS Implementation Cheatsheet

:root {
  --tm-header-family: 'Petrona', serif;
  --tm-body-family: 'Baskervville', serif;
  --tm-header-weight: 700;
  --tm-body-weight: 400;
  --tm-header-tracking: -0.01em;
  --tm-body-tracking: -0.005em;
}
Heading scale: clamp(2.75rem, 3.6vw, 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 Petrona at 700 for momentum, while forms, tables, and footnotes stay on Baskervville with 400 weight for predictable kerning.

FAQs

Why does Petrona make sense as the lead font?

Petrona owns the emotional register of this system. Its ink-traps, personality, cookery profile helps anchor campaign creative, meaning marketing and product teams can reuse the same voice without reinventing the scale.

Where should Baskervville show up?

Baskervville is the workhorse. Keep it in paragraphs, long-form editorial, knowledge bases, or anywhere legibility is non-negotiable. Its classic, transitional, history 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.