PowerToys already solves dozens of small-but-annoying Windows problems for power users, and the five wishlist items proposed by the community capture practical, high-impact improvements that could make the suite even more indispensable. (learn.microsoft.com)
PowerToys began life as a set of handy utilities for power users and has been steadily refined and expanded under Microsoft's stewardship into a modular, open-source toolkit for Windows. It now includes utilities such as FancyZones, PowerToys Run (the Command Palette), Image Resizer, Text Extractor, and a growing set of mouse and display helpers—tools that fill real gaps in Windows’ stock feature set. (learn.microsoft.com)
An xda-developers feature recently laid out five practical enhancements its author would like to see added to PowerToys: tighter integration between Workspaces and PowerToys Run, a lightweight image-format converter in Explorer, an automatic/interval screenshot tool, universal remapping for extra mouse buttons, and built-in external monitor controls (DDC/CI brightness/contrast). The suggestions are rooted in typical power-user workflows: fast keyboard-driven context switching, quick file-format tweaks, unattended capture for live events, reducing vendor lock-in from OEM mouse utilities, and ditching third-party monitor tools for native support.
This article explains why those five features make sense, what PowerToys already provides today, the technical constraints and opportunities for each request, and practical alternatives in the near term.
If Microsoft and the PowerToys community prioritize the features above in that order, users will get meaningful productivity and usability wins without bloating the suite—while PowerToys retains the focus and clarity that made it popular in the first place. (learn.microsoft.com) (learn.microsoft.com) (github.com) (twinkletray.com)
Source: xda-developers.com PowerToys is amazing, but it could be even better with these 5 features
Background / Overview
PowerToys began life as a set of handy utilities for power users and has been steadily refined and expanded under Microsoft's stewardship into a modular, open-source toolkit for Windows. It now includes utilities such as FancyZones, PowerToys Run (the Command Palette), Image Resizer, Text Extractor, and a growing set of mouse and display helpers—tools that fill real gaps in Windows’ stock feature set. (learn.microsoft.com)An xda-developers feature recently laid out five practical enhancements its author would like to see added to PowerToys: tighter integration between Workspaces and PowerToys Run, a lightweight image-format converter in Explorer, an automatic/interval screenshot tool, universal remapping for extra mouse buttons, and built-in external monitor controls (DDC/CI brightness/contrast). The suggestions are rooted in typical power-user workflows: fast keyboard-driven context switching, quick file-format tweaks, unattended capture for live events, reducing vendor lock-in from OEM mouse utilities, and ditching third-party monitor tools for native support.
This article explains why those five features make sense, what PowerToys already provides today, the technical constraints and opportunities for each request, and practical alternatives in the near term.
1) Workspaces + PowerToys Run: what’s missing and why it matters
Current behavior and limits
PowerToys’ Workspaces utility captures your current desktop (open apps and window positions) and lets you save that snapshot for later recall. It’s designed to restore an entire workflow—apps, their command-line arguments, and approximate placement—so you can jump into a consistent environment for a project. Workspaces can be launched from the PowerToys settings editor or via desktop shortcuts you create in the Workspaces editor. However, Workspaces does not currently expose a simple text-based launcher entry you can invoke and type to call a named workspace from the keyboard. That makes switching less fluid than it could be for keyboard-first users. (learn.microsoft.com)Why PowerToys Run integration is the logical next step
PowerToys Run (the Command Palette) is a keyboard-first launcher similar to macOS Spotlight. Integrating Workspaces into PowerToys Run—so you can type a workspace name, press Enter, and have PowerToys restore the saved layout—delivers immediate, measurable productivity gains:- Instant workspace switching without mouse navigation or opening the Workspaces editor.
- Shorter mental context switches when moving between tasks: one keystroke to go from “email + Slack + browser” to “IDE + terminal + docs.”
- Allows for global hotkey or fuzzy search to find and launch named setups.
Feasibility notes and design suggestions
- Expose each saved workspace as a searchable Command Palette item (name + optional tag).
- Allow Run to show launch status and optionally suppress visible window shuffling with a “quiet restore” attempt (best-effort: some apps refuse to accept programmatic placement).
- Support workspace aliases and keyboard-only creation: “Create workspace from current desktop — assign name” via the Command Palette.
- Consider a simple “switch-to” behavior that, when Workspaces is set to “use existing windows,” will move existing windows into the workspace layout instead of launching new instances—useful when toggling between active work contexts.
2) Lightweight image-format converter (PNG → JPG → WebP) in Explorer
The gap today
PowerToys’ Image Resizer is excellent for batch resizing from the Explorer context menu, but it’s not a dedicated file-type conversion tool. The Image Resizer docs explicitly state it is “not a file type conversion tool” and that the fallback encoder exists only for unsupported formats. If your goal is simply to change format (for smaller file size or compatibility), Image Resizer forces you into resizing workflows or fiddly encoder fallback settings rather than offering a single “Convert to …” command. This is a frequent ask from users who just need fast format conversion from the right-click menu. (learn.microsoft.com)Why a small converter belongs in PowerToys
- Format conversion is a low-friction, frequently repeated task (PNG → JPG to save upload time; JPG → WebP for modern web optimization).
- PowerToys already extends Explorer with context-menu tools (Image Resizer, PowerRename); a “Convert image format” entry would be consistent.
- A tiny tool that supports lossless/lossy choices, basic quality slider, and batch operation would save a surprising amount of time over launching an image editor or using web tools.
Recommended feature set (minimal viable product)
- Context menu entry: “Convert images → JPG / PNG / WebP / TIFF”.
- Optional quality slider for lossy targets (e.g., JPG quality 1–100).
- Batch support and ability to overwrite or create “converted” sibling files.
- Preserve metadata toggle (EXIF).
- Command-line support for scripting or automation.
Implementation considerations
Image encoding is handled by the Windows Imaging Component (WIC) and other available codecs, so PowerToys could safely reuse existing system encoders and third-party open libraries (libwebp) when necessary. The UI should be intentionally minimal—no need to match Photoshop—just a right-click quick action with a settings page for defaults. Microsoft docs for Image Resizer already clarify the tool’s encoder behavior, so the new converter should avoid confusing overlap with Image Resizer by strictly being a format conversion utility. (learn.microsoft.com)3) Automatic/interval screenshots: a niche but valuable power-user tool
Use cases and current tooling
Some workflows—live event coverage, long-running captures of dynamic UIs, or game stream clipping—benefit from periodic screenshots saved automatically to disk or an upload target. PowerToys does not provide an “automatic screenshot every N seconds” tool, and the Snipping Tool’s feature set focuses on manual captures, delayed snips, and video snips; it does include an autosave behavior for certain actions but not interval capture. Third-party utilities (Automatic Screenshotter, various scripting tools) fill this niche today. (support.microsoft.com)Why PowerToys should add it
- PowerToys targets edge-case power workflows; interval screenshotting fits that remit cleanly.
- Having an “Auto Snap” utility with safe defaults (auto-save to folder, configurable interval, exclusion list for apps) reduces reliance on ad-supported or abandoned third-party tools.
- Integration with the PowerToys settings ecosystem allows easy hotkeys, exclude-app lists, and a single place to manage capture behaviors.
Security and storage considerations
- Default to local save in a single “PowerToys AutoSnaps” folder with clear naming (timestamped), and an option to overwrite older captures to avoid disk bloat.
- Include an exclude-apps list so privacy-sensitive apps (banking windows, password managers) are omitted.
- Warn users about potential copyright and privacy implications of unattended capture in the UI.
Design outline
- On/Off toggle in PowerToys settings.
- Interval selector (1s–60s typical), capture mode (fullscreen/window/region), and target folder.
- Auto-upload integration hook (optional) so teams can push captures to a network share or cloud folder.
- Visual indicator and hotkey to pause/resume.
4) Mouse button customization: replace vendor baggage with a universal mapper
The problem vendors create
Many high-end mice expose additional buttons (side buttons, thumb buttons, extra programmable keys) and ship vendor-specific configuration utilities (Logi Options+, Razer Synapse, Corsair iCUE). Those apps are often heavy, always-running, and tied to a specific vendor or product generation. Users who want a lightweight way to map extra buttons to actions—launch apps, trigger shortcuts, or send macros—often end up installing proprietary software they’d prefer to avoid. GitHub feature requests for a dedicated mouse button remapper in PowerToys have run for years, showing clear user demand. (github.com)Why a PowerToys mouse remapper makes sense
- PowerToys already includes a Keyboard Manager and many input-focused utilities. Extending that approach to mouse buttons is a natural extension.
- A cross-vendor remapper reduces the need for multiple vendor utilities and keeps configuration centralized and portable.
- A reasonably scoped module would cover common needs for most users: remapping forward/back, mapping thumb buttons to keyboard shortcuts, application-specific profiles.
Practical feature list (v1)
- Detect mouse buttons through standard API (Raw Input / Windows Raw Input + HID).
- Map common extra buttons (XButton1, XButton2, wheel click, side buttons) to:
- Keyboard key or key combination
- Launch app / file
- Send multimedia control (play/pause, next)
- Per-application profiles (optional), and a global default.
- Lightweight background service with minimal CPU/memory footprint.
Limitations and pitfalls
- Some gaming mice implement proprietary protocols and drivers that intercept or transform HID reports and may hide raw button events from user-space, making universal mapping impossible for certain models.
- Full macro and lighting integration (what Razer/Corsair offer) is out of scope; PowerToys should favor stability and minimalism.
- The PowerToys dev team has acknowledged this demand on the official issue tracker; the feature is non-trivial because of the variety of mouse HID implementations, but it’s technically doable for the common button set. (github.com)
5) Monitor controls: backlight, contrast, and power state for external displays
The longstanding Windows shortfall
Windows historically manages brightness for built-in laptop panels natively but relies on hardware/driver/OEM cooperation for external displays. That inconsistency means many users cannot control external monitor brightness from Windows without vendor tools or third-party DDC/CI apps. Community tools such as Twinkle Tray, Monitorian, and ClickMonitorDDC exist because this feature remains fragmented across displays, drivers, and connectors. Microsoft’s driver documentation shows that enabling OS-level control for external connectors requires OEM or driver-level support and special INF entries—Windows cannot magically adjust an arbitrary external monitor without cooperation from hardware, driver, or DDC/CI support. (learn.microsoft.com)Why PowerToys should include monitor controls
- For users with DDC/CI-enabled monitors—most modern displays—PowerToys could provide a user-friendly tray slider and hotkeys to adjust brightness, contrast, and power state, matching what Twinkle Tray and Monitorian already offer.
- Integrating a monitor control module into PowerToys gives a safer, community-vetted alternative to third-party utilities, with Microsoft backing and updates through the PowerToys release cadence.
- PowerToys could add a “normalize brightness across displays” feature and scheduled brightness adjustments (e.g., lower brightness after hours).
Technical reality check
- DDC/CI is the routinely used protocol for adjusting monitor VCP (virtual control panel) values such as brightness (VCP code 0x10), contrast (0x12), and power (0xD6 for some displays). Tools like Twinkle Tray and Monitorian use DDC/CI to talk to monitors; PowerToys could too. But DDC/CI works only when:
- The monitor supports DDC/CI and has it enabled in its OSD.
- The connection path (dock, adapter) allows DDC/CI traffic (some USB-C docks or adapters block it).
- Drivers and graphics stack do not interfere with DDC commands.
- Some older dedicated tools (ClickMonitorDDC) have seen abandonment or become hard to find, underscoring the benefit of putting a maintained, Microsoft-backed solution into PowerToys instead of leaving users dependent on single-developer apps. However, claims about a specific project's continued availability should be checked at the time of use—the landscape changes. (twinkletray.com)
Suggested PowerToys monitor module behavior
- Discover displays and indicate DDC/CI support per monitor.
- Per-monitor sliders for brightness and contrast in the tray; optional global slider.
- Hotkey bindings for step-up / step-down brightness.
- Advanced: a command-line / URI handler so other apps / scripts can request changes (useful for scripts or Scheduled Tasks).
- Expose a log for failed commands to help users troubleshoot connection/adapter limitations.
Strengths of the proposal — why these five are smart bets
- Each feature is tightly scoped, addresses real user friction, and builds on what PowerToys already does well: lightweight, modular utilities that extend Explorer and the UI without heavy system intrusion.
- All five features are compatible with PowerToys’ open-source, community-driven development model; they can be iterated in preview and improved based on telemetry and user feedback.
- They reduce dependence on closed, vendor-specific apps (mouse and monitor controls) and on ad-hoc third-party utilities (automatic screenshotters and image converters), improving security and user experience.
Risks, trade-offs, and technical caveats
- Hardware variability: Mouse remapping and monitor DDC/CI control will not work universally—some devices and docking chains block necessary signals or expose only vendor-layered interfaces. Any PowerToys implementation must clearly communicate supported/unsupported cases, provide troubleshooting guidance, and allow graceful failure. (github.com)
- Overlap and confusion: Image Resizer vs. Image Converter might create overlapping UI if not carefully designed; the product should keep responsibilities clear (resizer = size/scale; converter = file format).
- Security and privacy: Automatic screenshotting raises privacy risks; the tool must default to safe settings, include an exclude list, and present explicit warnings for continuous capture.
- Complexity vs. bloat: One PowerToys virtue is its lean, focused utilities. It’s important not to let PowerToys balloon into a bloated “catch-all” system utility suite. Each new module should remain simple, with opt-in activation and clear settings.
Short-term workarounds and alternatives
- If you need quick conversion today: small context-menu utilities or lightweight command-line tools (ImageMagick, Windows built-in codecs) can batch-convert images with a single command; many PowerToys users use ImageMagick from the terminal or scripts while waiting for a native converter. For most users, a tiny one-click shell extension remains the easiest path.
- For mouse remapping now: vendor utilities remain the most feature-complete solution for complex macro lighting and per-game profiles; for simpler remaps, scripting tools like AutoHotkey can intercept and remap many mouse events.
- For monitor brightness: Twinkle Tray, Monitorian, and other DDC/CI apps are mature, free options that already implement the expected behavior; PowerToys adopting a similar model would reduce fragmentation and create a single maintained alternative. (twinkletray.com)
- For auto screenshots: several small apps (Automatic Screenshotter, scriptable PowerShell tools, OBS automated saving for video frames) can be used; but a PowerToys feature would centralize settings and better respect excluded apps and privacy.
Roadmap-style recommendations for PowerToys devs
- Prioritize PowerToys Run + Workspaces integration: low UI friction, high productivity gain, modest engineering scope.
- Add a lightweight Explorer image-format converter (simple UI, encoder chooser) as a sibling to Image Resizer.
- Prototype a “Auto Snaps” module behind a feature flag—test privacy defaults and disk-control safeguards.
- Begin a phased mouse remapper: v1 covers common extra buttons to key/macro mapping and per-app profiles; v2 can expand based on hardware telemetry.
- Deliver a monitor control module that detects DDC/CI capability, offers sliders, and logs failures with clear troubleshooting guidance.
Conclusion
PowerToys’ current trajectory—fast iteration, close community feedback, and a modular architecture—makes it the ideal home for these five improvements. Integrating Workspaces with PowerToys Run would be the quickest win for keyboard-first workflows; a small image converter and an auto-screenshot tool would resolve everyday friction that currently forces users into third-party tools; and mouse- and monitor-control modules would erase long-standing hardware vendor lock-in problems that frustrate power users. Each suggestion fits PowerToys’ ethos: solve niche, recurring pains with lightweight, transparent tools.If Microsoft and the PowerToys community prioritize the features above in that order, users will get meaningful productivity and usability wins without bloating the suite—while PowerToys retains the focus and clarity that made it popular in the first place. (learn.microsoft.com) (learn.microsoft.com) (github.com) (twinkletray.com)
Source: xda-developers.com PowerToys is amazing, but it could be even better with these 5 features
