A Google Chrome Dark Mode Extension: What It Changes per Site

Chrome's own dark setting covers the toolbar and the settings pages, and stops at the edge of the page. Google states the scope plainly: the homepage, toolbar, settings and some other pages go dark. Site content is the site's decision. That gap is the entire market for a Google Chrome dark mode extension, and the extensions in it differ far more than their store listings suggest. The important differences are what happens per site, what access the extension asks for, and what it costs after the trial.

Three different mechanisms behind one category name

The store lists dozens of items under the same description. They work in three distinct ways.

Dynamic inversion. The extension reads the colors a page declares and remaps them as the page renders, so an unfamiliar site comes out dark on first visit with no configuration. This covers the whole web and guesses on every page. Dark Reader is the best known example of this approach.

Curated per site themes. The extension ships hand written stylesheets for specific sites and applies nothing elsewhere. Results on covered sites are much better than any guess, because a person chose every color, and sites outside the list stay light. DocsAfterDark works this way, targeting the Google Docs interface specifically and reporting over 120,000 users.

Filters and dimming. The extension lays a filter over the page, reducing brightness or shifting color temperature without trying to understand the layout. This never breaks a page and never produces a real dark theme either. Useful at night, not a substitute for the first two.

Knowing which of the three is installed explains most complaints about dark mode extensions. A dynamic inverter looks broken on a complex web app because it is guessing. A curated theme looks inert on most of the web because it was never meant to cover it. A filter makes everything grey because that is all it does.

What per site control actually looks like

The phrase "works on every site" in a listing is a promise about coverage, not about control. Control is the feature that decides whether an extension is usable for work, and it comes in a few specific forms worth checking before installing.

A per site off switch is the minimum. One click disables the extension on the current domain and remembers it, so the one spreadsheet whose colors matter can be exempted permanently while everything else stays dark.

An allowlist mode reverses the default. Rather than darkening everything and exempting failures, the extension stays off until a site is explicitly added. For anyone who works in five web apps and browses widely, this is the mode that produces the fewest surprises.

Per site tuning is the next level: brightness, contrast, sepia and grayscale saved separately for each domain. This is what rescues sites that come out almost right, where the text is legible but the panels are too close to the background.

A keyboard shortcut to toggle the current tab matters more than it sounds. Comparing a rendering against the real page is a routine need when something looks wrong, and a shortcut makes it a keystroke instead of a trip to the toolbar.

Finally there is behavior on sites that are already dark. Better extensions detect an existing dark theme and leave it alone rather than darkening it twice, which is the difference between an interface that looks designed and one that looks washed out.

The permission, stated plainly

An extension that changes how pages look must be able to read and modify page content. In Chrome's own wording that appears as permission to read and change data on the sites visited, and it is a real grant rather than a formality. The same access that rewrites a background color can read a form field.

This does not make the category unsafe. It makes the publisher the thing being evaluated rather than the feature.

Three checks are quick and worth doing. The listing's Privacy section states what the developer has declared about data collection, and for Dark Reader it declares that no data is collected or used. The listing also shows the version, the last update date and the size, which for Dark Reader currently reads version 4.9.133, updated September 25, 2026, at 831 KiB, and a listing that has not been updated in a long time in a category this dependent on browser behavior is worth noticing. Source code availability is the third check: Dark Reader is published under the MIT license with a public repository dating back to 2014, which means the code can be inspected rather than trusted on reputation.

The counterweight is scale. The Dark Reader listing shows 7,000,000 users and a rating of 4.7 from 13.2K ratings, in the Accessibility category. Popularity is not an audit, but an extension with that footprint attracts scrutiny that an obscure one does not.

What the options cost

Pricing in this category ranges from free and open source to a one time purchase, and the free tiers are limited in ways that are easy to miss until a second machine appears.

Option	Price	Free tier limits	Coverage
Dark Reader (Chrome, Firefox, Edge)	Free, MIT licensed, donation supported	None, the extension is fully functional	Dynamic, any site
Dark Reader for Safari	$4.99 on the Mac App Store	Not applicable, paid app	Dynamic, any site
Night Eye Lite	Free	One browser, 5 website slots	Dynamic, limited to chosen sites
Night Eye Pro	$9 per year	Three browsers, unlimited sites	Dynamic, any site
Night Eye Pro Max	$14 per year	Six browsers, unlimited sites	Dynamic, any site
Night Eye Ultimate	$40 one time	Ten browsers, unlimited sites	Dynamic, any site
DocsAfterDark	Free	Not applicable	Google Docs interface only
Chromium auto dark flag	Free, built in	No per site control at all	All page content

Prices come from each product's own pricing page as published at the time of writing. The paid tiers are unusual in a free heavy category, and what they buy is mostly device count and support rather than a better rendering.

The last row belongs in the table because it is the option most people have not tried. Chrome carries an internal switch at chrome://flags, listed as Auto Dark Mode for Web Contents, that darkens page content without any extension. Google's help pages state that flags are temporary, can be removed without notice, and are not settings. It costs no permissions, offers no exceptions, and is worth a five minute test before installing anything.

Where every extension in this category struggles

Some surfaces are outside what a color rewriting extension can reach, and knowing the list prevents blaming the wrong tool.

Canvas and WebGL interfaces. Anything drawn rather than laid out, including design tools, diagram editors, maps and most charting libraries, arrives as pixels. An extension either leaves it alone or inverts it wholesale, and neither is what the reader wanted.

Documents that will be shared. A darkened document editor shows a dark page that exists only locally. What collaborators see, and what a PDF export contains, is unchanged. Screenshots taken in that state confuse everyone who receives them.

Color as information. Conditional formatting, status badges, diff views, tags assigned per client, anything where hue carries meaning. Remapping a palette destroys that meaning even when the result looks good.

PDFs in the built in viewer. Chrome's PDF viewer is not an ordinary page, and most extensions cannot touch it.

Heavy web apps. On a mail client or a project tool that rewrites large parts of the page continuously, a dynamic inverter has to keep up with every change, and the cost shows as a visible flash of light content before the dark rendering catches up.

Per site exemptions handle most of these, which is why the control features in the second section matter more than the rendering quality advertised in the first screenshot of any listing.

A short test that settles the choice

Reading listings does not distinguish these options, because every listing shows a well behaved article page rendered correctly. The differences appear on the sites that pay the bills, so the test should use those.

Pick the five services that occupy most of the day. Mail, whichever chat tool the team uses, the document editor, the tracker or dashboard, and the one internal tool that only the company runs. Open each in a tab and leave them open.

Run the built in flag first, since it costs nothing to try and nothing to remove. Note which of the five come out acceptable and which do not.

Install one extension and repeat, then look for four specific things rather than an overall impression. Whether secondary text stays legible, since faded grey on dark grey is the first thing to fail. Whether any color that carried meaning changed, particularly status colors and anything highlighted in a spreadsheet. Whether the interface flashes light before turning dark on the app that updates most often. Whether turning the extension off for one site takes one click and stays off after a restart.

Then check the count that decides the price. Free tiers in this category are limited by browser or device rather than by features, so a person with a work profile, a personal profile and a laptop at home is already past the limit of a one browser tier.

Half an hour covers all of it, and the result is specific to the sites that matter rather than to a reviewer's browsing habits. The most common outcome is that two or three of the five already have a native dark theme, one needs an extension, and the rest were never the problem.

The alternative that needs no guessing

Every extension in this category exists to guess a palette the site's own designers never wrote. For the handful of services that carry most of a working day, that guess is unnecessary, because those services usually ship a dark theme of their own. Gmail has one under Settings, in the Theme section. Google Drive on the web now offers Light, Dark and Device default under Settings, in the Appearance section. Many web apps switch automatically by reading the operating system preference through the prefers-color-scheme media query.

The obstacle is structural rather than technical. Tabs make apps interchangeable, so appearance ends up being set once for all of them. Treating each service as its own window puts the decision back where the answer differs: mail dark, the design tool in the colors its makers intended, the spreadsheet untouched. A browser that keeps each web app in its own window makes that the default arrangement, and organising those windows into workspaces keeps an evening reading setup distinct from a daytime working one. Checking whether a given service has a native dark theme against the list of supported apps takes less time than testing three extensions against it.

An extension remains the right answer for the long tail: an old internal tool, a documentation site from 2014, a vendor portal nobody will ever restyle. Keep it for those, with an allowlist rather than a blanket rule.

What to change first

Before installing anything, turn on the native dark theme in the three web apps used most and test Chrome's built in flag against whatever is left. If an extension is still needed, choose one with per site rules and an inspectable codebase, and run it in allowlist mode rather than everywhere. For the apps that matter every day, SpaceDeck makes the per app setting the normal case instead of an exception.