What is ForcedSkin?

A browser-level colour layer, not a new website

ForcedSkin exists for a simple mismatch: every site picks its own palette, and many never offer a usable dark or light alternative. Instead of hunting theme toggles on each domain, you install a Chromium extension (Chrome, Edge, Arc) and apply one coordinated palette to ordinary web pages as they load.

Unlike a company “about” overview, this article is the product definition in search terms. ForcedSkin is webpage theming: backgrounds, text, links, borders, forms, and other CSS-controlled UI. It is not a content blocker, layout redesign, or a skin for the Chrome toolbar. For a shorter product tour see About ForcedSkin.

What it changes — and what it deliberately leaves alone

The engine recolours CSS interface colours. Photos, videos, canvas drawings, and bitmap backgrounds are preserved whenever possible, so image-heavy pages do not turn into a negative photograph. Layout, copy, ads, and navigation stay as the site authored them; ForcedSkin does not rewrite HTML structure or block clicks.

Theming runs locally in the browser. Page HTML is not uploaded for colouring. Optional account features on forcedskin.com sync palettes and adapters after you sign in — they are not required to recolour pages. Details are in the privacy policy.

• CSS UI colours map to your light or dark palette
• Media pixels stay intact when the browser can tell them apart from UI
• No layout rewrite, ad injection, or navigation blocking

Modes, marketplace, and site-specific control

The popup exposes Light, Dark, Auto, and Off. Auto follows local time (light roughly 06:00–18:00, dark otherwise) without polling in the background. Off restores original site colours everywhere until you turn theming back on.

Palettes live in the theme marketplace. Community site adapters use the JSON schema forcedskin-adapter-formula/v1 to refine colouring on named hostnames. Per-site whitelist exclusions keep chosen domains native. Read how ForcedSkin works for the engine, or exclude sites for whitelist behaviour.

Honest limits on protected and closed surfaces

Browser extensions cannot restyle chrome:// pages, Chrome settings, or the Chrome Web Store. Closed Shadow DOM and bitmap-only UI also sit outside CSS recolouring. Open Shadow DOM, many SPAs, and ordinary frames are in scope when the page exposes styleable nodes.

Those limits are why ForcedSkin pairs a universal CSS engine with optional adapters and exclusions rather than promising a perfect skin on every URL. If a site already looks right, exclude it. If Chrome chrome itself is the target, this is the wrong product — see browser theme extension.

Common questions