VKT Toolkit · August 28, 2026 · 7 min read

How to Enable Dark Mode on Any Website (Chrome & Edge) — 4 Methods Compared

You open a news site at 11 PM and the white background burns your eyes. You wish every website had a dark mode toggle. Most don't. But you can force dark mode on any website — there are 4 ways to do it, and they're not all equal.

We tested all 4 methods on 20 popular websites (Google, Wikipedia, GitHub, news sites, government portals). Here's what actually works — and what breaks.

Method 1: Chrome Flags (Built-In, Free)

Type chrome://flags in your address bar, search for "Auto Dark Mode for Web Contents", set it to Enabled, and relaunch Chrome.

Pros:

• Free, built into Chrome — no extension needed;
• Works on every website immediately;
• Zero performance impact.

Cons:

• Pure black backgrounds with white text — looks harsh, especially on image-heavy sites;
• Images and videos sometimes get inverted or washed out;
• No per-site control — it's all or nothing;
• Flag may be removed in future Chrome versions.

Verdict: Good for a quick hack. Not great for daily use.

Method 2: Dark Reader (Extension, Free)

The most popular dark mode extension with 20M+ users. It dynamically rewrites each website's CSS to produce dark themes.

Pros:

• High-quality dark themes — images stay intact;
• Per-site toggle and brightness/contrast sliders;
• Active development, large community.

Cons:

• Heavy on resources — constantly analyzing and rewriting DOM elements. Noticeable on laptops;
• Complex sites can break (layouts shift, text disappears);
• Same dark treatment for every site — no warm tone or custom color options;
• Can conflict with other extensions.

Verdict: Best for users who want maximum dark coverage and don't mind the CPU cost.

Method 3: System Dark Mode

Enable dark mode in Windows (Settings → Personalization → Colors → Dark) or macOS (System Settings → Appearance → Dark). Browsers that support prefers-color-scheme will pass this signal to websites.

Pros:

• No extension needed — OS-level;
• Browser UI (tabs, address bar) also turns dark.

Cons:

• Only works on sites that implemented dark mode — most sites ignore it;
• No per-site control;
• Doesn't help on the sites that burn your eyes the most.

Verdict: Good as a baseline signal. Useless alone for sites that don't support it.

Method 4: VKT StylePatch (Extension, Free)

VKT StylePatch takes a different approach. Instead of complex DOM rewriting or brute-force inversion, it applies simple, customizable CSS overrides — background color, text color, font size, and font family — on a per-site basis.

Pros:

• Lightweight — no DOM analysis, just CSS injection. Minimal CPU/memory impact;
• Per-site settings — customize each site independently (warm tones on news sites, dark on GitHub, default everywhere else);
• Warm tone options — not just black/white. Choose soft dark backgrounds with warm text colors for less eye strain;
• Font size control — increase text size on sites with tiny fonts, without zooming the whole page;
• Settings persist — once configured, changes apply automatically every time you visit;
• Free tier — full customization for one site. Premium ($2.99/mo or $9.99 lifetime) unlocks all sites.

Cons:

• Doesn't dynamically analyze page elements — some complex sites may need manual color tweaking;
• Not as "automatic" as Dark Reader for full coverage.

Verdict: Best for users who want control — customize the sites that bother you, leave everything else default.

Comparison Table

Which Should You Pick?

• "I want dark mode everywhere, no thinking" → Dark Reader;
• "I just want a quick hack" → Chrome flags;
• "I only care about sites that support it" → System dark mode;
• "I want to customize specific sites — warm tones, bigger text, my colors" → VKT StylePatch.

Most people end up using two: System dark mode as a baseline + StylePatch for the sites that need it. That combination covers 95% of use cases with near-zero resource cost.

FAQ

More guides in the VKT blog; questions to [email protected].