Course contentsShow
← Web Development
Lesson 580 of 2,98210. Typography and Design SystemsFree lesson

Browser Support and Fallbacks

Implementing progressive enhancement with variable fonts and static font fallbacks.

Browser Support and Fallbacks for Variable Fonts

You'll learn how to use variable fonts while ensuring your site looks great even in browsers that don't support them yet.

The Core Challenge

Variable fonts are powerful but not universally supported, especially in older browsers. Progressive enhancement means serving modern features to browsers that can handle them while providing a solid fallback for those that can't. Think of it like offering a gourmet meal to those with the right equipment, while ensuring everyone else still gets a nutritious dinner.

The Progressive Enhancement Strategy

Start with a reliable static font as your baseline. This ensures all users get readable typography. Then layer on variable font features for browsers that support them:

/* Base fallback using standard static font */
body {
  font-family: 'Helvetica Neue', Arial, sans-serif;
  font-weight: 400;
}

/* Enhanced experience for browsers supporting variable fonts */
@supports (font-variation-settings: normal) {
  body {
    font-family: 'MyVariableFont', 'Helvetica Neue', sans-serif;
    font-weight: 350; /* Fine-tuned weight only variable fonts offer */
  }
}

Using @supports

The @supports rule tests for variable font capability before applying those styles. You can check for font-variation-settings support or specific high-level properties like font-optical-sizing.

The Fallback Stack Matters

Always list a static font after your variable font in the font-family stack. If the variable font fails to load or isn't supported, the browser gracefully falls back to the next font.

Key Takeaway: Use @supports to detect variable font capability and always provide static font fallbacks in your font-family stack, ensuring a reliable baseline experience before enhancing for modern browsers.