Monitor Brightness and Eye Strain: The PWM Trap

Brightness is the first thing most people adjust when their eyes start complaining. It is also the adjustment most commonly set wrong, and on a specific category of monitor hardware, lowering brightness through the hardware controls can actively make eye strain worse. Understanding why this happens, and how to work around it, is one of the more practically useful things you can learn about display health.


Why brightness matters for eye strain

A screen running significantly brighter than the room it sits in creates a large luminance contrast between the display and everything else in your visual field. Each time your gaze shifts from the screen to the desk, the wall, or another person, the pupil must adjust to the change in light level. Over a workday, this repeated adjustment is a real source of visual fatigue.

The general advice is correct: reduce screen brightness so it roughly matches the ambient light in the room. A practical check is the white paper test. Hold a white sheet of paper in the ambient light next to your monitor. If the monitor surface looks substantially brighter than the paper, reduce brightness until they roughly match. This is not a precise calibration; it is a sanity check.

The problem appears when you try to do this through the monitor's hardware controls on certain panels.


The PWM trap

Many monitors, particularly budget to mid-range LCD panels, control backlight brightness through pulse-width modulation (PWM). Instead of smoothly varying the electrical current to the backlight to change its intensity, PWM switches the backlight on and off rapidly. At 100% brightness, the backlight is on continuously. At 50%, it switches on and off at a fixed frequency, with equal on-time and off-time. At 25%, the off-time is three times the on-time.

The frequency of this switching varies by monitor. Some use 1000 Hz or higher, where the flicker is unlikely to cause issues for most users. Many use 120 to 480 Hz, which is fast enough to be invisible to conscious perception but not fast enough to be fully inert to the visual system.

Here is the trap: as you lower hardware brightness, the PWM duty cycle becomes more aggressive. The backlight spends more of each cycle in the off state. For users whose visual systems are sensitive to this kind of subliminal flicker, the symptom pattern is paradoxical. They reduce brightness to reduce eye strain, symptoms get worse, they reduce brightness further, symptoms worsen again. The fix they are trying to apply is causing the problem.

Signs that PWM flicker may be a factor in your eye strain:


How to check your monitor for PWM

Open your smartphone's camera app and set it to slow-motion video mode. Point it at your monitor while it is displaying a solid white or light grey surface at a reduced brightness setting (around 30 to 50% hardware brightness). If the recording shows horizontal bands sweeping across the image or a visible flickering pattern, the monitor is using PWM at that brightness level and the flickering is active.

At 100% hardware brightness, most PWM monitors show no banding because the duty cycle is 100% (backlight always on). Try the test at various brightness levels to find where PWM becomes active on your specific panel.


Software brightness vs. hardware brightness

Software brightness operates at the graphics output layer. The application reduces the pixel values in the image signal before they reach the display hardware. The backlight itself continues to run at whatever hardware brightness level you have set. Because the backlight state does not change, PWM behavior does not change either.

The practical consequence: if you set hardware brightness to 70% or 80% (above the PWM activation range for your specific monitor) and use software brightness to bring the perceived screen luminance down to match your room, you get the luminance reduction you want without engaging the more aggressive PWM duty cycles that cause flicker at lower hardware settings.

Circadian Shield includes software brightness control specifically for this use case, alongside automated color temperature adjustment and a break timer. Try it free on Mac or Windows.


Practical brightness levels by environment

These are rough starting points. The right setting depends on the specific ambient light in your space and your monitor's peak brightness rating.

The goal in all cases is approximate parity between screen luminance and room luminance. The white paper test is a serviceable check at any of these conditions.


Brightness and color temperature are separate problems

Reducing brightness addresses luminance mismatch between screen and room. It does not change the color spectrum of the light coming off the screen. A dim screen running at 6500K in a warm-lit evening room is still contributing short-wavelength light to the visual environment even at reduced brightness. Color temperature adjustment addresses that separately. For a full treatment of the color temperature side, see dark mode and eye strain and screen eye strain.


Related pages


Software brightness that skips the PWM range

Circadian Shield's software brightness control lets you reduce displayed luminance without lowering hardware brightness into the PWM flicker zone. Try it free on Mac or Windows.

Download Circadian Shield