Back to Blog

How to Find the Perfect Font for Your Next Project

TL;DRChoosing a font comes down to a repeatable process: define the tone with a few adjectives, shortlist two to four typefaces, and test them on a real page with headings, buttons and body copy. Check the license covers web use and the character set covers every language you need. Then deliver it well: self-host WOFF2 files, subset them, consider a variable font, and use font-display so text appears immediately. Self-hosting Google Fonts also avoids sending visitors’ IP addresses to Google, a known GDPR issue in the EU.

Typography carries most of a website. Body copy, headings, navigation, buttons and forms are all text, so the typeface you choose shapes how the site reads, how it feels and how fast it loads.

typeface

Here’s the process we use to choose fonts for a project, and the technical checks that make sure the choice works in production.

Start with the tone, not the font list

Font libraries contain thousands of options, and scrolling through them without a brief is slow. Start by writing down three or four adjectives that describe how the brand should come across: calm, precise, established, for example, or warm, approachable, energetic.

If the adjectives conflict, such as playful and authoritative, settle that with the brand owner before looking at type. Most font decisions that go wrong are really unresolved brand decisions.

A basic understanding of type classifications helps here. Serifs tend to read as traditional or editorial, geometric sans serifs as modern and clean, humanist sans serifs as friendly and highly legible, and slab serifs as sturdy. These are tendencies, not rules, but they narrow the search quickly.

Shortlist two to four typefaces

With the adjectives in hand, browse a few trusted sources and pick two to four candidates:

  • Google Fonts offers a large library of open source families that are free to use and self-host.
  • Adobe Fonts is included with Creative Cloud and covers many professional families.
  • Independent foundries and retailers sell licenses directly, often with more complete families and better support.

For each candidate, check the practical details before you get attached to it:

  • Character set. Make sure it covers every language the site needs, including accented characters, currency symbols and punctuation.
  • Weights and styles. A body font needs at least regular, italic and bold that work well together.
  • Legibility at small sizes. Look at it at 16px and below, not just in a large specimen.
  • License. Desktop, web, app and email use are often licensed separately, and some web licenses are priced by monthly pageviews.

Free fonts aren’t automatically lower quality. Families like Inter, Source Sans 3 and Merriweather are carefully made and widely used. Free fonts from unknown sources, though, often have incomplete character sets, poor spacing or unclear licenses. A paid typeface is usually worth it when the brand needs something distinctive, because the font will appear on everything from the website to slide decks and print.

Test fonts on a real page

Specimen pages show a typeface at its best. A real page shows how it performs. Build a simple test page with real or representative content and include:

  • An H1, H2 and H3
  • Several paragraphs of body copy and a bulleted list
  • Buttons, navigation labels and form fields
  • Numbers, such as prices or statistics

Swap each candidate in and compare them at desktop and mobile sizes. Check line length, line height and how the headings pair with the body font. If you’re pairing two typefaces, look for clear contrast between them and limit the site to two families in most cases.

Keep the test page and reuse it. It makes every future font decision faster.

Know how each font source is delivered

Where a font comes from affects how you can serve it:

  • Google Fonts can be loaded from Google’s servers or downloaded and self-hosted. The families are released under open source licenses that permit self-hosting.
  • Adobe Fonts are served from Adobe’s servers through a web project embed code. They can’t be downloaded and self-hosted, and web use depends on an active Creative Cloud subscription. If the site needs fonts it controls fully, license the typeface directly from the foundry instead.
  • Foundry licenses usually include web font files (WOFF2) that you host yourself, under the terms of the license.

Self-host Google Fonts for privacy and speed

When a page loads fonts from Google’s servers, each visitor’s browser sends its IP address to Google. In January 2022, a Munich regional court found that embedding Google Fonts this way without consent breached the GDPR. Self-hosting the font files on your own domain removes that third-party request.

It’s usually faster too. Browsers no longer share cached files between websites, so loading from Google’s servers offers no caching advantage, and serving fonts from your own domain avoids an extra connection to another server.

Load fonts efficiently

  • Use WOFF2. It’s the most compressed web font format and is supported by every current browser. Older formats aren’t needed.
  • Subset the files. Remove characters the site will never use. Tools such as pyftsubset from fontTools can cut file sizes significantly, though you need to keep every character your content and languages require.
  • Consider a variable font. A single variable font file can replace several separate weights, which often means fewer requests and less data.
  • Set font-display. font-display: swap shows text immediately in a fallback font and swaps in the web font when it loads, so text is never invisible. Use optional where avoiding layout shift matters more than always showing the web font.
  • Preload only the critical file. Preload the one or two fonts used above the fold, not the whole family.
  • Match the fallback font. The size-adjust and related @font-face descriptors let you tune a system fallback so the swap causes little or no layout shift.
@font-face {
  font-family: "Inter";
  src: url("/fonts/inter-var-latin.woff2") format("woff2");
  font-weight: 100 900;
  font-display: swap;
}

Build a reference collection

The fastest way to get better at choosing fonts is to notice them. When a site’s typography stands out, identify the font with your browser’s developer tools (the Computed tab shows the rendered font) or an extension such as WhatFont, and save it with a screenshot and a note about why it works. Over time, that collection becomes the first place you look.

Want typography that looks right and loads fast across your whole site? Hey Reliable’s front-end development team handles font loading, self-hosting and performance as part of every build. Get a proposal for your project.

Get started now

Start with a risk-free, no obligation proposal delivered to your inbox in one business day or less.

Get Started
  • 5-Star Rated Technical Partner
  • 100% White-Label - Sign our NDA
  • 90-Day Code Guarantee
Hey Reliable logo

Welcome to Hey Reliable

We’d love to hear from you. Please use the form below or email info@heyreliable.com.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Secret Link