Email Client Dark Mode Support Matrix
A technical comparison of how major email clients handle dark mode, colour inversion, authored CSS and MailMode preview modes.
Apple Mail default / Gmail Web
Client UI can be dark while rich HTML email is largely left as authored.
Apple Mail first
Samsung Email and Thunderbird can support authored dark CSS in some contexts, but version, platform and account setup matter.
Outlook.com / Gmail Android
Selective transformations can rewrite some colours, backgrounds, text and borders.
Gmail iOS / classic Outlook
Aggressive forced dark behaviour can break already-dark designs, logos and CTAs.
This is an independent MailMode reference, not official documentation from any email client provider. Dark mode behaviour can change by client version, app, OS, account type and rendering engine.
Client labels are behaviour families, not exact emulators
Dark app shell, light message
Rich HTML is largely left unchanged even when the surrounding client UI is dark.
Sender-controlled dark state
The client can respect dark CSS such as prefers-color-scheme when support is declared and tested.
Selective colour rewriting
The client changes some text, backgrounds, borders or attributes while preserving other areas.
Aggressive forced dark
The client aggressively transforms the email and can break already-dark designs.
Behaviour varies
Platform, version, account type and rendering engine can change the final result.
The practical dark mode map
Strongest authored CSS target
Apple Mail is generally the clearest place to use color-scheme, supported-color-schemes and prefers-color-scheme.
Usually no-change for rich HTML
Gmail Web often darkens the app shell while leaving rich HTML largely unchanged; CSS support does not mean dark-mode control.
High-risk full invert
Already-dark panels, white logos and pale text can be aggressively transformed.
Chromium-style darkening
It is usually closer to algorithmic partial inversion than Gmail iOS full invert, and needs Android-specific Gmail checks.
Full invert plus MSO/VML risk
Classic Outlook is still the Word-engine client; keep it separate from new Outlook, web Outlook and mobile Outlook.
Partial invert with data attributes
data-ogsc and data-ogsb are useful Outlook.com-style targeting hooks; prefers-color-scheme is not the main control surface.
Separate test target
Public evidence points toward web/PWA-style behaviour, but not exact parity with Outlook.com or classic Outlook.
Major email client dark mode behaviour
Matrix notes are based on public email-client documentation, Can I Email feature tables, WebKit, Gmail and Microsoft references, and email developer testing sources. Behaviour can vary by app version, account type and platform.
prefers-color-scheme + color-schemeHigh controlAuthored CSS / no changeMail uses scheme declarations as a signal; test macOS separately.Apple Mailprefers-color-scheme + color-schemeHigh controlAuthored CSSTest device layouts.Apple Mailprefers-color-scheme + color-schemeHigh controlAuthored CSSTreat as iOS-like, but test tablet layouts and device bugs.Apple Mailprefers-color-scheme dark toggle.Gmaildiv > u + .body / defensive CSSMixed controlPartial InvertChromium-style darkening; materially different from Gmail iOS.Gmail[data-ogsc] / [data-ogsb]Medium controlPartial InvertCan prefix classes and rewrite colours inline with !important.Outlookprefers-color-scheme where supported; scheme hints may helpMixed controlAuthored CSS / partial fallbackAccount type, app version and provider can matter, especially Microsoft accounts.CSSprefers-color-scheme where supportedMixed controlAuthored CSS / test requiredDesktop settings, app version and Android forced-dark behaviour can diverge.CSSWhich MailMode mode to check first
Baseline clients
Gmail Web and Apple Mail rich HTML baseline without authored dark CSS.
Sender-designed dark state
Apple Mail first, plus Samsung Email and Thunderbird only when the target environment honours authored dark CSS.
Selective client transforms
Gmail Android, GANGA, Outlook.com, Outlook mobile, Outlook Mac, likely new Outlook paths and unknown Yahoo/Samsung fallbacks.
Worst-case forced dark
Gmail iOS and classic Outlook Windows.
Variable families
Yahoo Mail, Thunderbird, Samsung Email and new Outlook should be checked against target versions.
Dark mode techniques by client family
Technique support describes practical email-development reliability, not just raw CSS support. Some clients support a CSS feature but still transform colours in dark mode.
@media (prefers-color-scheme: dark)Good target authored dark CSSApple Mail first; selected Samsung Email and Thunderbird contextsGmail, Yahoo, classic OutlookSelected clients only; Gmail does not provide a reliable dark-mode media-query path.CSScolor-scheme meta / root CSSDeclare light and dark supportApple / WebKit-style clients; selected Samsung Email pathsGmail, most Outlook surfaces, YahooApple-first signal, not a global switch.Apple Mailsupported-color-schemes metaLegacy Apple compatibilityOlder Apple / WebKit / Mail pathsMost non-Apple clientsUseful alongside color-scheme, but not a Gmail or Outlook control.Apple Mail<style> blocksClient-specific patchesApple, Gmail accounts, Outlook.comGANGA, body styles in Gmail, sanitised contextsSupport is not dark mode control; Gmail has style placement and size caveats.CSS!importantProtect authored rulesAuthored CSS pathsForced transforms, Outlook.com rewritesOutlook.com can mutate colours inline with !important.CSSdisplay:none / max-heightImage swapsApple, Gmail, Yahoo, Samsung and many modern clientsClassic Outlook caveatsdisplay:none has classic Outlook inheritance bugs; pair with max-height.Apple MailbgcolorTable-cell resilienceBroad light-mode fallbackOutlook.com, Outlook family, Gmail mobile forced-dark casesBaseline resilience, not a dark-mode lock.CSSmix-blend-modeTargeted Gmail iOS contrast fixesGmail account paths where supportedGANGA, Outlook, YahooNot broad support.Gmailu + .body / div > u + .bodyGmail targetingGmail accountsGANGA and non-Gmail clientsGmail-only pattern.Gmail[data-ogsc] / [data-ogsb]Outlook.com dark patchesOutlook.com / OWAApple, Gmail, classic Outlook; not proven across every Outlook appDo not assume identical reliability across Outlook mobile apps.OutlookGroup behaviour before choosing fixes
High developer control
Best authored dark CSS target, especially when scheme declarations are intentional. Start with the Apple Mail guide and Dark Mode CSS guide.
Split Web, iOS, Android and GANGA
Web is no-change, iOS is full invert, Android is Chromium-style partial darkening, and GANGA has reduced CSS. See the Gmail guide.
Do not treat Outlook as one client
Classic Windows, Outlook.com, new Outlook, Mac and mobile need different assumptions. Keep data-og patches separate from MSO/VML fallbacks.
Yahoo, Samsung and Thunderbird vary
Yahoo differs by platform, Samsung Email can depend on account type and app version, and Thunderbird desktop should not be treated as identical to Thunderbird Android.
Assumptions that break dark mode emails
Treating prefers-color-scheme as universal
Affected: Gmail, Yahoo, Outlook Windows. Safer: pair standards CSS with client-specific fallbacks.
Assuming Gmail Web and mobile match
Affected: Gmail family. Safer: test Web, iOS, Android and GANGA separately.
Assuming iOS and Android match
Affected: Gmail apps. Safer: treat iOS as full-invert risk and Android as partial-invert risk.
Assuming Outlook.com and classic Outlook match
Affected: Outlook family. Safer: separate data-og patches from MSO/VML fallbacks.
Assuming new Outlook equals classic Outlook
Affected: Windows Outlook. Safer: treat new Outlook as a separate test target.
Assuming CSS support equals dark mode control
Affected: Gmail and Yahoo. Safer: separate feature support from forced-dark behaviour.
Using one logo for every background
Affected: forced and partial dark clients. Safer: use backing surfaces, outlines or dark-specific assets.
Relying entirely on CSS variables
Affected: mixed-support clients. Safer: include literal fallback colours.
Using VML outside classic Outlook assumptions
Affected: new Outlook, web, mobile. Safer: keep VML for classic Outlook Windows only.
Treating Yahoo, Samsung or Thunderbird as fixed
Affected: mixed-client audiences. Safer: split platforms and account types where they matter.
Treating bgcolor as a dark-mode lock
Affected: Outlook.com, Outlook family, Gmail mobile. Safer: use it for baseline fallback, then test forced-dark rewrites.
Assuming !important wins
Affected: Outlook.com and OWA. Safer: expect inline colour mutation and verify data-og targeting.
Where the matrix needs careful interpretation
- New Outlook for Windows is a separate test target, not classic Outlook with a new skin.
- Yahoo Mail should ideally be split by web, iOS and Android when that audience is important.
- Thunderbird should ideally be split by desktop, Android and version where that audience matters.
- Samsung Email can support authored dark CSS in some contexts, but behaviour can vary by account type, app version and provider.
- Feature-support data and forced-dark behaviour are different kinds of evidence.
- Gmail can support useful CSS properties while still lacking a reliable dark-mode media-query control.
- Outlook.com can offer rich HTML/CSS support while still rewriting colours inline.
- Client behaviour changes over time, so this matrix should be periodically reviewed.
How this supports MailMode previews
MailMode is not an exact emulator for every email client. Its preview modes are practical approximations that help expose common dark mode risk families before real-client testing.
No-change checks help with Gmail Web and rich HTML Apple Mail baselines. Authored CSS helps with Apple Mail-style dark CSS, and with Samsung Email or Thunderbird only when the target environment is known to honour authored dark styles.
Partial Invert helps approximate Gmail Android, GANGA, Outlook.com/OWA, Outlook Mac, Outlook mobile, likely new Outlook paths, and unknown Yahoo/Samsung fallbacks. Full Invert helps expose Gmail iOS and classic Outlook Windows-style worst cases.
Sources & Further Reading
Last Updated: Sources Reviewed: