Monitorian is a Windows desktop tool to adjust the brightness of multiple monitors with ease.
The user can change the brightness of monitors, including external ones, either individually or in unison. For the system with an ambient light sensor, the adjusted brightness can be shown along with configured one.
In addition, the user can change the adjustable range of brightness and contrast for each monitor seamlessly.
If you wish to place executable files on your own, you can extract them from installer file (.msi) by the following command:
msiexec /a [source msi file path] targetdir=[destination folder path (absolute path)] /qn
In such case, please note the following:
[system drive]\Users\[user name]\AppData\Local\Monitorian\
Add-on features are available for Microsoft Store version on a subscription basis.
You can use command-line options to get/set the brigtness.
|Get brightness of a monitor.||/get|
|Get brightness of a specified monitor.||/get [Device Instance ID]|
|Get brightness of all monitors.||/get all|
|Set brightness of a monitor.||/set [Brightness]|
|Set brightness of a specified monitor.||/set [Device Instance ID] [Brightness]|
|Set brightness of all monitors.||/set all [Brightness]|
If this app is called with
/get option, it will return [Device Instance ID] [Monitor name] [Brightness]. The device instance ID is an unique identifier given by the OS to each monitor. The brightness ranges from 0 to 100%. It can be specified with brightness itself (e.g. 20), increase (e.g. +10) or decrease (e.g. -10) when you use
You can call this app by its name
Monitorian in command prompt or bat file. From Task Scheduler, it can be performed by the path to its alias
%LOCALAPPDATA%\Microsoft\WindowsApps\Monitorian.exe. For example, to increase brightness of all monitors by 30%, the Action will be the following:
The code for add-on features is not included in this repository.
This app is a WPF app developed and tested with Surface Pro 4 and 7.
The controllability of an external monitor depends on whether the monitor successfully responds to DDC/CI commands. Even if a monitor is expected to be DDC/CI compatible, it may fail to respond (a) if the monitor is weird, (b) if its connection to the system is problematic, or (c) when the system starts or resumes. If an issue is case (a) or (b), this app cannot help it. If case (c), this app may be able to handle it.
In any case, reporting on the controllability of a monitor MUST include probe.log and operation.log described below. The logs will be the starting point to look into the issue.
Probe into monitorsin the hidden menu described below.
Rescan monitorsin the hidden menu. A system sound will be played when completed.
Make operation login the hidden menu. After that, operation.log can be copied by
Copy operation log.
Command-line argumentsin the hidden menu. They will be tested along with current arguments when this app starts.
|.NET Framework 4.8 SDK
.NET Framework 4.8 targeting pack
|Windows 10 SDK (10.0.19041.0)||TargetPlatformVersion|
/Source/Monitorian.sln. Then go to the solution explorer and right click the solution name and execute
Restore NuGet Packages.
An alternative language can be shown by adding a Resources (.resx) file into
/Source/Monitorian.Core/Properties folder. Each Resources file stores name/value pairs for a specific language and will be selected automatically depending on the user's environment.
Resources.resxfile to override it.
Ver 3.5 2021-9-9
Ver 3.4 2021-8-30
Ver 3.3 2021-8-20
Ver 3.2 2021-8-9
Ver 3.1 2021-8-4
Ver 3.0 2021-7-1
Ver 2.19 2021-6-16
Ver 2.18 2021-5-23
Ver 2.17 2021-5-19
Ver 2.16 2021-4-11
Ver 2.14 2021-3-26
Ver 2.13 2021-2-13
Ver 2.11 2021-1-26
Ver 2.9 2020-12-22
Ver 2.8 2020-11-23
Ver 2.7 2020-10-30
Ver 2.6 2020-8-10
Ver 2.5 2020-8-1
Ver 2.4 2019-12-30
Ver 2.3 2019-11-28
Ver 2.2 2019-11-18
Ver 2.1 2019-11-6
Ver 2.0 2019-8-6
Ver 1.12 2019-3-9
Ver 1.11 2019-2-7
Ver 1.10 2019-2-3
Ver 1.9 2018-12-5
Ver 1.8 2018-11-24
Ver 1.7 2018-8-22
Ver 1.6 2018-5-25
Ver 1.5 2018-2-12
Ver 1.4 2018-1-17
Ver 1.2 2017-10-12
Ver 1.0 2017-2-22