The font you choose for your email signature affects how professional, modern, and trustworthy your emails appear. But email clients are ruthless with typography: Gmail strips external stylesheets, Outlook ignores web fonts, and every client has its own fallback behavior. This guide covers which fonts actually work in email signatures, why most custom fonts break, and how to choose the right one for your brand.
Typography is one of the strongest signals of professionalism. The right font makes your signature feel polished and intentional. The wrong font -- or a font that breaks and falls back to Times New Roman -- makes it look like you did not bother testing.
Unlike websites, where you can load any Google Font or custom typeface via a stylesheet, email signatures are severely constrained. Every email client processes HTML differently: Gmail strips <style> tags and @import rules, Outlook desktop uses Microsoft Word’s rendering engine, and mobile apps have their own limitations. The only reliable approach is to use fonts that are already installed on the recipient’s device.
These pre-installed, universally supported fonts are called email-safe fonts (sometimes called “web-safe” fonts). Choosing one ensures your signature looks the way you intended it to, regardless of whether the recipient is on a Mac, Windows PC, iPhone, or Android device.
These fonts are pre-installed on Windows, macOS, iOS, and Android. They render reliably in every major email client.
The most widely used email-safe font. Clean, neutral, and readable at any size. A safe default for any brand that does not have strong typographic preferences.
Font stack: Arial, Helvetica, sans-serif
Best for: Default choice, corporate, tech, SaaS
The designer's favorite. Nearly identical to Arial on Windows (where Helvetica is not installed), but renders with more polish on macOS and iOS. Use Helvetica first with Arial as fallback.
Font stack: Helvetica, Arial, sans-serif
Best for: Design, creative agencies, premium brands
The best serif option for email. Designed specifically for screens, so it is more readable than Times New Roman at small sizes. Adds a warm, traditional feel.
Font stack: Georgia, 'Times New Roman', Times, serif
Best for: Legal, consulting, editorial, academia
Designed for readability at small sizes. Its wide letterforms and generous spacing make it exceptionally legible, especially for contact details and fine print.
Font stack: Verdana, Geneva, sans-serif
Best for: Accessibility-focused brands, small text, legal disclaimers
A narrower cousin of Verdana. Popular in Windows environments and enterprise software. Clean and professional without being generic.
Font stack: Tahoma, Verdana, Geneva, sans-serif
Best for: Enterprise, IT, Windows-heavy environments
A humanist sans-serif with more personality than Arial. Its slightly irregular letterforms give it warmth and character while remaining fully professional.
Font stack: 'Trebuchet MS', Helvetica, sans-serif
Best for: Startups, creative teams, marketing
The classic serif font. Universally available but can look dated in modern business contexts. Works when you want a formal, traditional appearance.
Font stack: 'Times New Roman', Times, Georgia, serif
Best for: Government, legal, highly formal contexts
A monospaced font where every character has the same width. Unusual for email signatures but works in technical or developer-focused contexts. Use sparingly.
Font stack: 'Courier New', Courier, monospace
Best for: Developer tools, technical brands, retro aesthetics
Web fonts (Google Fonts, Adobe Fonts, custom typefaces loaded via CSS) require either an @import rule or a <link> tag in the HTML. Email clients strip both for security reasons. Here is what happens in the major clients:
Gmail (web & mobile)
Strips all <style> tags, @import rules, and <link> tags. Falls back to Arial.
Outlook desktop (Word engine)
Ignores all external font references. Falls back to Times New Roman if the font is not installed on the PC.
Outlook.com (web)
Strips <style> and @import. Falls back to the Outlook default (Calibri or Segoe UI).
Apple Mail
The most forgiving client. May support @import in some cases, but you cannot rely on it since your recipients use different clients.
Thunderbird
Partial support for <style> tags, but strips @import. Inconsistent behavior across versions.
The fix: always declare a font-family fallback stack
Even if you want to use your brand font, always include a fallback stack: font-family: 'YourBrandFont', Arial, Helvetica, sans-serif. This ensures the signature degrades gracefully when the custom font is not available, which is most of the time.
Recommended font combinations that create visual hierarchy while staying email-safe.
Name: Arial (bold, 14-16px)
Details: Arial (regular, 12px)
The safest pairing. Use weight and size variation within a single font to create hierarchy. This approach works across every email client without any rendering surprises.
Name: Georgia (bold, 14-16px)
Details: Arial (regular, 12px)
Pairs a warm serif for your name with a clean sans-serif for contact details. Creates a sophisticated contrast that works well for legal, consulting, and editorial brands.
Name: Trebuchet MS (bold, 14-16px)
Details: Verdana (regular, 12px)
Both fonts are highly readable on screen. Trebuchet adds personality to your name, while Verdana ensures your contact details are crisp and easy to scan.
Name: Helvetica (bold, 14-16px)
Details: Helvetica (regular, 12px)
Clean, modern, and refined. Helvetica has a premium feel that works for design-forward and tech brands. Falls back to Arial on Windows without noticeable difference.
A clear size hierarchy makes your signature easy to scan. Here are the recommended sizes for each element.
When you create a signature with BrandFooter, you choose a font from a curated list of email-safe options. Behind the scenes, BrandFooter generates the correct font-family declaration with a proper fallback stack. The font is applied as an inline style on every text element in the signature HTML, so it works even in Gmail (which strips <style> tags).
For teams, the font is set at the brand level. When you choose Arial for your company, every signature generated for every team member uses the same font stack. This ensures typographic consistency across your entire organization without requiring each person to configure their own settings.
Common questions about fonts in email signatures.
No. Google Fonts require an external stylesheet or @import rule, both of which Gmail and Outlook strip from HTML. Your signature will silently fall back to the system default font, which is usually Times New Roman in Outlook and Arial in Gmail. Instead, use email-safe fonts and specify a fallback stack like 'Arial, Helvetica, sans-serif'.
Use 14-16px for your name (the most prominent element), 12-13px for your job title and company, 12px for contact details like phone and email, and 10px for legal disclaimers. These sizes create a clear visual hierarchy and remain readable on both desktop and mobile screens without overwhelming the email body.
Outlook desktop uses the Microsoft Word rendering engine, which does not support web fonts, @import, or <link> tags. If your font is not installed on the recipient's computer, Outlook falls back to Times New Roman by default. The fix is to use email-safe fonts that are pre-installed on all major operating systems.
Sans-serif fonts (Arial, Helvetica, Verdana) are the most popular choice because they look clean and modern on screens. Serif fonts (Georgia, Times New Roman) work well for formal, traditional, or legal contexts. There is no wrong answer as long as you pick an email-safe font. The key is to match the font to your brand personality.
One. Using a single font family throughout your signature creates a clean, consistent appearance. If you want contrast, vary the size and weight (bold for your name, regular for details) rather than introducing a second font. Two fonts at most if your brand guidelines require it, but never more than two.
BrandFooter uses email-safe font stacks with proper fallbacks. When you select a font in the generator, BrandFooter automatically generates the correct CSS font-family declaration with fallback fonts. For example, selecting 'Arial' produces 'Arial, Helvetica, sans-serif'. This ensures your signature looks consistent across every email client.
Choose from email-safe fonts with automatic fallback stacks. Our free generator creates signatures that render perfectly in Gmail, Outlook, and Apple Mail.