TYPEMATCHSEO
Launch

TYPEMATCH.

V2.1

Browse Directory
700
400
PAIRING ID: TEN-FUG // ETHOS: SANS-SERIF + DISPLAY

Balancing Tenor Sans with Fugaz One

Build a contrast-first system where Tenor Sans leads and Fugaz One keeps long-form content legible.

Display Face

Tenor Sans

Weight: 700

Body Face

Fugaz One

Weight: 400

This pairing is engineered for teams that need a clear hierarchy without sacrificing brand voice. Tenor Sans brings humanist, display, fashion energy to hero units, pricing sections, and campaign headlines. Fugaz One absorbs the heavy lifting for paragraphs, product storytelling, and UI labels with its italic, geometric, display 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 Tenor Sans with Fugaz One

Build a contrast-first system where Tenor Sans leads and Fugaz One keeps long-form content legible.

This pairing is engineered for teams that need a clear hierarchy without sacrificing brand voice. Tenor Sans brings humanist, display, fashion energy to hero units, pricing sections, and campaign headlines. Fugaz One absorbs the heavy lifting for paragraphs, product storytelling, and UI labels with its italic, geometric, display 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.

Tenor Sans thrives as a headline face thanks to its humanist, display, fashion qualities. Use weights 400–600 for crisp editorial lockups.
Fugaz One excels in paragraphs and UI thanks to its italic, geometric, display traits. Keep it between weights 400–600 for optimal readability.
Hierarchy guidance: run a 1:1.4 modular scale and reserve Tenor Sans for H1–H3 while Fugaz One powers captions, body copy, and data tables.

Best-Fit Use Cases

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

Accessibility Notes

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

CSS Implementation Cheatsheet

:root {
  --tm-header-family: 'Tenor Sans', sans-serif;
  --tm-body-family: 'Fugaz One', display;
  --tm-header-weight: 400;
  --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 Tenor Sans at 400 for momentum, while forms, tables, and footnotes stay on Fugaz One with 400 weight for predictable kerning.

FAQs

Why does Tenor Sans make sense as the lead font?

Tenor Sans owns the emotional register of this system. Its humanist, display, fashion profile helps anchor campaign creative, meaning marketing and product teams can reuse the same voice without reinventing the scale.

Where should Fugaz One show up?

Fugaz One is the workhorse. Keep it in paragraphs, long-form editorial, knowledge bases, or anywhere legibility is non-negotiable. Its italic, geometric, display 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.