Engineering notes · 17 November 2026

Restoring display colors without fighting other apps

Making a screen warmer is only half the job. A screen-color utility also needs to know when to stop, what to restore, and when the state it saved is no longer safe to use.

These are the choices in Sunbend 1.1.1 for Mac. They describe the implementation, not a promise that every display or macOS version behaves identically.

Restore a captured state, not an assumed default

Sunbend’s standard method captures a color table for each display before applying its own adjustments. Each new frame is derived from that captured table. It does not repeatedly multiply an already-adjusted frame, which would accumulate the change.

“Restore normal colors” pauses the app. It cancels the active fade and attempts to restore the captured tables. It does not calibrate the display, set a new color profile, or assume that a generic neutral table is the right starting point for your screen.

Check ownership before writing again

A display’s state can change while a utility is running. Before each standard-method write, including the intermediate frames of a fade, Sunbend compares the current table with the last one it wrote. Before restoring, it also checks the display’s color-profile identity.

If either check shows an unexpected change, Sunbend stops applying adjustments and reports that the display needs attention. Writing the old table back anyway could overwrite someone else’s change. This is why the app can pause after a conflict instead of repeatedly trying to force its colors onto the screen.

A disconnected display is a separate case: an offline display cannot be restored. Sunbend drops its stale display identifier and discovers it again on reconnection.

A successful write is not proof of visible color

The standard method can check the table it reads back. That is useful evidence about the API state, but it is not a measurement of light leaving the panel. Sunbend therefore also offers a short display check and asks whether you actually saw the change.

This distinction matters for the reported M5 Pro/Max limitation. We have not validated the workaround on those chips. A successful API call alone is not enough to claim compatibility.

The overlay has a different tradeoff

The experimental method uses a tinted, click-through window over each selected screen instead of adjusting its color table. Removing that window removes Sunbend’s overlay. The windows are configured to accompany Spaces and full-screen apps, but that configuration does not replace testing those cases across hardware and macOS versions.

Blending a tint over an image is less precise than adjusting its channels: dark regions can become lighter. Sunbend asks macOS to exclude the layer from screenshots and screen sharing; some capture apps may still include it. It is a fallback with visible compromises, not an equivalent replacement for the standard method.

What has actually been checked

On the development M3 Pro MacBook Pro, a harness using the app’s overlay class demonstrated a tint, click-through behavior, capture exclusion, and removal. In the running app, we also exercised method selection, warmth and dimming controls, film pause and resume, and interaction with Brave entering and leaving full screen. Those UI checks do not establish physical color accuracy or HDR behavior.

M5 Pro/Max, older macOS versions, Intel Macs, external-display combinations, and HDR still need direct validation. The download page keeps the current compatibility limits beside the installer.

Download for Mac

7-day free trialNo account