TYPEMATCHSEO
Launch

TYPEMATCH.

V2.1

Browse Directory
700
400
PAIRING ID: RUS-SOR // ETHOS: SANS-SERIF + SANS-SERIF

Systematizing Russo One & Sora

Build a mono-category system where Russo One leads and Sora keeps long-form content legible.

Display Face

Russo One

Weight: 700

Body Face

Sora

Weight: 400

This pairing is engineered for teams that need a clear hierarchy without sacrificing brand voice. Russo One brings russian, bold, strong energy to hero units, pricing sections, and campaign headlines. Sora absorbs the heavy lifting for paragraphs, product storytelling, and UI labels with its digital, crisp, tech 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 Russo One & Sora

Build a mono-category system where Russo One leads and Sora keeps long-form content legible.

This pairing is engineered for teams that need a clear hierarchy without sacrificing brand voice. Russo One brings russian, bold, strong energy to hero units, pricing sections, and campaign headlines. Sora absorbs the heavy lifting for paragraphs, product storytelling, and UI labels with its digital, crisp, tech 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.

Russo One thrives as a headline face thanks to its russian, bold, strong qualities. Use weights 400–600 for crisp editorial lockups.
Sora excels in paragraphs and UI thanks to its digital, crisp, tech traits. Keep it between weights 400–600 for optimal readability.
Hierarchy guidance: run a 1:1.2 modular scale and reserve Russo One for H1–H3 while Sora powers captions, body copy, and data tables.

Best-Fit Use Cases

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

Accessibility Notes

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

CSS Implementation Cheatsheet

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

FAQs

Why does Russo One make sense as the lead font?

Russo One owns the emotional register of this system. Its russian, bold, strong profile helps anchor campaign creative, meaning marketing and product teams can reuse the same voice without reinventing the scale.

Where should Sora show up?

Sora is the workhorse. Keep it in paragraphs, long-form editorial, knowledge bases, or anywhere legibility is non-negotiable. Its digital, crisp, tech 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.