Safari 27.3 Beta Adds Adaptive Dark Mode, Which WebKit Says Darkens Light Pages for Users Who Enable It and Skips Pages Declaring Dark-Mode Support
WebKit says Safari 27.3 beta's Adaptive Dark Mode darkens light pages for users who enable it but leaves alone pages that declare dark-mode support; the opt-out keyword it names is unsupported in beta 1.
Overview
Safari 27.3 beta includes Adaptive Dark Mode, which WebKit’s announcement, dated November 3, 2026, describes this way: “When enabled by a user, Safari adapts light websites and presents them as dark.” Pages that already signal dark-mode support are left unchanged, according to the same post. Apple’s Safari 27.3 beta release notes list the feature in their Rendering section under New Features. The WebKit post also carries a note that the keyword it recommends for opting out is not supported in the first beta.
What WebKit says the feature does
WebKit’s post says that for pages that signal dark-mode support with <meta name="color-scheme" content="light dark"> in HTML or color-scheme: light dark in CSS, Adaptive Dark Mode “does not change a thing”. For other pages it analyzes the page’s colors and estimates whether the page is predominantly light or dark; a page with a generally dark background and light text is not changed, while a light page is adapted. The same post gives these details:
- Color handling. WebKit says it developed a color matrix that inverts the luminosity of colors while preserving hue, that text color is transformed with the aim of sufficient contrast as defined by the WCAG 4.5:1 contrast ratio, and that light CSS gradients are also transformed to dark.
- Images. Most images are left unchanged. Safari inspects SVG images and transforms colors when needed; for bitmap images it analyzes pixel histograms and inverts simple black-and-white logos.
<canvas>content is left unchanged, and in some cases effects such as masks andmix-blend-modeare turned off. - Privacy. WebKit says Safari prevents websites from detecting when Adaptive Dark Mode has been applied: JavaScript that queries CSS colors receives the original authored colors, and images drawn into a canvas render in their original form.
WebKit gives its own figures for the motivation: “Almost 40% of web page loads are from users in dark mode, and yet only 10% of page loads support it.” These are WebKit’s statistics, and the post does not say how they were measured.
What site authors are told to do
The post’s advice is to declare dark-mode support with the color-scheme meta tag in the HTML head and/or the color-scheme property on :root or body, and not to inject that declaration later with JavaScript. For part of a page, authors can apply color-scheme: light dark to an element and add their own dark styles.
To keep a page from being transformed, WebKit says to use <meta name="color-scheme" content="light only"> or the CSS rule color-scheme: light only. The post adds, in a parenthetical note, that the only keyword is not supported in Safari 27.3 beta 1 and that readers should check back as the feature evolves through the beta process.
The Mozilla Developer Network’s color-scheme reference describes only as forbidding the user agent from overriding the color scheme for the element, and says it can be used to turn off color overrides caused by Chrome’s Auto Dark Theme. MDN’s examples write the keyword as only light, while WebKit’s post writes light only. MDN’s formal syntax lists only? joined to the scheme list with &&, which the Herald reads as allowing either order, though neither MDN nor WebKit says so in words.
How other outlets describe it
9to5Mac reported on November 3 that when Dark Mode is enabled and a visited site does not support it, Safari shows a “Try” button, and that users can have Adaptive Dark Mode kick in automatically or use it site by site. MacRumors says that after a user taps Try, Safari makes the background darker, changes text contrast, inverts logos and graphics, recolors vector artwork, lifts raised surfaces and rebalances layered shadows, and that not every adjustment is applied to every site. MacRumors adds that “Developers can also add a tag that causes Safari to ignore Adaptive Dark Mode and show the website as the developer intended.”
TechRadar says that for developers “there are new tags they can use that will prevent Adaptive Dark Mode from adjusting them.” Neither MacRumors nor TechRadar names the tag, and WebKit’s post says the keyword it names for opting out is unsupported in beta 1.
Timing and open questions
TechRadar wrote on November 3 that the updates were found only in the developer betas. On November 5, 9to5Mac reported that Apple had released the first iOS 27.3 public beta for iPhone, listing Adaptive Dark Mode among its Safari changes. On release timing, MacRumors says the 27.3 releases “will launch this December after several rounds of beta testing”, 9to5Mac’s November 3 article says the update “will likely be released to everyone sometime in December”, and TechRadar says “There’s no word on when the full releases will arrive”.
Apple’s release notes state that Safari 27.3 beta is available for iOS 27.3 beta, iPadOS 27.3 beta, visionOS 27.3 beta, macOS 27.3 beta, macOS 26 and macOS Sequoia. The three press articles name the iOS, iPadOS and macOS 27.3 betas. None of the cited sources says whether the only keyword will be supported in a later beta or the final release, or what a page that uses it sees in the meantime.