The best font for email is a web-safe font that renders identically everywhere: Arial, Helvetica, Verdana, Georgia, or the recipient's system default. For body text, set it at 14 to 16 pixels with generous line height, and always define a fallback stack.
That's the short answer, and it's boring on purpose. Email is not the place for typographic self-expression, because you don't control the rendering environment. The reader's email client does.
Here's the uncomfortable truth about email typography: that beautiful custom font you licensed for your website will silently fall back to something else in most inboxes. Outlook on Windows is especially aggressive about substitutions. If you didn't plan the fallback, Outlook plans it for you, and it usually picks Times New Roman.
This guide covers which fonts are actually safe, how fallback stacks work, what Gmail and Outlook support, and the sizes and spacing that keep your emails readable on a phone at 7 a.m.
What Makes a Font 'Email Safe'
A font is email safe when it's preinstalled on virtually every device your recipients use: Windows, macOS, iOS, and Android. If the font lives on the reader's machine, the email client just uses it. No downloads, no substitutions, no surprises.
This is different from web fonts. On a website, you can load any font via CSS and the browser fetches it. Most email clients block or ignore those font downloads for security and performance reasons. Some clients support them (Apple Mail is the notable friendly one), but the biggest client by volume, Gmail, does not support custom web fonts in the way designers wish it did.
So the practical rule: design with the system fonts you're guaranteed, and treat anything fancier as a progressive enhancement that some readers will see and most won't.
The Safest Fonts for Email, Ranked by Use Case
For clean, neutral body text: Arial. It's the workhorse. Installed everywhere, legible at small sizes, and invisible in the best way. Helvetica is the slightly more refined sibling, standard on Apple devices, and Arial substitutes for it seamlessly on Windows.
For maximum on-screen readability: Verdana. It was designed specifically for screens, with wide letterforms and generous spacing. It's excellent at 13 to 14 pixels, though it can look bulky at larger sizes.
For a warmer, editorial feel: Georgia. It's the rare serif that was built for screens rather than print, and it holds up well for newsletter-style emails. Times New Roman also renders everywhere, but it carries a dated, default-settings feel that most senders want to avoid.
For a modern-but-safe look: Tahoma and Trebuchet MS are both widely installed and slightly more distinctive than Arial without becoming risky.
For code or plain-text emphasis: Courier New is the universal monospace. Useful in developer-focused emails; avoid it for general copy.
Honorable mention: the system font stack. Using something like -apple-system, Segoe UI, Roboto, Arial tells each device to use its own native UI font: San Francisco on Apple devices, Segoe UI on Windows, Roboto on Android. Your email then looks native to each platform. Many product teams have moved to this approach because it looks current everywhere without loading anything.
Fallback Stacks: How to Write Them
A font stack is an ordered list. The client uses the first font it finds installed and ignores the rest. Every font declaration in your email should be a stack, never a single name.
A solid sans-serif stack: Helvetica Neue, Helvetica, Arial, sans-serif. Apple users get Helvetica Neue, Windows users get Arial, and the generic sans-serif at the end is the safety net.
A solid serif stack: Georgia, Times New Roman, serif.
A brand-font stack with graceful degradation: YourBrandFont, Helvetica Neue, Arial, sans-serif. Apple Mail readers may see your brand font; everyone else gets a clean fallback you chose deliberately.
Two practical warnings. First, always end with a generic family (sans-serif or serif) so nothing is left to chance. Second, test what your fallback actually looks like. If your brand font is a wide geometric sans and your fallback is narrow Arial, line breaks and button widths will shift. Pick a fallback with similar proportions so the layout survives the swap.
What Gmail and Outlook Actually Support
Gmail supports the standard web-safe fonts plus Roboto and Google Sans, and it respects your font stack as long as the fonts are on the device. It does not load external web fonts from your CSS. Design for your fallback stack and you'll be fine in Gmail on both desktop and mobile.
Outlook is the complicated one, because Outlook is really several products. Outlook on the web and the newer Outlook clients behave much like other modern clients. Classic Outlook for Windows, however, uses Microsoft Word's rendering engine, which has a notorious quirk: when it encounters a web font it can't use, it may ignore your entire stack and fall back to Times New Roman rather than the next font you listed. The common fix is to avoid referencing downloadable web fonts at all in emails, or to gate them so Outlook never sees them, keeping a plain system stack as what Outlook reads.
Apple Mail on Mac and iPhone is the most capable: it supports custom fonts loaded via CSS and renders stacks faithfully. If a meaningful share of your audience is on Apple devices, custom fonts are a genuine enhancement for them.
The strategy that follows from all this: build every email so it looks good in worst-case rendering (Arial or the system font), and treat anything better as a bonus.
Font Size, Line Height, and Spacing
Typography is more than the typeface. Sizing and spacing decide whether people actually read your email.
Body text: 14 to 16 pixels. Under 13 pixels, mobile readers start pinching to zoom, and some clients may scale tiny text unpredictably. 16 pixels is a comfortable default for longer content.
Line height: roughly 1.4 to 1.6 times the font size. Cramped line spacing is the most common reason an email feels dense even when the copy is short.
Headings: 20 to 28 pixels is plenty inside an email. Giant hero text that works on a landing page wraps awkwardly on a 375-pixel-wide phone screen.
Line length: keep your content column around 600 pixels wide. It's the long-standing email standard for a reason: it produces a readable line length on desktop and scales down cleanly on mobile.
Contrast: dark gray or black text on a light background. If you support dark mode, test it, because some clients invert colors and can turn subtle grays into unreadable mush.
Plain Text vs Designed Emails
Here's a nuance that matters if you do sales or outreach: heavily designed emails aren't always the goal.
Cold and one-to-one sales emails perform best when they look like a person typed them. That means default-looking fonts, no images, no multi-column layouts. A cold email set in a custom brand font with styled buttons pattern-matches to marketing, and readers triage marketing differently than personal mail. Spam filters weigh heavy HTML differently, too. This is why outreach platforms like ClickReach send messages that render like normal personal emails rather than newsletters: for deliverability and reply rates, plain wins.
Newsletters, product announcements, and transactional emails are the opposite case. Readers expect design, and consistent typography builds brand recognition. That's where your Georgia headlines or system-font stacks earn their keep.
Match the typography to the job. A designed cold email and a plain-text product launch are both mismatches.
FAQ: Email Fonts
What is the single best font for professional email?
If you must pick one: Arial at 14 to 16 pixels. It renders identically everywhere and never distracts from your message. Helvetica, Verdana, and Georgia are equally defensible choices.
Can I use Google Fonts like Lato or Montserrat in email?
You can reference them, but most clients, including Gmail, won't load them, and classic Outlook may punish the attempt by defaulting to Times New Roman. If you use them, gate them carefully and design the fallback first.
What font size should I use for email?
14 to 16 pixels for body text, 20 to 28 pixels for headings, and nothing below 12 pixels anywhere, including footers and legal text if you can help it.
Do fonts affect spam filtering?
Not directly by typeface choice. Indirectly, yes: excessive styling, image-heavy layouts, and tiny hidden text are patterns filters dislike. Simple, consistent typography keeps you out of that territory.
Should my email font match my website font?
Only if your website font is email safe or has a very close safe fallback. Brand consistency is nice; rendering reliably in every inbox is nicer.
Conclusion
Email typography rewards restraint. Choose a web-safe font or the system stack, write a fallback chain that ends in a generic family, set body text at 14 to 16 pixels with breathing room, and test in Gmail, Outlook, and Apple Mail before you ship.
Your readers will never compliment your email font. That's the point. The best email typography is the kind nobody notices, because nothing got in the way of reading the message.
