Chrome dark mode not working — the browser UI goes dark but websites stay white, or nothing goes dark at all despite enabling it, or dark mode works in some places but not others — has three separate causes that require three separate fixes. Understanding which layer is broken takes 30 seconds and saves you chasing the wrong fix. For a broader walkthrough, our Google Chrome Errors is a good next read.
Chrome’s dark mode operates across two layers that are independently controlled:
- Browser UI dark mode — the tab bar, address bar, menus, and Chrome’s own interface
- Webpage dark mode — the content of websites (text, backgrounds, images)
These are controlled separately. You can have a dark browser UI with white websites, or white browser UI with dark websites. Understanding which isn’t working tells you where to look.
Windows dark mode — the browser UI layer
Chrome’s UI follows the Windows system colour theme by default. If Windows is set to Light mode: Chrome stays light regardless of what you do inside Chrome. Set Windows to Dark first: Settings → Personalisation → Colours → “Choose your mode” → Dark. Chrome’s interface changes immediately to match.
If you’ve already set Windows to Dark mode but Chrome’s UI is still light: Chrome might be overriding the system setting. In Chrome: menu → Settings → “Appearance” → “Theme” → click “Open Chrome Web Store” → search for a dark theme and install one, or use the “Go default” option to sync back to system theme.
Force dark mode on websites — the flag approach
The browser UI being dark doesn’t make websites dark. For that you need Chrome to force websites to use dark colour schemes. The flag:
Type chrome://flags/#enable-force-dark in the address bar → find “Auto Dark Mode for Web Contents” → change from Default to “Enabled” → Relaunch Chrome.
This forces dark mode on every site, including ones that don’t have their own dark mode implementation. The trade-off: some sites look slightly off (colours inverted in unexpected ways, images with white backgrounds becoming black). Mostly works well for text-heavy sites; occasionally strange on image-heavy sites.
If you want dark mode only on specific sites: the flag approach forces it everywhere. For per-site control, a dedicated extension like Dark Reader gives you granular control per domain.
Sites with native dark mode support
Well-designed sites implement their own dark mode that responds to your system colour preference. These don’t need the Chrome flag — they detect Windows/macOS dark mode automatically and switch their own colour scheme. GitHub, Twitter/X, Gmail (when using its built-in dark theme), Wikipedia, YouTube, Google’s products — all have native dark modes that activate when the OS is set to Dark.
If these sites are still showing light colours despite Windows being in Dark mode: Chrome isn’t correctly passing the prefers-color-scheme: dark media query to the website. This is rare but happens with certain extensions that interfere with CSS processing.
Test: open DevTools (F12) → toggle the CSS media feature simulation. In DevTools → Rendering tab (enable via three dots → More tools → Rendering) → “Emulate CSS media feature prefers-color-scheme” → select “dark.” Does the site change? If yes: the site has native dark mode, Chrome is just not passing the OS preference correctly. If no: the site doesn’t have native dark mode, you need the flag or extension approach.
Dark Reader — the reliable solution
For websites without native dark mode, the flag approach works but can produce inconsistent results. Dark Reader (free browser extension, available in Chrome Web Store) provides a much more refined dark mode experience with fine-tuned contrast, brightness, and sepia controls per site.
Install Dark Reader → it’s immediately active on all sites. Click the extension icon to configure brightness/contrast, toggle per-site, or add sites to the exclusion list where you don’t want dark mode applied. Compared to Chrome’s built-in flag: Dark Reader produces much better colour handling, respects the site’s images correctly, and allows per-site customisation.
Trade-off: Dark Reader has access to all page content to implement the colour transformation, which is a privacy consideration for sensitive sites. Many users disable it on banking and secure sites while keeping it everywhere else.
Our guide on Chrome page loading issues covers the broader rendering problems that sometimes affect dark mode alongside other visual features, and our Chrome stability troubleshooting covers flags and experimental features causing crashes. For Chrome’s built-in dark mode implementation details and the CSS prefers-color-scheme API, Chrome Developer documentation covers the colour scheme media query that sites use to detect system dark mode preference.
Extensions that conflict with dark mode
Some extensions actively interfere with how colours are rendered in Chrome tabs. This is especially common with:
- Grammar and spelling extensions that overlay text styling
- Screenshot and screen capture tools that hook into the rendering pipeline
- Custom font extensions that affect how text styles are applied
- PDF viewer extensions that change how content is processed
If dark mode was working and stopped working after installing an extension: disable it in chrome://extensions and test. Dark mode should restore. If it does: that extension is the conflict. Check if the extension has an update available, or just keep it disabled when dark mode matters.
Per-site dark mode vs global dark mode
Many users actually don’t want every site dark — they want dark mode for most sites but not Google Sheets (which looks odd dark), not websites with custom light design they like, and not image galleries where colour accuracy matters.
Hybrid approach using Dark Reader: install Dark Reader → set to “Enabled” globally → open the extension settings → “Sites list” tab → add sites you want to exclude to the “Not Inverted” list. These sites remain in light mode while everything else gets dark mode.
Same logic applies the other way: if you prefer light mode globally but want specific sites dark (like code documentation or technical references), add just those to Dark Reader’s “Only Inverted” list.
Chrome profile and sync state
Dark mode settings including Chrome theme and the experimental flag state aren’t always synced between devices via Chrome Sync. If dark mode works on one computer but not another using the same Chrome account: the settings diverged. You’ll need to configure the flag and theme settings separately on each device.
Chrome extension settings (like Dark Reader’s per-site configuration) also don’t always sync perfectly. Dark Reader specifically offers its own sync through Google Drive — enable it in Dark Reader settings to keep your per-site configuration consistent across devices.
PDF dark mode in Chrome
Chrome’s built-in PDF viewer has its own dark mode toggle separate from the browser UI and website dark mode. When viewing a PDF in Chrome: look for the moon/sun icon in the PDF viewer toolbar at the top. If it’s not visible: the PDF viewer might be using an older version that doesn’t expose the toggle — update Chrome to the latest version.
The PDF dark mode in Chrome inverts the page while trying to keep image colours intact. Results vary by PDF — text-only PDFs look great; scanned image PDFs look inverted and strange. For complex PDFs, toggle dark mode off specifically for PDFs via the toolbar icon while keeping website dark mode active through the flag or extension.
macOS users — different path for Chrome dark mode
On macOS, Chrome follows the system Appearance setting rather than Windows colour mode. System Preferences → Appearance → Dark. Chrome’s UI changes with it. The website dark mode flag works the same as on Windows: chrome://flags/#enable-force-dark → Enabled.
macOS also supports a scheduling feature (System Preferences → Appearance → “Auto”) that switches between light and dark based on time of day. Chrome follows this schedule — it’s dark at night and light during the day automatically. If Chrome is toggling unexpectedly: this schedule might be the cause. Dark Reader handles this better than the Chrome flag by keeping dark mode consistent regardless of system schedule changes.
| Problem | Layer | Fix |
| Chrome UI is light, websites are light | Windows system mode | Settings → Personalisation → Colours → Dark |
| Chrome UI is dark, websites are light | Webpage dark mode not enabled | chrome://flags/#enable-force-dark → Enabled, or install Dark Reader |
| Chrome UI is light despite Windows being dark | Chrome theme override | Chrome Settings → Appearance → Theme → reset to default/Go default |
| Sites with native dark mode staying light | CSS media query not passing | Disable extensions; test in Incognito; verify prefers-color-scheme in DevTools |
| Dark mode inconsistent across sites | No native dark mode on some sites | Dark Reader with per-site configuration |
| Dark mode breaks after extension install | Extension rendering conflict | Disable extensions one at a time to identify culprit |
Understanding the two-layer structure (Windows system theme for Chrome UI + separate webpage dark mode) is the key insight. Once you know which layer is broken, the fix is immediate. Most people who say “Chrome dark mode doesn’t work” actually have one layer working and one not, and they just need to enable the other half.
Eye strain context — why dark mode matters to different users
People choose dark mode for different reasons, and those reasons affect which implementation they need:
Ambient light sensitivity: working in dark rooms where white backgrounds are blindingly bright. The Chrome flag forcing dark on all sites helps here, even if colours aren’t perfect.
OLED display users: dark pixels on OLED screens use virtually no power. True dark mode (black backgrounds rather than just dark grey) meaningfully extends battery life on OLED laptops and phones. Dark Reader allows you to configure background colour to true black (#000000) for this purpose.
Eye fatigue reduction: research is mixed on whether dark mode actually reduces eye fatigue compared to a properly calibrated bright screen, but many users find dark mode more comfortable for long reading sessions. This is personal preference more than physiology.
Sleep and circadian rhythm: dark mode with warmer colour temperature in the evening (which Night Light in Windows handles separately from dark mode) is genuinely useful. Night Light + dark mode together is the best combination for evening use.
Night Light vs dark mode — not the same thing
Windows Night Light (Settings → System → Display → Night light) shifts screen colour temperature to warmer tones in the evening to reduce blue light exposure. Dark mode changes backgrounds from white to dark. These are different features that complement each other but don’t replace each other.
Chrome has its own blue light filter in some versions but it’s less customisable than Windows Night Light. For most users: enable Windows Night Light for scheduling, and Dark Reader for website dark mode — they work together without conflict.
Incognito and dark mode
Incognito windows don’t load extensions by default. If Dark Reader is your dark mode solution: it won’t work in Incognito unless you explicitly enable it there. chrome://extensions → Dark Reader → toggle “Allow in Incognito.” Same for any extension providing dark mode functionality.
The Chrome flag (enable-force-dark) does apply to Incognito since it’s a browser-level setting, not an extension. This is actually useful for privacy-conscious users who use Incognito frequently — the flag gives dark mode without requiring an extension with full page access.
When “dark mode” is just high contrast
Windows Accessibility includes a “High Contrast” mode that’s distinct from dark mode. High contrast uses very limited colour palettes (black background, white text, strong accent colours) rather than the softer dark grey palettes of dark mode. If you accidentally enabled High Contrast: Settings → Accessibility → Contrast themes → “None.” High Contrast affects Chrome’s UI and how pages render within it, and can make Chrome look “dark but wrong.”
Some keyboard shortcuts (Left Alt + Left Shift + Print Screen) toggle High Contrast by accident. If Chrome’s colours suddenly look dramatically different (stark black and white rather than subtle dark grey): High Contrast was toggled. Disable it via the Settings path above and normal colours return immediately.
Dark mode, in short, is not a single toggle — it’s a layered system where the OS, the browser, individual websites, and extensions each have their own controls. Once you understand the layers and know which one isn’t cooperating in your specific situation, the fix is straightforward. For most users who just want everything dark: Windows Dark + Dark Reader extension is the most reliable combination available in 2026.
One last practical note on the force-dark flag: Chrome occasionally resets experimental flags after a major update. If dark mode stops working on websites after Chrome updates and you’re using the flag approach: check chrome://flags again — it may have reverted to Default. This is one reason Dark Reader is preferred over the flag for consistent results; it persists across updates and doesn’t depend on Chrome’s experimental flag infrastructure. If this sounds familiar, Chrome Cache Not Clearing is worth a look.
