Choosing Fonts That Actually Survive Email

Web fonts get stripped by most email clients. Here are the typefaces that render reliably everywhere — and how to make them feel less generic.

Choosing a font for an email signature is harder than choosing one for a website. On the web you can load any of the thousands of typefaces hosted on Google Fonts, Adobe Fonts, or self-hosted. In email, most of those options vanish. Email clients strip or ignore @font-face declarations, and the recipient's system either has the font installed locally or it does not. Designing for that constraint is the difference between a signature that looks intentional everywhere and one that reverts to Times New Roman the moment it leaves your machine.

Why email clients ignore web fonts

Email clients are conservative by design. Loading custom fonts from external URLs would introduce a privacy and security surface that most clients deliberately avoid: every email open would trigger an external request, potentially leaking the recipient's IP address and read timing to whichever font server you specified. Outlook for Windows does not support external fonts at all because the underlying Word renderer does not. Gmail strips @font-face declarations from the head. Apple Mail honours system-installed fonts but not arbitrary external ones. Most webmail clients sandbox or strip @font-face for similar reasons.

The practical result is that the only fonts that render reliably across email are the ones already installed on the recipient's operating system. There is no way around this, only ways through it.

The list of fonts you can actually rely on

A surprisingly short list of fonts are installed on virtually every Windows, macOS, iOS, and Android device in current use. These are the only fonts that are safe to specify without a system-font fallback.

For sans-serif body text: Arial, Helvetica, Verdana, Tahoma, and Trebuchet MS. Arial and Helvetica are nearly identical for practical purposes and are the most universally available. Verdana is wider and more legible at small sizes. Tahoma is a slightly tighter alternative.

For serif body text: Georgia, Times New Roman, and Cambria. Georgia is the most readable on screen and is the default choice for serif signatures. Times New Roman feels institutional and is rarely the right choice for modern signatures.

For monospace or technical accents: Courier New and Consolas. Both are widely installed.

This is the complete list. Comic Sans is installed everywhere but should not be considered a serious option. Impact, Arial Black, and other display variants are installed but are generally too heavy for body text.

How to use a custom font and survive the fallback

The signature looks generic if you use only Arial. The trick is to specify your preferred custom font first, then fall back gracefully to a system font. In CSS this looks like font-family: "Inter", Arial, Helvetica, sans-serif. On a recipient who happens to have Inter installed (a small minority), the signature renders in Inter. On everyone else, it falls back to Arial — which looks reasonable in its own right.

The critical move is choosing a fallback that has similar visual proportions to the preferred font. Inter, Helvetica Neue, and Arial all have similar x-heights, widths, and weights, so a layout designed for Inter will not visibly reflow when it falls back to Arial. By contrast, a layout designed for a condensed display font might overflow its container when it falls back to a wider system font.

For email signatures specifically, use the custom font only for accent elements — your name, perhaps a job title — and use a web-safe font for all body text including phone, email, address, and any disclaimer text. This concentrates the visual risk to one or two lines where a font swap is least disruptive.

The case for one font, used confidently

Most professional signatures use a single typeface from top to bottom, varied only by weight, size, and colour. This produces a calmer, more confident result than mixing a display font with a body font. A signature in nothing but Helvetica Neue at three different sizes (bold name, regular role, smaller contact) looks more polished than a signature combining a script font for the name with a sans-serif for everything else.

If you do mix typefaces, limit yourself to two and make sure they are clearly different — a serif paired with a sans-serif, not two similar sans-serifs that look like a mistake. Pair a confident serif like Georgia with a clean sans like Helvetica, or a script display font like Alex Brush (for handwritten-style names) with a body sans.

Step by step

  1. Pick one body font from the safe list — In the Styling tab, set the body font to Arial, Helvetica, Georgia, or Verdana. This is the font 95% of your recipients will see for most of the signature.
  2. Optionally pick one display font for your name — If you want a more distinctive look, use the Display Font picker for your name only. SignatureCraft falls back to a comparable system font for recipients without the display font installed.
  3. Set sizes deliberately — Name around 16 pixels, role and company around 13 pixels, contact details around 12 pixels. Keep the contrast modest — large size jumps look amateurish.
  4. Test on Outlook and Gmail web — These render fonts most strictly. If the signature reads cleanly in both, every other client will be fine.

Tips

  • Never use more than two typefaces in a single signature — one is almost always better.
  • Avoid fonts under 11 pixels for any text the recipient might actually need to read.
  • Bold weights render more reliably than italic across email clients. Use bold for emphasis where possible.