Dark Reader as a browser extension: reading at night on a Mac

The Dark Reader browser extension is usually installed once, left in its default state, and then judged on whether a handful of sites come out looking right. That is an unfair test of it, because almost every complaint about the extension traces back to one of two settings that were never touched: the rendering mode and the site list. On a Mac there is a third variable, which is that the Chrome, Firefox, Edge and Safari versions are not the same product and do not cost the same.

Four rendering modes, not one

The extension generates a dark theme in four different ways, chosen under the More tab. The official help documents what each one does, and the differences are large enough that changing the mode fixes most rendering failures.

Dynamic is the default. The documentation describes it as deeply analysing website style sheets, background images and vector graphics. It requires some resources on initial page load and produces the best visual results. This is the mode that makes an unfamiliar site come out correctly without configuration, and also the mode that costs a moment of work every time a page loads.

Filter is based on CSS filters. It inverts the whole page and reverts some parts back, using GPU resources. The help lists its problems without softening them: it disables text sub-pixel rendering, inverts already dark parts into light, causes lags on large pages, and fails to render some pages in Firefox.

Filter+ is the same approach built on custom SVG filters, which handles colors better and makes images less dull. The documentation notes that it works poorly in Firefox.

Static rapidly generates a basic stylesheet. It is the cheapest of the four and the least faithful.

The practical reading of that list is that Dynamic should stay as the global default, and Filter or Filter+ is a per site rescue for a page Dynamic mishandles. A page where photographs look washed out is a candidate for Filter+. A page that lags while scrolling is a candidate for leaving Dynamic in place and excluding the site instead.

The site list is the setting that decides whether it suits work

Coverage is what the listing advertises. Control is what determines whether the extension survives a working week, and it lives in two places.

The Site list tab has two mutually exclusive positions. Not invert listed is the default posture: darken everything, and skip the domains on the list. Invert listed only reverses it, so the extension does nothing until a site is explicitly added. For anyone who works in five web apps and browses widely, the second position produces far fewer surprises, because a spreadsheet whose colors carry meaning is never touched by accident.

The patterns accepted are more precise than a domain field suggests. The documentation gives google.com, mail.google.com, google.* and google.com/maps as valid values, and states that regular expressions are supported when written between slashes, as in /www\.google\..*/. A path level pattern matters in practice, because one section of an internal tool can be excluded without losing the rest of it.

Separately, the Only for button in the popup scopes the brightness, contrast, sepia and grayscale sliders to the current website. Clicking it, then adjusting, then clicking it again saves a per site profile. This is what rescues the pages that come out almost right, where the text is legible but the panels sit too close to the background.

The Toggle site button at the top of the popup adds the current site to the list, or removes it. When that button is greyed out, the help explains that the browser is restricting script injection on the current page, which is a browser restriction rather than a fault in the extension.

Four browsers, four different deals

The name is the same everywhere. The price, the maintainer's reach and the feature depth are not.

Version	Price	Audience shown on the listing	Notes
Chrome	Free	7,000,000 users, 4.7 from 13.2K ratings	Version 4.9.133, updated September 25, 2026, 831KiB, 39 languages
Firefox	Free	1,338,395 users, 4.5 from 6,946 reviews	Carries the Recommended badge, also available for Firefox on Android
Edge	Free	Listed in the Edge Add-ons store	Built in page darkening conflicts with it, see below
Safari	$4.99 on the App Store	282 ratings, 4.3 average	One purchase covers macOS and iOS on the same iCloud account

Two things follow from that table. The first is that the free versions are the same open source project, published under a public repository and developed since 2014, while the Safari version is a paid app sold through Apple's store. The Safari listing states that a single purchase includes access to the macOS version when using the same iCloud account, so the $4.99 covers the iPhone, the iPad and the Mac together rather than each separately.

The second is that the Safari build is not simply the Chrome build recompiled. Reviewers on the App Store note that it offers a narrower set of options than the desktop extensions, which is a consequence of how Safari structures extensions rather than a decision about features. Anyone choosing between Safari and a Chromium browser specifically for reading at night is choosing between the deeper configuration and the browser they prefer to use.

Edge deserves one specific warning. Edge ships its own setting for darkening all web pages, and the extension's own help tells Edge users to open the menu, then Settings, then Appearance, then the dark theme for all web pages option, and disable it if it is on. Two systems inverting the same page is the fastest way to produce a grey, low contrast result and blame the extension for it.

The permission, and what the publisher has declared

An extension that repaints pages must be able to read and modify page content. On the Firefox listing the required permissions are stated as access to browser tabs and access to data for all websites. That is a real grant, not a formality, since the same access that rewrites a background color can read a form field.

Three checks are quick. The Chrome Web Store listing's privacy section states that the developer has disclosed that it will not collect or use data, and the extension's own help repeats that it inserts no ads and collects no data. The listing identifies the publisher as Dark Reader Ltd, with a London address, a D-U-N-S number and a declaration as a trader under European Union rules, which is more identifying information than most extensions carry. And the source is public, so the code can be inspected rather than trusted on reputation.

Scale is a weak signal that still counts for something. A listing with 7,000,000 users in the Accessibility category attracts scrutiny that an obscure one does not, and the version history shows continuous maintenance rather than a project abandoned two browser releases ago.

What it will not darken

Several complaints are not faults and cannot be fixed by changing settings, because the extension has no access to the pages in question.

The extension store pages and the browser's own settings pages stay light. The help states the reason directly: the extension has no access to these pages.

The new tab page and the browser interface stay light until the browser's own theme is set to dark. That is a browser setting, not an extension setting, and on macOS following the system appearance is usually enough.

A white flash when opening a new tab or navigating is caused by the browser painting its theme background color before the page loads. Setting a dark browser theme removes it. On a Mac with the system in dark appearance this is often already handled.

Private windows need explicit permission. On a Chromium browser, the extensions page has an Allow in incognito switch for each extension, and without it the extension simply does nothing there. Local files need a separate switch, Allow access to file URLs, which matters for anyone who opens exported HTML reports from disk.

Two details that make it faster to live with

The popup is not the only way to reach the extension, and two small settings change how often it has to be opened at all.

The first is the keyboard shortcut. The links under the buttons in the popup open the browser's hotkey editor, where both the global on and off switch and the per site toggle can be bound to keys. Comparing a rendered page against the real one is a routine need when something looks wrong, and a shortcut turns that into a keystroke instead of a trip to the toolbar. On a Mac the extension shortcuts live in the browser's own keyboard shortcuts page rather than in System Settings.

The second is the toolbar icon itself. After installation the icon is often hidden behind the extensions button next to the address bar, and the help gives the fix: click that button, then the pin next to the entry. Without it, the fastest way to exclude one site is buried two clicks deeper than it needs to be.

For anyone willing to go further, the popup also exposes a developer tools panel holding the configuration for the current theme mode. It accepts CSS selectors, so a site that renders badly can be corrected locally, and the same fix can be submitted upstream.

Where a dark theme is the wrong tool

Every extension in this category exists to guess a palette the site's designers never wrote. For the five or six services that fill a working day, that guess is unnecessary, because those services usually ship a dark theme of their own that is designed rather than derived.

This is worth separating from the long tail. An internal tool from 2014, a vendor portal nobody will restyle, a documentation site with no theme switch: those are exactly what a dynamic inverter is for, and an allowlist posture keeps it pointed at them. Mail, chat, the document editor and the tracker are a different problem, because each of them has an appearance setting of its own and each deserves a different answer.

Tabs are what makes that hard. When every service lives in the same window, appearance gets decided once for all of them, and per site rules become a list to maintain. Treating each service as its own window puts the decision back where the answers differ, with mail in its native dark theme, the design tool in the colors its makers intended, and the spreadsheet untouched. A browser that keeps each web app in its own window makes that arrangement the default, and grouping those windows into workspaces keeps an evening reading setup separate from a daytime working one.

What to change first

Before adjusting anything else, switch the Site list to Invert listed only and add just the sites that genuinely need darkening, then set the browser's own theme to dark so the new tab flash disappears. Keep Dynamic as the global mode and use Filter+ only on individual pages that come out dull. For the handful of services open all day, turn on their native dark themes and let SpaceDeck hold each one in its own window instead.