E-Mail-Signatur-Schriftarten, die in jedem wichtigen E-Mail-Client überleben
You open a beautifully crafted email on your phone. The recipient’s Outlook client strips your carefully chosen web font, falls back to Times New Roman, and your signature now looks like a ransom note. This is the reality of email rendering: each client has its own CSS parser, font fallback logic, and security restrictions. If you want a signature that looks professional in Gmail, Outlook, Apple Mail, and every dark-mode variant in between, you must choose fonts that survive the rendering gauntlet.
The rendering landscape: what actually happens
Every major email client handles fonts differently. Gmail strips <link> and @import stylesheets, so any web font you try to load from Google Fonts or Typekit will simply not appear. Outlook (both desktop and web) uses the Word HTML rendering engine, which ignores font-family declarations that reference fonts not installed on the local system. Apple Mail respects web fonts but only if they are served over HTTPS and the user has not disabled remote content loading. Resend, SendGrid, and other transactional email APIs pass through your HTML faithfully, but the recipient’s client still applies its own rules.
The practical outcome: you cannot rely on any font that is not pre-installed on the user’s operating system. Your signature must use a stack of fallback fonts that work across Windows, macOS, iOS, Android, and Linux. The safest approach is to specify a primary font that is universally available, then chain fallbacks that cover every major platform.
The universal font stack that works
After testing signatures across Gmail (web and mobile), Outlook 2019, Outlook 365, Outlook for Mac, Apple Mail, Yahoo Mail, and ProtonMail, one stack consistently renders correctly:
font-family: Arial, Helvetica, sans-serif;
This is the baseline. Arial ships on every Windows machine, every Mac, every iOS device, and every Android device. Helvetica is the macOS native fallback. The generic sans-serif catches any edge case. This stack renders identically across all clients because it uses system fonts that are never blocked or substituted.
If you want a slightly more modern look, you can use:
font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif;
This stack prioritises the system font of each platform: San Francisco on Apple devices, Segoe UI on Windows, Roboto on Android. It looks native on every device. The downside: it is verbose, and some older Outlook versions may ignore -apple-system and BlinkMacSystemFont entirely, falling back to Segoe UI. That is fine—Segoe UI is still clean and readable.
What about serif or monospace?
Serif fonts like Georgia or Times New Roman are safe fallbacks, but they look dated in most modern signatures. Monospace fonts (Courier New, Consolas) are appropriate only for developer signatures or code snippets. For general business use, stick with sans-serif.
Fonts to avoid (and why they break)
Some fonts are tempting but will fail in at least one major client.
- Calibri: Default in Outlook 2007–2019 for email composition, but not installed on macOS or iOS. Apple Mail will fall back to Times New Roman, which looks terrible next to your logo.
- Verdana: Installed on Windows and macOS, but not on most Android devices. Android will fall back to Droid Sans or Roboto, which changes the spacing and line height.
- Tahoma: Similar to Verdana—Windows and macOS only. Missing on Linux and many Android builds.
- Georgia: Safe on desktop, but mobile clients often substitute it with a generic serif that looks heavier.
- Google Fonts (Open Sans, Roboto, Lato): These are not installed on any operating system by default. Gmail strips the
@importrule. Outlook ignores it. Apple Mail will load them only if remote content is enabled, and many users block remote images and fonts.
The rule: if the font is not installed on the device, it will not render. Do not rely on web fonts for email signatures.
Size, weight, and spacing: the hidden variables
Font choice is only half the battle. Even with a safe font stack, your signature can break due to size, weight, or line-height inconsistencies across clients.
Font size: Use px or pt units. Avoid em or rem because they inherit from the email client’s base font size, which varies wildly. A 12px font in Gmail web is readable. In Outlook desktop, 12px is tiny because Outlook defaults to 14pt. Compromise: use 13px or 14px for body text, and 11px or 12px for fine print (phone numbers, disclaimer). Test at both sizes.
Font weight: Most clients support font-weight: bold and normal. Avoid numeric weights like 400 or 700—some clients ignore them. Use the keyword values instead.
Line height: Set line-height: 1.4 or 1.5 explicitly. Without it, Outlook desktop collapses lines to single spacing. Apple Mail and Gmail use their own defaults, which can make your signature look cramped or stretched.
Letter spacing: Avoid letter-spacing entirely. Outlook desktop ignores it, and Gmail renders it inconsistently. If you need spacing for visual effect, use non-breaking spaces or a table cell with padding.
Dark mode: the final frontier
Dark mode inverts colours, but it also affects font rendering. Some clients (Outlook for Mac, Apple Mail) apply a colour inversion that can make light-coloured fonts unreadable on a dark background. Others (Gmail, Outlook web) only invert images and leave text alone.
The safest approach: use black or very dark grey text (#333333 or #222222). Avoid white or light grey text. If you must use a colour, test it in dark mode on at least Gmail (iOS and Android), Outlook for Mac, and Apple Mail. Do not use data-ogsc or data-ogsb hacks—they are unreliable and can break rendering in future client updates.
For your font stack in dark mode, the same system fonts work. No special dark-mode font is needed. Just ensure your text colour has sufficient contrast against both light and dark backgrounds.
How newmail.click handles this
newmail.click generates signatures that use the platform-specific font stack (-apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif) by default. You can override it with any combination of system-safe fonts in the editor. The free builder outputs inline CSS that survives Gmail, Outlook, and Apple Mail without stripping. Pro-tier subscribers get click and open tracking that works across all major clients—no font-related tracking failures because we never inject remote fonts. Slack and email alerts fire on engagement, and UTM defaults are appended to every link without breaking the signature’s layout. We do not offer team plans, SSO, or SCIM.
Your signature will render consistently on every device your recipient uses. No web fonts, no broken fallbacks, no dark-mode disasters. Just a clean, professional signature that works.