All articles

What Safari's new Adaptive Dark Mode could mean for Apple Mail

WebKit just announced Adaptive Dark Mode, which turns light pages dark in Safari 27.3 beta. Apple hasn't said it's coming to Mail, but the opt-out rules are the same ones your email code should already follow.

On November 3, 2026, the WebKit team announced Adaptive Dark Mode, a new Safari feature that takes light websites and presents them as dark. It's available now in Safari 27.3 beta. When a user turns it on, WebKit analyses each page and transforms the colours: light backgrounds go dark, dark text goes light.

The announcement is about Safari and websites. It doesn't mention Mail or email at all. But WebKit is the engine Apple Mail uses to render HTML, so this is the kind of change I keep an eye on. Nothing here is confirmed for Apple Mail yet. What's useful today is that WebKit has spelled out exactly which pages it leaves alone, and those rules line up with how I already recommend coding dark mode for email.

What Adaptive Dark Mode does

According to the WebKit post:

  • Pages that declare support for both schemes (light dark) are left unchanged.
  • Pages that already have a dark background and light text are left unchanged.
  • Pages with a light appearance get adapted to dark.
  • Text is adjusted to aim for a WCAG contrast ratio of 4.5:1.
  • SVG colours are transformed when needed, and simple black-and-white bitmap logos may be inverted.
  • Masks and mix-blend-mode may be switched off on transformed elements.
  • Sites can't detect when it's applied. JavaScript that reads CSS colours gets the original authored colours.

That last point matters for email too. Even if a client never exposes this, you can't rely on detecting it. You can only declare what your design supports.

The opt-in and opt-out rules

WebKit lists two ways to tell it your page already handles dark mode:

<meta name="color-scheme" content="light dark">
:root {
  color-scheme: light dark;
}

And two ways to opt out and keep a page light:

<meta name="color-scheme" content="light only">
:root {
  color-scheme: light only;
}

One catch: WebKit says the only keyword isn't supported in Safari 27.3 beta 1. So for now, "light only" doesn't work in the very build that introduces the feature. I'd expect that to change before release, but I wouldn't build a plan around it until it does.

WebKit also recommends declaring the colour scheme in the HTML head and/or on :root or body, rather than injecting it later with JavaScript. In email you don't have JavaScript anyway, so the head is where this belongs.

What I'd do in email code right now

If you already follow a solid dark mode setup, you probably don't need to change anything. If you don't, this is a good prompt to fix it, because the same declarations help in Apple Mail today and in Gmail's apps, which now honour light only too.

A typical head setup I use:

<meta name="color-scheme" content="light dark">
<meta name="supported-color-schemes" content="light dark">
<style>
  :root {
    color-scheme: light dark;
    supported-color-schemes: light dark;
  }
  @media (prefers-color-scheme: dark) {
    .bg-body { background-color: #121212 !important; }
    .text-body { color: #f2f2f2 !important; }
  }
</style>

The point is to declare light dark and then actually supply the dark styles. Declaring support without designing for it just hands the reader a light email with no adjustments.

Where automatic transforms hurt

Whether it's Safari's new feature, Gmail's forced dark mode or Outlook's colour inversion, automatic transforms tend to break the same things:

  • Logos. WebKit says simple black-and-white bitmap logos may be inverted. A black wordmark on a transparent PNG is exactly the asset that goes wrong. Add a subtle outline or light padding, or swap in a dark-mode version.
  • Brand colours. A transform aims for readability, not for your brand palette. If colour accuracy matters, own the dark styles yourself.
  • Blend effects. If your design relies on mix-blend-mode or masks, WebKit may switch them off on transformed elements. Test anything decorative.
  • Contrast. Aiming for 4.5:1 is good for accessibility, but it may shift your colours more than you'd like. Check contrast yourself first so the transform has less to fix.

What agencies and brands should do

  1. Audit your templates for a color-scheme declaration in the head. If it's missing, add it.
  2. Decide per brand: support light dark properly, or choose light only and accept that not every client honours it.
  3. Make sure logos work on both light and dark backgrounds.
  4. Keep an eye on Apple's release notes for Mail. If Adaptive Dark Mode reaches Mail, emails without a declaration are the ones that will change.

I'll update this post if Apple confirms anything for Mail.

Related on the Journal

If you want a second pair of eyes on how your templates hold up in dark mode, try the free dark mode tester or get in touch for a dark mode and QA review.

Sources

Work with me

Need this handled in your templates?

Send me your design file or the HTML that's misbehaving. You'll get a clear scope, timeline and quote within 1 business day.