Flicker-Free Mode for Mac: How Sundown Dims Through Gamma Instead of the Backlight

You have tried turning your brightness up. You have tried turning it down. Both make your head hurt, just differently. Up is too harsh. Down triggers the invisible strobe that your MacBook uses to simulate dimness. You cannot win because the display hardware was not designed with your neurology in mind.

Flicker-free mode is a specific technical approach to this problem. It is not a marketing phrase. It describes a method where the hardware backlight stays locked at maximum output while all perceived dimming happens through software manipulation of the display's gamma lookup table. The result is a screen that looks as dim as you want while the backlight stays at full power, so dimming no longer relies on the backlight's PWM.

This post explains the mechanism in detail, shows you why the obvious fixes do not work, and walks through exactly what Sundown does at the rendering level to take dimming off the backlight without forcing you to stare at a full-brightness panel.

Why Your MacBook Flickers When You Dim It

Every MacBook display controls brightness using Pulse Width Modulation. The backlight does not glow at a lower wattage when you drag the brightness slider down. It switches between fully on and fully off at a fixed frequency, and the ratio of on-time to off-time determines perceived brightness.

At 50% brightness, the backlight is on for half of each cycle and off for the other half. At 20% brightness, it is on for one-fifth of the cycle. The lower you go, the more time the display spends in the off state. Your eyes average the rapid switching into a steady glow. Your visual cortex does not.

NotebookCheck measurements show MacBook Pro miniLED models use PWM across the whole brightness range, switching far faster than you can see. The MacBook Air activates PWM below roughly 40% brightness. Both use it. They differ in when and how aggressively.

The critical point most articles miss: on MacBook Pro 14-inch and 16-inch models with miniLED, PWM operates at every brightness level including 100%. The local dimming zones that give miniLED its contrast advantage require PWM to function. You cannot escape it by cranking brightness to maximum. The backlight still strobes. It just strobes with a near-100% duty cycle.

What the Research Actually Says About Invisible Flicker

IEEE 1789-2015 classifies LED flicker risk by frequency. Below 90 Hz is high risk. Above 1,250 Hz is low risk. The MacBook Pro's PWM falls in the low-risk band. Low risk is not no risk.

Research by Wilkins and colleagues showed that headache incidence doubles at 100 Hz flicker versus 32 kHz. The MacBook's PWM is far faster than 100 Hz, but for people who are sensitive to flicker, faster is not the same as harmless.

Electroretinography studies demonstrate measurable cortical response to flicker frequencies far above the 80 Hz threshold of conscious perception. Your brain cannot see the strobe. It responds to it anyway. The headache, the eye pressure behind your orbits, the difficulty concentrating after an hour of screen work at low brightness — these are neurological responses to a physical stimulus that your conscious vision has no mechanism to detect.

The Three Approaches to Stopping PWM

There are three common ways to take PWM out of dimming on a Mac. Each involves a trade-off.

Option 1: Lock brightness at maximum. On displays where full brightness means a 100% duty cycle, the backlight never enters the off state. The trade-off is obvious: you now have a screen that is painfully bright in any room that is not flooded with sunlight. This is the approach most forum posts recommend. It works for about ten minutes before your eyes start watering from the sheer luminance.

Option 2: Use an external monitor with DC dimming. Some monitors dim by reducing the voltage to the backlight rather than strobing it. No PWM at all, at any brightness level. The trade-off is cost (a good DC-dimmed monitor is $400 or more) and portability (you lose the benefit the moment you leave your desk).

Option 3: Lock brightness at maximum and dim through the gamma table. This is what flicker-free mode does. The hardware backlight stays at full blast. The gamma lookup table — the mathematical function that maps pixel values to display output — is modified to reduce perceived brightness across the entire panel. Your screen looks dim while the backlight stays at full power, so the dimming doesn't rely on the backlight's PWM and you aren't staring at raw full-brightness luminance either.

How Gamma Table Dimming Works

Every display has a gamma lookup table (LUT). It is a function that translates the digital color value for each pixel into the actual light output. When macOS wants to show a pixel at 50% brightness in the color value, the gamma table maps that to the corresponding voltage for the display hardware.

Flicker-free mode modifies this table. Instead of letting the backlight handle dimming (via PWM), Sundown adjusts the gamma curve so that every pixel's output is scaled down mathematically. A pixel that would normally produce 200 candelas might be mapped to produce 80 candelas. The backlight is still at 100%. The pixel just asks for less light.

This is the same technique your display uses for color temperature adjustment. When you enable Night Shift or any blue light filter, macOS modifies the gamma table to reduce blue channel output. Flicker-free mode extends this to all three channels equally, producing a uniform dimming effect.

The technical implementation in Sundown uses CoreGraphics gamma APIs. It writes directly to the display's color lookup table for each connected screen, and the display hardware applies that table until the next adjustment.

Why Software Dimming Looks Different From Hardware Dimming

If you have ever compared a display at 50% hardware brightness versus 100% brightness with a 50% gamma reduction, you may have noticed they do not look identical.

Hardware dimming (PWM) reduces the total amount of light leaving the display. Software dimming (gamma) reduces the range of light values the display can produce. The practical difference is contrast ratio. With hardware dimming, the ratio between the brightest and darkest pixels remains the same. With gamma dimming, the brightest achievable pixel is capped lower, which slightly compresses the contrast range.

In practice, the difference is subtle at moderate dimming levels (30% to 70% perceived brightness). At very deep dimming (below 20%), gamma dimming can make dark scenes look washed out because the display cannot produce enough distinction between near-black values.

Sundown accounts for this by applying a perceptually calibrated gamma curve rather than a linear reduction. Dark values are preserved with more precision than bright values, maintaining visible contrast in shadow detail even at low perceived brightness. The result is a dimmed display that looks natural, not flat.

MacBook Air vs MacBook Pro: Different Strategies

The two machines require different approaches because their PWM behavior differs.

MacBook Air (M2, M3, M4): PWM activates below approximately 40% brightness. Above that threshold, the Air uses DC voltage reduction, which produces zero flicker. If you keep your Air above 40% brightness, you do not need flicker-free mode for PWM protection. You may still want it for the additional dimming control, but PWM is not the concern.

MacBook Pro 14-inch and 16-inch (2021 and later): MiniLED local dimming zones require PWM at every brightness level. Even at 100%, the individual dimming zones strobe to maintain contrast. No brightness setting takes PWM out of the picture on these machines by itself, which is where gamma-based dimming comes in.

Sundown detects which Mac you are running on and adjusts its behavior accordingly. On a MacBook Air above 40% brightness, it leaves the hardware brightness alone and only applies color temperature filtering. On a MacBook Pro, it locks to maximum and handles all dimming through the gamma table by default when flicker-free mode is enabled.

Battery Impact

A reasonable concern: if the backlight runs at 100% all the time, does battery life suffer?

Yes, somewhat. A backlight at full power draws more than one at a typical indoor setting, so expect a shorter charge when flicker-free mode is on, especially on long unplugged days.

Whether that trade-off makes sense depends on how much PWM bothers you. If low brightness is where your screen days tend to go wrong, giving up some battery for a backlight that isn't doing the dimming may be an easy call.

How Sundown Implements Flicker-Free Mode

When you toggle flicker-free mode in Sundown's menu bar popover, three things happen in sequence.

First, Sundown reads your current hardware brightness value and stores it. This saved value is what gets restored when you turn flicker-free mode off.

Second, Sundown sets the hardware backlight to maximum through IOKit's brightness API. The display goes to full luminance.

Third, Sundown recalculates the gamma table to compensate. The gamma curve is adjusted so that the perceived brightness on screen matches what it was before the mode was enabled, even though the physical backlight is now at 100%. If you had your screen at 50% perceived brightness, the gamma table reduces pixel output by approximately 50%. The aim is for the screen to look the same. The hardware behavior is completely different.

Sundown applies the gamma adjustment together with the brightness change, so the two land as one step rather than two.

If you connect or disconnect an external display, Sundown reapplies the brightness lock automatically. If the system goes to sleep and wakes, the lock is reapplied on wake. The app watches for display configuration changes so it can put the backlight back to full power when something resets it.

FAQ

Does flicker-free mode work on external monitors?
Flicker-free mode controls the MacBook's built-in display backlight via IOKit. External monitors have their own backlight controllers that macOS cannot access. For external displays, the gamma dimming still applies (your external screen will look dimmer), but the hardware brightness remains controlled by the monitor's own firmware.

Can I use flicker-free mode with Night Shift or f.lux?
Technically yes, but there is no benefit. All three apps modify the gamma table. Running multiple gamma-modifying apps simultaneously can produce unpredictable color results. Sundown's built-in color temperature filtering goes deeper (500K vs Night Shift's 2700K), so flicker-free mode plus Sundown's own filter covers everything.

Will flicker-free mode affect True Tone?
True Tone adjusts the display's color profile based on ambient light sensors. It operates at a different layer than the gamma table. Both can run simultaneously without conflict. However, True Tone's adjustments are subtle (it shifts color temperature by a few hundred Kelvin), and at the deep warm temperatures Sundown applies, the True Tone adjustment becomes imperceptible.

Is there any scenario where flicker-free mode makes things worse?
If you are not sensitive to PWM, running flicker-free mode costs you some battery life (the backlight at max draws more power) and very slightly reduces contrast ratio at deep dimming levels. For most users, these trade-offs are unnoticeable. If PWM bothers you, you may decide they are a fair price for a backlight that isn't doing the dimming.

Flicker-free mode is one toggle in the menu bar, so it's easy to try on your own screen. Start your 7-day free trial at trysundown.com.