A small, fan-made Windows utility called Monarch is solving a surprisingly persistent pain point for multi‑monitor users: quickly disabling individual displays, saving and switching monitor profiles, and doing it all with keyboard shortcuts—features many people say should be part of PowerToys.
Background
Monitors are now used for many different workflows: multi‑screen productivity, streaming, VR passthrough, and competitive gaming. The diversity of uses has exposed a gap in Windows’ UX: turning a single external display on or off, or switching complex monitor layouts quickly and safely, still requires digging through Settings or unplugging cables. That friction matters for two practical reasons.
First, modern OLED and WOLED monitors remain vulnerable to localized wear when static UI elements sit on them for long periods. Even with manufacturer mitigations, users who keep static toolbars, HUDs, or side‑panels on a second screen worry about long‑term image retention or burn‑in.
Second, gamers and content creators often need to reconfigure displays on the fly (disable side monitors for fullscreen gaming, switch to a single focused display, or power down bright reference screens at night). Windows exposes some global modes, but per‑monitor, scriptable control has been limited—so small utilities and hobby projects are filling the gap.
Monarch entered that gap as a straightforward, focused tool: detach one or more monitors in software, save layouts as profiles, switch profiles quickly with hotkeys, and—critically—provide safe rollback mechanics to avoid leaving the user with a blank desktop. The tool landed attention after its developer posted on Reddit and the story was picked up by tech sites.
What Monarch does (and how it works)
Core features, at a glance
- Save and restore display topologies as profiles.
- Detach and reattach individual outputs in software (no cable changes).
- Assign global hotkeys to profiles or specific detaches for instant switching.
- Built‑in safety rollback: confirmations and auto‑revert if a change isn’t confirmed.
- Prevents disabling the last active display to avoid a black screen trap.
The technical mechanism: Display topology APIs
Monarch doesn’t need to physically switch cables; it operates by changing Windows’ display topology using the OS display configuration APIs. Those APIs—QueryDisplayConfig, SetDisplayConfig and related DisplayConfig functions—are the same system primitives used by Windows to enumerate displays and change which sources are routed to which targets. Changing topology in software typically causes the target monitor to enter standby because Windows stops sending video to it. That behavior is what Monarch leverages to make a monitor go “off” without touching power buttons.
VideoCardz’s coverage confirms that Monarch calls Windows’ display topology APIs to detach and reattach outputs, and notes that the developer added hotkey support in a recent update (v1.1.0). If you’re evaluating the tool, assume it’s modifying the same documented display topology state that other system utilities and the Windows Settings app rely on.
Why a tool like this matters (use cases)
1) Protecting OLED/WOLED monitors from static wear
There’s a very practical reason enthusiasts and professionals care about turning off an unused display: OLED pixels age with use, and static content accelerates local degradation. Even modern panels and firmware mitigations can’t eliminate
all risk—practical mitigation includes avoiding prolonged static images and lowering brightness. A simple way to reduce wear is to stop driving the panel when it’s not in use; Monarch automates that action.
2) Faster, less error‑prone workflow switching
For users who regularly switch between multi‑monitor workspaces, streaming rigs, and single‑monitor gaming, the ability to recall a layout by hotkey saves time and reduces mistakes. Instead of hunting for "Display settings" and clicking through menus, a single keypress can drop unnecessary monitors out of the topology and restore them later.
3) Night‑time comfort and power saving
Turning a bright reference monitor off when it’s not needed (but the machine is still active) makes late‑night work more comfortable and conserves a little power. For shared desks, it’s also less intrusive to colleagues.
4) Cleaner, cable‑free hardware switching
Many people swap between docked laptop and desktop modes or multiple PCs; Monarch’s approach avoids physically replugging cables or reaching behind a monitor to press a tiny power button.
Strengths: what Monarch gets right
- Single‑purpose focus. Monarch attacks one explicit problem instead of bloating a toolbox. That focus makes the UI and configuration straightforward for its audience.
- Safety-first defaults. The auto‑revert confirmation timer and the guardrail preventing disabling the last active display are practical, sensible protections—exactly the kind of defensive design you want for an app that can blind you if something goes wrong.
- Hotkey support. Adding global shortcuts makes the tool genuinely useful for gamers and power users who demand fast context switching without opening windows. VideoCardz confirmed hotkey support landed quickly after the initial release.
- Leverages documented APIs. By using Windows’ DisplayConfig APIs, the tool is doing topology changes the OS understands, rather than fragile hacks. That reduces the chance of short‑term breakage across Windows updates compared with more brittle approaches.
Risks and limitations — what to watch out for
- Trust and provenance. Any utility that manipulates system display topology and registers global hotkeys needs a trustworthy distribution channel and preferably open source code you can inspect. At time of publication, coverage references the app and a GitHub source, but users should verify the official repo and signed releases before running unsigned binaries on production systems. Treat anything that manipulates display hardware with caution.
- Edge cases with drivers and special targets. DisplayConfig functions behave differently depending on graphics drivers and connection types. Miracast sinks, docking stations, exotic multi‑GPU setups, or some virtual display drivers might not respond exactly the same as a simple HDMI/DP monitor, so expect variance in behavior on complex rigs. Microsoft’s docs document these nuances.
- HDR and color profile side effects. Toggling outputs or changing topology can interact with HDR and advanced color profiles that Windows associates with a particular display. The developer has noted that HDR toggling is possible but may have side effects because Windows sometimes reconfigures HDR state when displays are enabled or disabled—test carefully if you rely on calibrated color workflows.
- Potential for user error. Safety guards help, but a buggy update to any app that controls displays could leave a user with a blank console. Always test in a configuration where you can recover (secondary admin session, remote desktop to a different machine, or a short confirmation timeout). Monarch’s auto‑revert is a meaningful mitigation, but it’s not a substitute for careful testing.
How this compares to existing alternatives
- monoff / single‑purpose "turn off monitors" executables: Tools like monoff simulate idle or call power functions to turn off displays. They’re simple and portable, but they usually don’t provide profiles, selective per‑monitor detaches, or recovery guards. monarch targets the topology problem rather than just forcing displays to sleep.
- Windows built‑in options: Win+P presentation modes and the Display Settings UI let you change global modes or disconnect displays, but they’re slower for frequent, scripted switching and don’t support hotkeys for per‑monitor detach.
- PowerToys: already packs many quality‑of‑life utilities (FancyZones, Awake, Workspaces), but to date it hasn’t offered a per‑monitor detach hotkey. There is a longstanding community feature request to add a "turn off monitor" shortcut to PowerToys, which demonstrates user demand. If PowerToys added safe profile‑based detach/reattach, it would reach a much wider audience with Microsoft’s security posture.
Practical guide: testing Monarch safely (recommended checklist)
If you decide to try Monarch, follow this step‑by‑step to minimize risk:
- Verify the source.
- Locate the official repository or release channel and confirm the author (look for the developer’s name used in the Reddit post). Do not run random binaries from untrusted mirrors.
- Inspect the release artifacts.
- Prefer a signed installer or a release with reproducible build notes. If code is available, scan quickly for obvious network calls or telemetry. If you can’t review the code, run the binary in a sandbox or VM first.
- Create a recovery plan.
- Be comfortable with a second path to the machine (e.g., RDP from another machine, a keyboard to switch display modes, or a restore point). Confirm that your GPU drivers are up to date.
- Start with a benign test.
- Save a known good display layout. Detach a non‑critical external monitor and confirm it goes to standby. Wait for the confirmation timer to trigger and verify auto‑revert works.
- Test hotkeys and profiles.
- Configure a short‑timeout profile switch hotkey for a single secondary monitor first, then expand to multi‑monitor combos. Ensure hotkeys don’t conflict with existing global shortcuts.
- Monitor system behavior.
- Watch for driver messages, HDR toggles, or resolution changes. If you use color‑managed workflows, validate that reattaching restores color and HDR state as expected.
- If anything goes wrong:
- Use the recovery plan, or reboot if needed. Document the sequence that triggered the issue and report it to the developer with logs to help a safe bugfix.
Why PowerToys should consider adopting a similar utility
PowerToys is intentionally the home for small, well‑made utilities that fill gaps in Windows. Several arguments make a solid case for adding a
Monitor Profiles / Detach utility to PowerToys:
- User demand is real. Community requests for a shortcut to instantly turn off monitors date back years, and the immediate uptake of Monarch’s post shows this use case has wide appeal.
- It complements existing tools. PowerToys already includes utilities for multi‑monitor workflows (FancyZones, Workspaces) and power/state control (Awake). A monitored, signed PowerToys version would offer the same convenience while maintaining Microsoft’s supply‑chain trust model.
- Safety and discoverability. PowerToys can bake in best practices (confirmation timers, last‑display protection, clear UI) and provide telemetry‑free, audited code—important if the functionality becomes mainstream.
- Surface for expansion. A PowerToys tool could also provide advanced features like per‑profile HDR toggles, scheduling, and integration with Workspaces for a one‑click environment switch.
Responsible adoption — what Windows enthusiasts should demand
If this kind of utility is going to migrate from hobbyist to mainstream, a few conditions should be required:
- Open source or auditable builds. The community should be able to inspect the code path that manipulates topology and confirm there is no hidden telemetry or risky behavior.
- Signed releases and distribution through trusted channels. The easiest way to reduce user risk is to distribute via the Microsoft Store or a signed GitHub release with a clear maintainership history.
- Clear UI and defaults that favor safety. Confirmation timers, an opt‑out for auto‑revert, and blocked operations that would disable all displays should be the default.
- QA across driver stacks. The maintainers should test on Intel, AMD, and NVIDIA drivers, plus docking stations and wireless display targets, and document known limitations.
Final verdict: useful, practical, but proceed with care
Monarch is a textbook example of hobbyist ingenuity solving a targeted, real‑world problem. It takes a small, commonly‑needed operation—detaching a monitor—and turns it into a repeatable, keyboard‑driven workflow with sensible safety guards. That combination explains the immediate traction on Reddit and tech sites.
At the same time, anything that manipulates display topology deserves careful vetting. Users should verify the distribution, prefer signed or open builds, and test in a recoverable environment before trusting it on a main workstation. Given the demand and the clear UX win, this is exactly the sort of feature that would be more comfortable in the PowerToys ecosystem—if Microsoft decides to add a vetted, signed, and user‑friendly per‑monitor detach/profile tool to its official utilities, many users will be happier and safer for it.
Quick reference: alternatives and complements
- monoff and similar small utilities — fast, portable, but lack profiles and per‑monitor control.
- Windows built‑in: Win+P and Display Settings — reliable but slow for frequent switching.
- PowerToys: great for many workflows (FancyZones, Workspaces, Awake) but currently missing per‑monitor detach hotkeys.
If you install Monarch, test carefully, prefer auditable releases, and consider filing a feature request or PR to PowerToys if you want a native, signed implementation with the safety and discoverability benefits that come from an official Microsoft toolbox.
Source: XDA
This fan-made Windows monitor management tool should be in PowerToys