Safari Adaptive Dark Mode: How Safari 27.3 Beta Works

Apple's WebKit team introduced Safari Adaptive Dark Mode in the Safari 27.3 beta, a feature that automatically darkens light websites without the site needing to build its own dark theme, according to WebKit's announcement two days ago. It only works once a user turns it on, and it requires the device's system appearance to already be set to Dark. WebKit's announcement does not provide a stable-release date, and it doesn't specify a full list of supported devices or operating systems, so anyone outside the beta has nothing to test yet.

Almost 40% of web page loads come from users already browsing in dark mode, but only about 10% of sites actually support it, according to WebKit. Adaptive Dark Mode is Apple's attempt to close that gap at the browser level instead of waiting on individual developers to catch up.

MacStories also covered the feature yesterday as part of the broader 27.3 beta rollout, noting that Safari 12.1 was the first browser to support dark mode on the web back in 2019.

How Safari Adaptive Dark Mode works

Safari scans each page's colors and estimates whether it reads as predominantly light or dark (WebKit, two days ago). Dark-themed pages, dark background with light text, are left alone. Pages that read as light get transformed.

This isn't a blanket color inversion that flips every pixel. WebKit built a dedicated color matrix that inverts luminosity while preserving hue, so light backgrounds turn dark and dark text turns light without scrambling every color on the page (WebKit, two days ago).

WebKit says it aims for sufficient contrast as defined by the WCAG 4.5:1 ratio when transforming text, and light CSS gradients get darkened right alongside solid backgrounds (WebKit, two days ago). That's WebKit's own target; the announcement doesn't include independent contrast audits confirming how consistently it holds up across a wide range of live sites.

Apple frames this as an engine-level feature, WebKit Adaptive Dark Mode, built directly into the browser rather than bolted on through an extension. Because the transformation happens inside WebKit itself, the company says it can apply more creative fixes while running faster and more power-efficiently (WebKit, two days ago). That's Apple's own characterization; the announcement includes no third-party benchmarks to verify the speed or power claims.

How to turn on Safari Adaptive Dark Mode right now

To try it, turn on Safari 27.3 beta and set the system appearance to Dark. Safari won't offer the feature otherwise (WebKit, two days ago).

With Dark mode active, Safari shows a preview of Adaptive Dark Mode on a qualifying page and offers a "Try" option to switch it on (WebKit, two days ago). Sites that already declare support for both light and dark appearance are handled differently: WebKit says Adaptive Dark Mode "does not change a thing" on those pages (WebKit, two days ago), though the announcement doesn't say whether the preview prompt still appears on them. Testing smaller sites that haven't built a dark theme, local business pages, older blogs, simple storefronts, makes the effect easier to spot than testing a site that already supports dark mode.

If a page renders poorly once the feature kicks in, WebKit invites beta testers to file a report through Feedback Assistant (WebKit, two days ago).

Where Safari's dark mode for websites still struggles

Images mostly stay untouched, which WebKit says preserves their visual integrity (WebKit, two days ago). Logos and icons are a known trouble spot, since inverting the background behind them can wreck their contrast. Safari inspects SVG icons and logos individually and adjusts their colors when needed, and for bitmap images it reads the pixel histogram to invert simple black-and-white logos (WebKit, two days ago).

Some effects don't survive the transformation. Masks and mix-blend-mode can look broken once their underlying colors shift, so Safari may turn those effects off rather than render them incorrectly (WebKit, two days ago). Canvas content is left alone entirely, since WebKit says canvases can hold a wide range of content that's hard to predict (WebKit, two days ago).

WebKit identifies canvas, masks, and mix-blend-mode as cases that may not transform cleanly, which points toward more inconsistent results on image-heavy sites, complex web apps, or anything leaning on canvas-rendered interfaces. The announcement describes the goal as "a consistent dark experience across the web" (WebKit, two days ago), but the mechanics it lays out don't guarantee that outcome on every page. WebKit says it aims to preserve contrast for buttons, text over images, and hover menus (WebKit, two days ago), though that's a stated design goal rather than a tested guarantee across the web.

Developer opt-outs and privacy in Safari's dark mode

Developers who don't want Safari to force dark mode on their site have a way to opt out. Declaring color-scheme: light dark in CSS, or the matching HTML meta tag, tells Safari the site already supplies its own light and dark styling, and Adaptive Dark Mode skips that page entirely (WebKit, two days ago).

That's a separate mechanism from forcing a page to stay light regardless of the system setting, which uses a color-scheme: light only CSS rule or matching HTML meta tag (WebKit, two days ago). WebKit says the only keyword isn't supported in Safari 27.3 beta 1, so developers can't rely on a light-only declaration in this build. Whether later beta builds will support the light-only opt-out isn't stated.

Apple's broader recommendation is to build genuine dark mode support instead of leaning on the automatic pass, declaring color-scheme early in HTML or CSS rather than injecting it later with JavaScript, which helps pages render correctly as fast as possible (WebKit, two days ago). WebKit also lists a handful of smaller fixes for sites still using older techniques: swapping bitmap logos for SVG, using CSS gradients instead of tiled background images, and adding padding so transformed elements don't crowd together (WebKit, two days ago).

On privacy, Apple says Safari blocks websites from detecting whether Adaptive Dark Mode is active, arguing that letting sites detect it would hand trackers another fingerprinting signal (WebKit, two days ago). JavaScript that queries a page's CSS colors gets back the original authored colors rather than the transformed ones, and canvas images render in their original form regardless of the setting (WebKit, two days ago). That's Apple's own description of its design; the announcement includes no independent testing against outside detection or fingerprinting techniques, so it's worth treating as a claim rather than a verified guarantee.

What to do now

Adaptive Dark Mode works today, but only inside Safari 27.3 beta, only after turning on Dark system appearance, and only on sites that haven't already declared their own dark-mode support (WebKit, two days ago). Still open: a stable-release date, how consistently the contrast and color transformations hold up across a wide range of live sites, and whether a future beta adds the light-only opt-out for developers.

Anyone already running Safari 27.3 beta should test it on a handful of everyday sites, news pages, shopping sites, smaller blogs without a built-in dark theme, and watch for logos that lose contrast, effects that get disabled, or canvas content that doesn't change. Readers outside the Safari 27.3 beta can't try the feature based on the availability WebKit has described. Wait for a stable release before counting on it for daily browsing.