Optical Display Dimming & Kelvin Color Math

Why hardware backlights flicker with PWM below 50%, CSS luminance vs 3400K-6500K RGB math, OLED black pixel savings, and Video Spotlight isolation.

Drop a laptop or external monitor backlight slider below 30% in a dark room and your eyes often feel tired within twenty minutes—even though the screen looks dimmer.

In many displays, that fatigue comes from hardware Pulse-Width Modulation (PWM) rather than absolute brightness itself. Understanding how panel dimming, perceptual gamma, blackbody RGB matrices, and browser compositing interact is the whole engineering rationale behind Smart Brightness.

Hardware PWM Flicker Below 50% Duty Cycle

Most desktop monitors and OLED laptop panels do not dim LEDs smoothly by lowering DC drive current across the full range. Lowering DC current too far shifts phosphor color accuracy and introduces uneven panel uniformity, so firmware drives the backlight at peak current and flickers it off and on thousands or hundreds of times per second.

At 100% brightness, the duty cycle stays continuous (1.0 DC-equivalent). Drop the hardware slider to 35% or 20%, and a 240 Hz–480 Hz PWM panel spends more than half of every millisecond completely black between sharp peak flashes:

100% Backlight:  ████████████████████████████  (Continuous light, 0% modulation)
 50% PWM Cycle:  ████░░░░████░░░░████░░░░████  (50% dark gaps every cycle)
 20% PWM Cycle:  ██░░░░░░░░██░░░░░░░░██░░░░░░  (High temporal contrast spikes)

Even when flicker sits above conscious fusion threshold (~60–90 Hz), saccadic eye movement across text lines produces subtle phantom-array stroboscopic trails that force ciliary and extraocular muscles to work harder. Keeping the physical display near 80%–100% (where PWM duty cycles stay wide or DC-driven) and attenuating pixel luminance inside the browser compositor removes hardware flicker entirely for web reading.

Perceptual Brightness vs Optical CSS Luminance Transforms

Cutting pixel intensity linearly in RGB space does not match how human vision senses brightness.

Standard web content lives in sRGB, where numerical RGB channels map to physical light output via an approximate gamma curve of ~2.2. Meanwhile, human photoreceptors respond logarithmically / via a compressive power law (Stevens’ power law around L^(1/3)). Cut sRGB values straight in half (255 -> 128) and physical photon output falls to roughly (0.5)^2.2 ≈ 21.7%, yet perceived lightness still reads around 50%—while muddy gray overlays kill edge crispness.

Why Naive Black Overlays Wash Out Pages

Many quick browser extensions dim websites by stretching a single position: fixed; background: rgba(0, 0, 0, alpha) sheet across the viewport. That shortcut creates two visible defects:

  1. Contrast compression: A translucent black veil pulls bright white #FFFFFF downward, yet lifts dark-mode #0A0F1C surfaces toward gray haze whenever blend modes or hardware gamma interact poorly, hurting text legibility.
  2. Media destruction: Full-screen dimming blankets crush shadow detail inside embedded HTML5 video players, charts, and photographs identically alongside harsh white documentation pages.

Compositing optical luminance adjustments (brightness(f) filters coupled with dark canvas re-mapping where needed) preserves relative foreground-to-background contrast ratios much more cleanly than slapping a semi-transparent tint box over the screen.

Kelvin Color Temperature RGB Approximation (3400K to 6500K)

Daylight calibration (D65, 6500K) delivers balanced neutral whites in sunlit offices, yet radiates a strong spike around 460–480 nm that suppresses evening melatonin onset and exaggerates glare against dark walls.

To shift a webpage smoothly between 6500K and warm 3400K candlelight without resorting to murky orange filters that erase syntax-highlighting colors, Smart Brightness applies RGB channel attenuation curves modeled along the Planckian blackbody locus (following classic Tanner Helland / CIE daylight polynomial fits):

For temperature T in [3400K, 6500K]:
  t = T / 100  (34 .. 65)
  R = 255  (red channel stays anchored at 1.00 below 6600K)
  G = clamp(99.4708 * ln(t) - 161.1196, 0, 255)
  B = clamp(138.5177 * ln(t - 10) - 305.0448, 0, 255)

Normalized against D65 (6500K), those multipliers look like this across presets:

Kelvin Preset Red Multiplier Green Multiplier Blue Multiplier Visual Effect
6500K Daylight 1.00 1.00 1.00 Unaltered neutral white point
5000K Studio 1.00 0.89 0.76 Subtle blue-spike trim for afternoon coding
4400K Sunset 1.00 0.84 0.66 Warm paper tone; syntax blues stay distinct
3600K Midnight 1.00 0.77 0.50 Strong short-wavelength reduction
3400K Deep Warm 1.00 0.75 0.46 Maximum amber comfort for dark rooms

Because the red channel remains at 1.00 while green and blue taper smoothly along logarithmic curves, monochrome contrast stays sharp and colored UI pills remain distinguishable. You can test these transitions live in the Smart Brightness interactive sandbox.

True #000000 OLED Subpixel Power Draw

On IPS or VA LCD screens, a pure black #000000 background only blocks light using twisted liquid crystals while the rear LED matrix still burns power behind it. On emissive OLED displays, the physics flip completely.

Every pixel in an OLED panel generates its own light through organic red, green, and blue subpixels. Standard “dark mode” themes (#111827 or #1E293B) keep millions of subpixels lit at low current—producing slight dark-gray glow in dark rooms and drawing continuous display current. Dropping page backgrounds down to exact #000000 turns unlit OLED subpixels completely off: zero photon emission, zero black-floor haloing around text, and measurable battery savings on OLED laptops during long reading sessions.

Video Spotlight DOM Isolation

Optical dimming fails if it makes movies unwatchable. Apply brightness(0.45) globally across html on a video site and crisp night scenes inside an HTML5 <video> element crush straight into flat black noise.

Video Spotlight isolates <video> elements and active player wrappers inside the DOM tree, pinning media surfaces back to 100% native luminance while surrounding article text, comment feeds, and sidebars stay dimmed and warm-tinted.

Like every Chromium Manifest V3 extension, this DOM-level control respects hard browser security boundaries documented in the Smart Brightness Privacy Policy: extensions cannot inject stylesheets into internal chrome:// settings pages, the Chrome Web Store domain itself, or hardware-protected DRM video overlay planes where the OS composites decrypted frames directly outside Blink’s CSS tree. Inside normal web documents, keeping all profile storage in chrome.storage.local means per-domain brightness, Kelvin, OLED, and spotlight preferences stay strictly on your machine with zero network requests.