You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
morg aafac9862a Add HyperX Pulsfire mousemat support 5 hours ago
.github Create FUDING.yml for GitHub 2 years ago
.gitlab Rework and fix Polychrome v1 controller 3 months ago
AutoStart FreeBSD: Fix compilation 3 months ago
Controllers Add HyperX Pulsfire mousemat support 5 hours ago
RGBController Adding DEVICE_TYPE_ACCESSORY to enum 1 month ago
debian debian: Adding qttools5-dev-tools to build deps 3 months ago
dependencies Update hidapi to version 0.12.0. Direct mode stabilization of Logitech G203 Lightsync (fixes #877). 1 month ago
fedora Adding i18n resource file generation into .pro 4 months ago
i2c_smbus AMD ADL SMBus improvements 1 day ago
i2c_tools Add i2c tool for reading multiple bytes from an SMBus device register 2 years ago
net_port SDK Listening Options 3 months ago
pci_ids Initial commit for KFA2 RTX 2080 Super EX OC 1 day ago
qt Fix warning in OpenRGBNanoleafScanningThread.cpp 2 weeks ago
scripts Adjusting for website deployment 18 hours ago
serial_port Add support for BlinkyTape LED controllers 1 year ago
super_io Initial commit for Gigabyte Super-IO motherboard controller (X570-UD) 2 weeks ago
wmi Attempt to fix Qt file dialog issue in Windows 1 year ago
.editorconfig Inital commit to .editorconfig file 7 months ago
.gitignore Update .gitignore to include *.qrc files related to i18n update 4 months ago
.gitlab-ci.yml Fixing regression bug caused by DELIMITER change in the supported devices script 1 month ago Change Non-Mainline pipelines to be manually triggered 3 months ago
Colors.h Add Electric Ultramarine color 9 months ago
Detector.h Add I2C PCI detector type for registering GPU detectors, update Gigabyte RGB Fusion GPU controller to use it 4 months ago
DeviceDetector.h Add I2C PCI detector type for registering GPU detectors, update Gigabyte RGB Fusion GPU controller to use it 4 months ago
LICENSE Add LICENSE 4 years ago
LogManager.cpp Add LL_DIALOG log level, which can trigger the GUI to show a message box containing the log message 11 months ago
LogManager.h Correct type casting on log prints 4 months ago
NetworkClient.cpp Fix MacOS warning in NetworkClient.cpp 2 weeks ago
NetworkClient.h SDK Listening Options 3 months ago
NetworkProtocol.cpp Initial network files 2 years ago
NetworkProtocol.h SDK Listening Options 3 months ago
NetworkServer.cpp Fixing MacOS / Clang builds 3 months ago
NetworkServer.h SDK Listening Options 3 months ago
OpenRGB.h Rename OpenAuraSDK.cpp to OpenRGB.cpp and remove old unused code 3 years ago
OpenRGB.patch Add timeouts to i2c-nct6775 driver and fix kernel segfault caused by byte access with no data 3 years ago Fix multiply defined warnings in CorsairPeripheralV2Devices controller 2 weeks ago
OpenRGBPluginInterface.h Update plugin API to version 2, add unregister functions for all ResourceManager callbacks 9 months ago
PluginManager.cpp Normalising config directory to ensure it has trailing path separator resolving #2552 3 months ago
PluginManager.h Normalising config directory to ensure it has trailing path separator resolving #2552 3 months ago
ProfileManager.cpp Fix profile not being applied when I2C bus ID changes on reboot 5 days ago
ProfileManager.h Fixing profile loading #1135 2 years ago Adding `qt5-linguist` to Fedora build dependencies 2 months ago
ResourceManager.cpp Normalising config directory to ensure it has trailing path separator resolving #2552 3 months ago
ResourceManager.h Add I2C PCI detector type for registering GPU detectors, update Gigabyte RGB Fusion GPU controller to use it 4 months ago
SettingsManager.cpp Add error logs for non logged exceptions 7 months ago
SettingsManager.h Initial commit for Plugins 2 years ago
cli.cpp Fix warnings in cli.cpp 7 days ago
filesystem.h Adding test stages to Linux builds 1 year ago
main.cpp Adding `en_AU` and `en_GB` locales to resolve #2500 2 months ago

Visitors Pipeline Status

Visit our website at!

One of the biggest complaints about RGB is the software ecosystem surrounding it. Every manufacturer has their own app, their own brand, their own style. If you want to mix and match devices, you end up with a ton of conflicting, functionally identical apps competing for your background resources. On top of that, these apps are proprietary and Windows-only. Some even require online accounts. What if there was a way to control all of your RGB devices from a single app, on both Windows and Linux, without any nonsense? That is what OpenRGB sets out to achieve. One app to rule them all.


  • Set colors and select effect modes for a wide variety of RGB hardware
  • Save and load profiles
  • Control lighting from third party software using the OpenRGB SDK
  • Command line interface
  • Connect multiple instances of OpenRGB to synchronize lighting across multiple PCs
  • Can operate standalone or in a client/headless server configuration
  • View device information
  • No official/manufacturer software required
  • Graphical view of device LEDs makes creating custom patterns easy

Supported Devices



This project interacts directly with hardware using reverse engineered protocols. While we do our best to make sure we're sending the right data, there is always some risk in sending data to hardware when we don't understand exactly how that hardware works.

There have been two instances of hardware damage in OpenRGB's development and we've taken precautions to prevent it from happening again.

  • The Mystic Light motherboard code bricked the RGB controller of some MSI motherboards. The code was disabled and reworked. We have been re-adding these motherboards to the support list as we verify that the new code works with them. Affected boards can be unbricked with a Nuvoton Nu-Link adapter.
  • There were reports of bricked Gigabyte Aorus Z390 motherboards caused by dumping SMBus address 0x68 in an attempt to reverse engineer the RGB. Due to this, the SMBus Tools page on OpenRGB is hidden by default now as it has no real use to non-developers.



  • You will need the Microsoft Visual 2019 C++ runtime installed. You can get it here
  • Pre-built Release binaries are available for Windows 10 / 11 64bit under the Releases section on GitLab.
  • If you want to test the latest (potentially unstable) code you can also get the Windows package from the pipeline builds.
  • To build the application yourself on Windows:
    1. Download the latest Visual Studio Community Edition and Qt Creator.
    2. Open the project in Qt Creator.
    3. Use the MSVC compiler kit, either 32- or 64-bit, to build the application.
    4. Run the project from Qt Creator. If you want to use your custom build standalone, download the latest matching Release package and replace the OpenRGB.exe in it with your new build.

SMBus Access

  • You must run the application as Administrator the first time to allow WinRing0 to set up. It can be run as a normal user afterwards
  • Early versions of OpenRGB used InpOut32. This is no longer needed and should be removed to avoid warnings by some anti-cheat software. You can uninstall Inpout32 by following the instructions here.

USB Access

  • Early versions of OpenRGB used the WinUSB driver, installed using Zadig. This is no longer required, and you need to uninstall the WinUSB driver if you previously installed it. You can uninstall the WinUSB driver by following this guide.


Debian / Ubuntu
  • OpenRGB builds an official Debian package for Bullseye and Ubuntu 21.04 onwards for both the 64bit release and pipeline builds
  • There is also a legacy package for Debian 64bit Buster and it's derivatives (Ubuntu prior to 21.04) with release and pipeline builds
  1. Install build dependencies
    • sudo apt install git build-essential qtcreator qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools libusb-1.0-0-dev libhidapi-dev pkgconf libmbedtls-dev
  2. git clone
  3. cd OpenRGB
  4. qmake
  5. make -j$(nproc)
  6. You can then run the application from the compile directory with ./openrgb or install with make install
  7. You will also need to install the latest UDEV rules.
  • You can also build a Debian package (.deb) from this source code with dpkg-buildpackage -us -B
    • Building a Debian package requires debhelper to be installed: sudo apt install debhelper
  • OpenRGB builds an official Fedora 35 and 36 package for both the release and pipeline builds
  1. Install build dependencies
    • sudo dnf install automake gcc-c++ qt5-qtbase-devel qt5-linguist hidapi-devel libusbx-devel mbedtls-devel
  2. git clone
  3. cd OpenRGB
  4. qmake-qt5
  5. make -j$(nproc)
  6. You can then run the application from the compile directory with ./openrgb or install with make install
  7. You will also need to install the latest UDEV rules.

SMBus Access

  • SMBus access is necessary for controlling RGB RAM and certain motherboard on-board LEDs.

  • If you are not trying to use OpenRGB to control RGB RAM or motherboard LEDs, you may skip this section.

  • ASUS and ASRock motherboards have their RGB controller on a secondary SMBus interface and requires a Linux kernel > 5.7 commit

  • Allowing access to SMBus:

    1. Load the i2c-dev module: sudo modprobe i2c-dev
    2. Load the i2c driver for your chipset:
    • sudo modprobe i2c-i801
    • sudo modprobe i2c-nct6775 - Secondary controller for motherboard LEDs (requires kernel patch)
    • sudo modprobe i2c-piix4
    • Unmodified kernel will have one interface, patched kernel will have two. The first at 0x0B00 and the second at 0x0B20. The 0x0B20 interface is for motherboard LEDs.

  • You'll have to enable user access to your SMBus if you don't run as root.

    • List all SMBus controllers: sudo i2cdetect -l
    • Note the number for PIIX4, I801, and NCT6775 controllers.
    • Give user access to those controllers. If you have not installed OpenRGB from a package (e.g. deb, RPM or from the AUR) then most likely you need to install the UDEV rules.
  • The i2c-nct6775 kernel module requires patching, please refer to instructions here

  • Some Gigabyte/Aorus motherboards have an ACPI conflict with the SMBus controller. Please add a kernel parameter to resolve this conflict.

USB Access

  • USB devices require udev rules to access as a normal user.
  • Alternatively you can run OpenRGB as root to detect all USB devices. (Not recommended)
  • USB based Gigabyte AORUS motherboards may also have an ACPI conflict. Please add a kernel parameter to resolve this conflict.

Installing UDEV rules manually

  • If you have installed OpenRGB from a package then latest UDEV rules are installed locally at /usr/lib/udev/rules.d/60-openrgb.rules
  • Flatpak and Appimage "packages" will need to install this file manually.
  • Udev rules are built from the source at compile time. When building locally they are installed with the make install step to /usr/lib/udev/rules.d/60-openrgb.rules
  • If you need to install the UDEV rules file manually you can also download the latest compiled udev rules from Gitlab.
    • Copy this 60-openrgb.rules file to /usr/lib/udev/rules.d/
    • Then reload rules with sudo udevadm control --reload-rules && sudo udevadm trigger

Kernel Parameters

  • To resolve an ACPI conflict add the acpi_enforce_resources=lax kernel parameter.

  • If you want to check if the kernel was loaded with this option you can execute this command from the terminal once you've rebooted.

    • cat /proc/cmdline
    • Please see the Arch wiki for details on how to update your bootloader.
    Debian / Ubuntu
    • On Fedora, install grubby and then following command: grubby --update-kernel=ALL --args="acpi_enforce_resources=lax"
    • For more information please refer to the Fedora docs for grubby.


  • Pre-built binaries in zipped application package format are available under the Releases section on GitLab.
  • You can build the project using Qt Creator or on the command line.
    1. Install build dependencies with Homebrew
      • Install Homebrew by following the instructions at
      • brew install git qt5 hidapi libusb mbedtls@2
      • brew link qt5
    2. Create a local certificate called OpenRGB with code signing capability
    3. git clone
    4. cd OpenRGB
    5. qmake
    6. make -j8
    7. macdeployqt -codesign=OpenRGB
    8. Copy the application package to Applications

SMBus Access

  • For Intel devices using a controller in the I801 family you have to download and install the macUSPCIO driver

USB Access

  • USB devices may require the Input Monitoring permission. You can add OpenRGB in System Preferences > Security & Privacy > Privacy.

Join Our Discord

Visit Our Subreddit

How-Tos and FAQs

Support OpenRGB

  • OpenRGB is a project I created to solve a problem I had with the RGB ecosystem. My goal isn't to make money off of this project. That said, people have requested to donate, and donations allow me to buy more RGB stuff to reverse engineer.
  • Donate via PayPal
  • Become a Patron (I'm not doing any Patreon-exclusive content, it's purely for donation)
  • Donate via Bitcoin: 1N83YPu7btXYadPS1neB9zX7X1QTdpyZQ

History of OpenRGB

  • OpenRGB is a continuation of OpenAuraSDK, which itself was created out of reverse engineering work done on the Keyboard Visualizer project. For a complete history of the RGB projects that led to OpenRGB's creation, see the History page.


  • Want to contribute support for a new device? Check out the RGBController API page for documentation of how OpenRGB implements device control.
  • Want to create a new OpenRGB SDK client implementation? Check out the OpenRGB SDK Documentation page for documentation of how the OpenRGB SDK network protocol functions.
  • Please read the Contributing Guidelines before starting work on your new changes.


Applications Supporting OpenRGB SDK

OpenRGB Plugins

Projects Used

Projects Researched

While no code from these projects directly made its way into OpenRGB, these projects have been invaluable resources for protocol information.