Open-source project
MonitorControl/MonitorControl avatar
MonitorControl/MonitorControl

MonitorControl: Bringing Native Brightness and Volume Control to External Mac Displays

🖥 Control your display's brightness & volume on your Mac as if it was a native Apple Display. Use Apple Keyboard keys or custom shortcuts. Shows the native macOS OSDs.

34,733 stars1,042 forksSwiftMIT

At a glance

What is it?
MonitorControl is an open-source macOS utility that uses DDC/CI and software fallbacks to control external display brightness, volume, and contrast with native OSD and keyboard shortcuts. It is a practical tool for Mac users with non-Apple monitors, but it has notable hardware limitations.
Who is it for?
Adopt MonitorControl if you use a Mac with an external non-Apple display that supports DDC/CI over USB-C or DisplayPort, and you want hardware-level brightness and volume control with native OSD and keyboard shortcuts. Do not adopt it if you rely on the built-in HDMI ports of certain Macs (2018 Intel Mac mini, M1 Macs, entry-level M2 Mac mini) or if you use DisplayLink docks, where only software dimming is available.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 32 days ago.
What is it written in?
Mainly Swift, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • MonitorControl/MonitorControl34,733 ★ · +745
Star history
Repository2026-08-182026-11-15
MonitorControl/MonitorControl34k34.7k

745 Stars in the last 89 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The Problem: External Displays Are Second-Class Citizens on macOS

macOS gives built-in and Apple displays native brightness and volume control through the keyboard and Control Center. External monitors from other manufacturers do not get that treatment. Users are left with the monitor's own buttons, which are often awkward, or third-party utilities that lack integration. MonitorControl solves this by intercepting the standard brightness and media keys and applying them to external displays. It also adds a menubar slider for brightness, volume, and contrast. The target audience is clear: Mac users with one or more non-Apple external displays who want the same control they get with an Apple display. The README states that it supports 'most modern LCD displays' via DDC/CI, plus software alternatives for displays that lack that protocol. This is a focused tool for a specific annoyance, not a general system utility.

How It Works: DDC/CI, Native Protocols, and Gamma Table Fallbacks

The core mechanism is DDC/CI, a standard that allows software to send control commands to a display over the video connection. MonitorControl uses this to adjust brightness, contrast, and volume on displays that implement it. For Apple and built-in displays, it uses the native Apple protocol. When hardware control is not possible, the app falls back to software methods: Gamma table control for software dimming, and shade control for virtual screens like AirPlay, Sidecar, and DisplayLink. The README also mentions combining hardware and software dimming to extend the range below the display's minimum. This is a layered approach: try the hardware path first, then degrade to software. The app also supports smooth brightness transitions and can synchronize brightness from built-in or Apple screens to non-Apple displays, replicating ambient light sensor and Touch Bar changes. That synchronization is a differentiator, as it ties external displays into the same adaptive brightness behavior as the built-in screen.

Getting It Running: Installation and First Steps

Installation is straightforward. You can download the latest .dmg from the Releases page, or use Homebrew with the command 'brew install --cask monitorcontrol'. After copying the app to Applications, you launch it and are prompted to add it to Accessibility under System Settings, Privacy & Security. That permission is only required if you want to use the native Apple keyboard brightness and media keys; if you skip it, you can still use the menubar sliders. The README advises enabling 'Show advanced settings' in the app's Settings to access dozens of customization options. Custom keyboard shortcuts are set under the Keyboard section in Settings. The app uses Apple media keys by default. This is a simple setup, but the Accessibility permission is a common hurdle for less technical users. The build process is more involved: you need Xcode, SwiftLint, SwiftFormat, and BartyCrouch for localizations, then clone the repository and open the Xcode project. Dependencies are fetched automatically, with a manual fallback via 'File > Packages > Resolve Package Versions'.

Hardware Limitations: Where DDC/CI Fails

The README is explicit about several cases where hardware control is not possible. The built-in HDMI port on the 2018 Intel Mac mini, all M1 Macs (MacBook Pro 14" and 16", Mac Mini, Mac Studio), and the entry-level M2 Mac mini do not support DDC control. The README recommends using USB-C instead, or using BetterDisplay for full DDC control over HDMI. Some displays, notably EIZO, use MCCS over USB or a custom protocol, so they only get software dimming. DisplayLink docks and dongles do not allow DDC control on Macs. These are real constraints that affect a significant number of users. If you have one of those Macs or docks, MonitorControl will still work, but only with software dimming, which is less precise and may not adjust the actual backlight. This is a case where the tool is the wrong choice if you expect hardware-level control over HDMI on those machines. The documentation is honest about these gaps, which is a strength, but it also means you need to check your hardware before relying on it.

The Sequoia and Tahoe Crash Warning

The README states that macOS 27 Golden Gate compatibility requires MonitorControl v4.4.0 or newer. It also notes that current versions have limited native macOS OSD support on macOS Tahoe: although the Control Center brightness or volume OSD appears, the OSD percentage value will not show or update. This is a concrete limitation that users on Tahoe will face. The project is not archived, the latest release is v4.4.0 (September 2026), and the last push was in October 2026, so development is active.

Alternatives: BetterDisplay and the Trade-Offs

The README itself points to BetterDisplay as an alternative. It says BetterDisplay offers 'additional features, more advanced brightness control with XDR/HDR brightness upscaling and support for more Mac models and displays.' The key difference in approach is that BetterDisplay appears to have broader DDC support over HDMI, including on Macs where MonitorControl cannot do hardware control. BetterDisplay also goes beyond brightness and volume, with features like XDR/HDR brightness upscaling, which MonitorControl does not claim to have. The README says BetterDisplay offers full DDC control over HDMI for free on those Macs. This is a direct comparison: if you need HDMI DDC on unsupported Macs, or you want HDR brightness scaling, BetterDisplay is the more capable tool. MonitorControl's advantage is its simplicity and its focus on the core task, plus its native OSD integration, which BetterDisplay may handle differently. The choice depends on whether you hit MonitorControl's hardware limits.

Maintenance and License: What You Need to Know

MonitorControl is licensed under the MIT License, which is permissive and allows commercial use, modification, and redistribution. There are no copyleft obligations. The project is actively maintained, with a release in September 2026 (v4.4.0). The README notes that the app uses Sparkle for updates, which is a standard macOS auto-update framework. The build process requires SwiftLint, SwiftFormat, and BartyCrouch, which are development tools, not runtime dependencies. The runtime dependencies include MediaKeyTap, Settings, SimplyCoreAudio, KeyboardShortcuts, and Sparkle. For an end user, maintenance is low: you install the app and let Sparkle handle updates. For a developer who wants to fork or contribute, the codebase is Swift, and the README says to consult the maintainer before making fundamental changes. The project is open to pull requests, but the maintainer has sole discretion over acceptance. This is a standard open-source model, and the MIT license makes it safe to adopt for internal use.

Editorial conclusion

Adopt MonitorControl if you use a Mac with an external non-Apple display that supports DDC/CI over USB-C or DisplayPort, and you want hardware-level brightness and volume control with native OSD and keyboard shortcuts. Do not adopt it if you rely on the built-in HDMI ports of certain Macs (2018 Intel Mac mini, M1 Macs, entry-level M2 Mac mini) or if you use DisplayLink docks, where only software dimming is available. Before installing, verify your macOS version: for macOS 27 Golden Gate, v4.4.0 or newer is required, and on macOS Tahoe the native OSD percentage value will not show or update. Also check whether your display implements DDC/CI; if not, you will be limited to software dimming, which may be acceptable but is not true hardware control. For full DDC over HDMI on unsupported Macs or XDR/HDR brightness upscaling, consider BetterDisplay as a free alternative.

Frequently asked questions

Is MonitorControl free to use?

Yes. The feature list ends with Completely FREE, the repository ships an MIT License.txt, and both install routes are free: the .dmg from the releases page or `brew install --cask monitorcontrol`. The README also describes BetterDisplay as free when it points you there for HDMI control on M1 Macs.

how to use monitorcontrol

Copy the app from the .dmg into Applications and launch it, then adjust brightness with the keyboard or the menubar sliders. Settings opens from the menu, where you enable `Show advanced settings` for the deeper options and set custom shortcuts under Keyboard; the app uses Apple media keys by default.

Is monitor control safe to use?

The app asks to be added to Accessibility under System Settings, Privacy & Security, and the README says that grant is required only for the native Apple brightness and media keys. If you skip it, the menubar sliders still control your displays and only the key handling is unavailable.

monitorcontrol vs betterdisplay

The README names BetterDisplay as the place to go for XDR and HDR brightness upscaling, support for more Mac models and displays, and full DDC control over HDMI on M1 Macs, which MonitorControl does not support on the built-in port. @waydabber maintains MonitorControl and develops BetterDisplay.

monitorcontrol vs lunar

The credits name @alin23, who spearheaded M1 DDC support in MonitorControl, as the developer of Lunar.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/monitorcontrol-monitorcontrol.svg)](https://hysenlabs.com/projects/monitorcontrol-monitorcontrol)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/monitorcontrol-monitorcontrol.svg)](https://hysenlabs.com/projects/monitorcontrol-monitorcontrol)

Was this useful?