Dim a Mac screen below the minimum brightness

At night the lowest brightness notch is still too bright, and on an external monitor the lowest DDC/CI value is only the panel's own minimum. One lever goes below both: the display transfer table. Here is how it works, what it costs, and how to get back.

Why the slider has a floor

The slider does not reach zero. On a built-in display macOS stops at a floor set by the panel's minimum backlight; on an external monitor the lowest DDC/CI value still means “the panel at its own minimum”. Below that the panel simply has no darker state to offer.

That floor is a hardware fact, not a setting. No slider, brightness key or app can move it — which is the whole reason a second lever exists.

The lever that does go lower

The picture is produced by the GPU and shaped by a transfer (gamma) table before it reaches the panel. Scaling that table down darkens every pixel while the backlight stays where it was, so the image can go below what the panel would do on its own. It is the same mechanism Night Shift and colour profiles use.

Two ways to reach it without buying anything:

• Reduce white point. System Settings → Accessibility → Display. A built-in dimmer that goes below the slider's floor, free and fully reversible. It is blunt: it lowers the white point, not the black.
• A free utility that writes the gamma table. MonitorControl does software dimming as well as DDC — if brightness and volume are all you want, use it and pay nobody.
• Or a console that names the path. LumePane tries DDC/CI first, falls back to the transfer table when a panel does not answer, and tells you which of the two a given display is on instead of pretending they are the same thing.

What it costs

• Blacks stop being true black. Dimming the picture rather than the backlight lifts the black floor relative to white; at low values dark scenes read as grey.
• Contrast is compressed, not just lowered. Highlights and shadows are scaled together, so the image loses punch before it loses brightness.
• Colour accuracy drifts unless the app computes from the original curve. A tint applied on top of an already-shaped table changes the colour twice.
• HDR and OLED are a different problem. Tone mapping is not yours to rewrite, and an SDR gamma dim on HDR content is simply wrong.
• Banding can appear on 8-bit panels at very low values, because fewer code values are left to describe the gradient.

How to do it without breaking the display

The one rule that makes this reversible: <strong>capture the panel's original ramp once</strong>, when you take control, and always compute from that copy. If each adjustment shapes the curve you last wrote, repeated dimming compounds — a few passes later the screen is black and nobody knows why.

Write, then read the table back and compare one interior sample with what you asked for. A wake, a resolution change or a GPU reset can discard the table without telling anyone; retry with backoff instead of assuming the write stuck.

Undo should be one action, not a reboot: write the captured curve back and hand the display to ColorSync.

When not to use it

If the work depends on measured colour — print, photography, video grading — a gamma dim is not a substitute for a colorimeter, and no software dimmer is. For HDR use the display's own brightness control. And if the panel does answer DDC/CI, dim the backlight: that is the honest dim, and the one that keeps blacks black.

Quick answers

Related

How to change an external display's brightness · Colours look washed out after dimming · Scheduled dimming walks the screen to black · What a gamma table actually does · DDC/CI not responding · All guides