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.
Version 1.0rc2, additional downloads and versions on Releases page
Control RGB without wasting system resources
OpenRGB keeps it simple with a lightweight user interface that doesn't waste background resources with excessive custom images and styles. It is light on both RAM and CPU usage, so your system can continue to shine without cutting into your gaming or productivity performance.
Control RGB from a single app
If you have RGB devices from many different manufacturers, you will likely have many different programs installed to control all of your devices. These programs do not sync with each other, and they all compete for your system resources. OpenRGB aims to replace every single piece of proprietary RGB software with one lightweight app.
Contribute your RGB devices
OpenRGB is free and open source software under the GNU General Public License version 2. This means anyone is free to view and modify the code. If you know C++, you can add your own device with our flexible RGB hardware abstraction layer. Being open source means more devices are constantly being added!
Control RGB on Windows, Linux, and MacOS
OpenRGB runs on Windows, Linux and MacOS. No longer is RGB control a Windows-exclusive feature! OpenRGB has been tested on X86, X86_64, ARM32, and ARM64 processors including ARM mini-PCs such as the Raspberry Pi.
' Old (Early Binding - requires reference) Dim wdApp As Word.Application Set wdApp = New Word.Application
Last updated: March 2025
' New (Late Binding - no reference needed) Dim wdApp As Object Set wdApp = CreateObject("Word.Application") No reference required; works with any Office version. Cons: No IntelliSense; slightly slower; must declare all constants manually. Frequently Asked Questions Q: Can I just copy MSWORD.OLB from an old PC? A: Technically yes, but it must be registered ( regsvr32 rarely works for .olb files) and is a license violation unless you own Office 2007. Not recommended. Q: I need 12.0 for a legacy compiled EXE – what now? A: Run the EXE on a machine with Office 2007 installed, or use virtualization (e.g., Windows XP Mode with Office 2007). Q: Is there an official download from Microsoft? A: No. Microsoft does not offer individual object libraries for download. They are only distributed as part of the corresponding Office suite. Summary | If you… | Do this… | | :--- | :--- | | Control the source code | Upgrade reference to Word 16.0/14.0, or use late binding. | | Cannot change code | Install Office 2007 (virtual or physical). | | See a “download” website | Avoid it – likely malware or illegal. | Need further help? Check your project’s compatibility with newer Office versions using Microsoft’s Office Primary Interop Assemblies (for .NET). microsoft word 12.0 object library download
You can copy and paste this directly onto a website, forum, or internal IT wiki. Applies to: Visual Basic for Applications (VBA), VB6, VB.NET, and older automation projects. The Problem You open an older VBA project (in Excel, Access, or Visual Studio) and see a broken reference marked "MISSING: Microsoft Word 12.0 Object Library" . Your code won't compile, and features like Word.Application or Document objects fail. ' Old (Early Binding - requires reference) Dim wdApp As Word