Chrome’s force dark mode flag: what it does and where it breaks
Last updated: 20 August 2026 · By the Eclipse team.
The short answer: Chrome has a built-in setting that darkens websites that never implemented dark mode. Turn it on at chrome://flags → search dark → set Auto Dark Mode for Web Contents to Enabled → Relaunch. It is free, requires no extension, and works on almost every page. It also darkens your photographs, can mangle gradients and CSS-variable-driven themes, and is an experimental flag Chrome may remove without warning.
How to turn it on
- Type
chrome://flagsin the address bar and press Enter. - Type dark in the search box at the top of the Experiments page.
- Find Auto Dark Mode for Web Contents and change the dropdown from Default to Enabled.
- Click the Relaunch button that appears at the bottom.
Chrome closes and reopens with your tabs restored. To undo it, return to the same flag and set it back to Default.
The dropdown also offers variants such as different inversion strategies for images and selective inversion of non-image elements. If the default setting is close but images look wrong, trying one of those variants is worth a minute before giving up on the feature.
What it actually does
It applies an automatic darkening transform at the rendering layer, below the page’s own CSS. Light backgrounds become dark, dark text becomes light. Crucially, it does this without any understanding of what individual elements represent — it is a transform over rendered colours, not an interpretation of a design.
That single property explains every complaint about it. The transform cannot know that one white rectangle is a page background that should go dark, while another white rectangle is the background of a company logo that should stay exactly as it is.
Where it breaks
- Photographs and illustrations. Content images get darkened along with the interface. On an image-heavy page the result reads as a fault rather than a theme.
- Logos and icons with baked-in backgrounds. A logo saved as dark artwork on white becomes dark artwork on dark.
- Complex gradients. Transforms that work on flat fills produce muddy or banded results across a gradient.
- Sites already using CSS custom properties for theming. The transform can fight the site’s own variables and land somewhere neither design intended — occasionally producing genuinely unreadable text.
- Sites that already have dark mode. Forcing dark on an already-dark theme can invert it back toward light. Some sites detect and resist this; many do not.
- It is all-or-nothing. There is no per-site exclusion. A page it ruins is a page you either tolerate or turn the whole feature off for.
Flag vs extension: an honest comparison
| Chrome flag | Dark mode extension | |
|---|---|---|
| Cost | Free, built in | Free or freemium |
| Install | Nothing to install | Extension required |
| Per-site control | None | Yes |
| Leaves photos alone | No | Depends on the tool |
| Brightness/contrast tuning | No | Usually yes |
| Stability | Experimental; may be removed | Stable API surface |
| Performance | Native, very cheap | Varies enormously |
The flag’s honest advantage is that last row. It runs inside the renderer, so it costs almost nothing — unlike some extensions, which cost a great deal. If your priority is a fast browser and you can live with darkened images, the flag is a perfectly reasonable answer and you should not let anyone sell you past it.
When to use the flag anyway
- You mostly read text-heavy pages with few images.
- You are on a low-powered machine and every millisecond counts.
- You cannot install extensions — managed or locked-down device.
- You want to try dark browsing before committing to any tool.
When you want something else
If images matter to you, or you need certain sites excluded, or you want to tune brightness rather than accept one fixed transform, the flag has no answer for you. That is the gap an extension fills: it can classify elements before deciding what to do with each one, which is precisely the information the renderer-level transform throws away.
Try it yourself: Eclipse applies a generated dark theme to any site, with per-site overrides and live brightness and contrast controls. Free, no account, no site limits.
Product and website names mentioned here belong to their respective owners and are used only to describe what they do. Eclipse is an independent extension and is not affiliated with, endorsed by, or sponsored by any of them.
Related guides
How to Enable Dark Mode on Any Website
Four methods that actually work — the site’s own setting, your OS preference, Chrome’s built-in flag, and an extension — with the trade-off each one makes.
Why Inverting Colours Isn’t Dark Mode
Inversion flips your brand blues to orange and your photographs to negatives. What a real generated theme does differently, in colour-space terms.
How Dark Mode Extensions Actually Work
CSS filters, stylesheet rewriting, and generated themes are three different machines. Knowing which one you are running explains every quirk you have hit.
Dark Mode Not Working on Some Sites? 9 Causes
Shadow DOM, canvas, iframes, inline styles, CSP — the specific technical reasons a page resists dark mode, and which ones are actually fixable.