Custom fonts without compromise using Next.js and `next/font`

As web developers, we know the importance of typography in design. Custom fonts can set the tone for a website and enhance its overall aesthetic. However, using custom fonts can often create issues with website performance and user experience.

One of the biggest issues with custom fonts is the Cumulative Layout Shift (CLS) that occurs when a font takes too long to load. These Flashes of Unstyled Content (FOUC) can alter the positioning of elements already on the page and make it difficult to navigate. CLS and FOUC can also impact an application's search engine ranking.

On Vercel’s external websites, we used to solve these problems with the workarounds that we’ll talk about below. However, with the release of Next.js 13, we switched to next/font, which cut down on complex code, client-side JavaScript, and layout shift.

Before next/font

At vercel.com and nextjs.org, we were optimizing our font loading in a few key ways:

1. We hosted our font ourselves, instead of using a third-party URL like Google Fonts.
2. We preloaded the font using <meta> tags.
3. We only preloaded the Latin subset of characters. This is enough for English, and other subsets could still load in as needed.
4. We specified fallback fonts that looked as similar as possible to our desired font. This included fonts that weren’t technically “web safe,” but were still available on many users’ devices.
5. We set the font-display CSS property to optional so that the text on the page wouldn’t flicker and cause layout shift if it loaded late.
6. We used client-side JavaScript to detect if a user has visited Vercel's site before, and if not, we served them the fallback font for a zero layout-shift experience.

As you might guess, these optimizations took some complex workarounds in the codebase.

Here’s the relevant code from the return statement of our old next/head, which was rendered on every page:

<script
dangerouslySetInnerHTML={{
    __html: `
    if (!window.newVisit && document.cookie && document.cookie.indexOf('beenHere=1') !== -1) {
      document.documentElement.classList.add('inter')
    } else {
      window.newVisit=true
    }
    setTimeout(function() {
      document.cookie='beenHere=1;samesite=lax;expires='+
      new Date(Date.now()+31*3600*24*1000).toGMTString()
    })`,
  }}
/>
<link
  as="font"
  crossOrigin="anonymous"
  href="https://assets.vercel.com/raw/upload/v1660068731/fonts/4/Inter.var.latin.woff2"
  rel="preload"
  type="font/woff2"
/>

And here’s code from our old CSS:

:root {
  --font-sans: -apple-system, BlinkMacSystemFont, 'Segoe UI', 'Roboto',
    'Oxygen', 'Ubuntu', 'Cantarell', 'Fira Sans', 'Droid Sans', 'Helvetica Neue',
    sans-serif;
}

:root.inter {
  --font-sans: 'Inter', -apple-system, BlinkMacSystemFont, 'Segoe UI', 'Roboto',
    'Oxygen', 'Ubuntu', 'Cantarell', 'Fira Sans', 'Droid Sans', 'Helvetica Neue',
    sans-serif;
}

In addition to these adjustments, we also optimized the font through manual subsetting, such as the example below:

@font-face {
  font-family: 'Inter';
  font-style: normal;
  font-weight: 100 900;
  font-display: optional;
  src: url('https://assets.vercel.com/raw/upload/v1660068731/fonts/4/Inter.var.latin.woff2')
    format('woff2');
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA,
    U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212,
    U+2215, U+FEFF, U+FFFD;
}

/* Plus eight more @font-face definitions for other languages and characters. */

As you can imagine, we’d need to adjust and lengthen the code for any new fonts we wished to add.

Enter next/font

With far less code, next/font reliably incorporates all the optimizations mentioned above for either third-party or first-party fonts. Automatic self-hosting—which means total elimination of external network requests—contributes to the bulk of the magic. Plus, your self-hosted font file is further optimized to preload only the characters your website needs.

Where next/font takes it a step further is preventing layout shift entirely. It calculates the size-adjust property based on the actual font files (.ttf or .woff2, for example), making the calculation available on the server before the font is even requested. This allows next/font to generate a fallback font that matches the spacing of your custom font, ensuring a seamless swap.

To fully leverage the fallback font, we set display: "swap" when configuring the font object. This just allows the browser to swap the custom font in, even if it's slow to load.

In total, here’s what the new code looks like:

import { Inter } from 'next/font/google';

const interFont = Inter({
  display: 'swap',
  subsets: ['latin'],
  variable: '--font-sans',
});

export const interFontClass = interFont.variable;

We can then easily add new fonts and use this one throughout our site as needed. You’ll notice we used the variable property, which allows us to reference the variable without changing our existing CSS. You can also use this for easy integration with TailwindCSS in your own project.

Check out the video below for a full demonstration of next/font:

next/font is now included in Next.js 13, so no additional installation is required. This also means when importing, you can drop the @ in front of next/font.

Additionally, when using the new Next.js 13 App Router, you can place font imports in specific layouts, only preloading fonts you need for specific pages the user navigates to. Do take care to import your font in the highest common layout for all pages that need it, to avoid loading in multiple instances of the font.

Bring your own fonts

Web typography has significant impact on a website's overall design and user experience. Custom fonts bring out your brand’s uniqueness, and with next/font, you don’t have to worry about all the baggage that used to come with them.

If you're ready to enhance your own applications’s typographical performance, get started with the documentation on next/font.

Explore more

Watch on YouTube

Docs for `next/font`

Related reading

How to build zero-CLS A/B tests with Next.js and Vercel Edge Config

Elijah Cobb, Samuel Foster, and 1 other

Improving readability with React Wrap Balancer

Shu Ding, Emil Kowalski, and 1 other

Less code, better UX: Fetching data faster with the Next.js 13 App Router

Alice Alexandra Moore, Ariel Kanter