# \[GUIDE\] How to install OpenRGB on FW16

**URL:** <https://community.frame.work/t/guide-how-to-install-openrgb-on-fw16/53358>\
**Category:** Framework Laptop 16\
**Tags:** framework-laptop-16-amd-7040\
**Created:** [June 21, 2024, 7:30pm UTC](https://community.frame.work/t/guide-how-to-install-openrgb-on-fw16/53358 "2024-06-21T19:30:47Z")\
**Posts on this page:** 8\
**Page:** 3

<div class="post-metadata">

**Author:** ![tagno25](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tagno25/32/28302_2.png) [@tagno25](https://community.frame.work/u/tagno25)\
**Post date:** [December 18, 2025, 6:41am UTC](https://community.frame.work/t/guide-how-to-install-openrgb-on-fw16/53358/41 "2025-12-18T06:41:57Z")

</div>

I have created a release ([v0.3.1](https://github.com/tagno25/qmk_firmware/releases/tag/v0.3.1)) on Github with pre-compiled u2f files that are compatible with the current BIOS release.

---

<div class="post-metadata">

**Author:** ![chet\_merrier](https://avatars.discourse-cdn.com/v4/letter/c/4bbf92/32.png) [@chet\_merrier](https://community.frame.work/u/chet_merrier)\
**Post date:** [December 19, 2025, 4:58am UTC](https://community.frame.work/t/guide-how-to-install-openrgb-on-fw16/53358/42 "2025-12-19T04:58:36Z")

</div>

Thank you working great.

---

<div class="post-metadata">

**Author:** ![Eli\_Spizzichino](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/eli_spizzichino/32/43996_2.png) [@Eli\_Spizzichino](https://community.frame.work/u/Eli_Spizzichino)\
**Post date:** [January 19, 2026, 3:31pm UTC](https://community.frame.work/t/guide-how-to-install-openrgb-on-fw16/53358/43 "2026-01-19T15:31:38Z")

</div>

@tagno25 thanks for the great work  
Do you know if the LED matrix can be controlled in a similar way?

---

<div class="post-metadata">

**Author:** ![RyzenFromFire](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ryzenfromfire/32/44852_2.png) [@RyzenFromFire](https://community.frame.work/u/RyzenFromFire)\
**Post date:** [January 20, 2026, 12:29am UTC](https://community.frame.work/t/guide-how-to-install-openrgb-on-fw16/53358/44 "2026-01-20T00:29:48Z")

</div>

Maybe not as helpful as a drop-in implementation, but for now I made a translation/mapping of how the keys are shown in the OpenRGB layout to how they are physically affected: [FW16 ANSI KB OpenRGB Mappings - Google Sheets](https://docs.google.com/spreadsheets/d/1-WC4I3RvMtg0W0OWpP5w2NfjlNumt1Tsyb9e5Zq8DPU/edit?usp=sharing)

Might help anyone trying to configure Direct mode manually like I was. The layout is strange yet surprisingly logical in some ways. _Most_ keys are where you might expect them to be.

---

<div class="post-metadata">

**Author:** ![RyzenFromFire](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/ryzenfromfire/32/44852_2.png) [@RyzenFromFire](https://community.frame.work/u/RyzenFromFire)\
**Post date:** [January 20, 2026, 12:38am UTC](https://community.frame.work/t/guide-how-to-install-openrgb-on-fw16/53358/45 "2026-01-20T00:38:39Z")

</div>

So far as I can tell, the LED matrix does not use QMK firmware in the same way the keyboard, numpad, and RGB macropad do. Moreover, like the standard numpad, the LED matrix is not RGB, so it doesn’t make much sense to be controlled by OpenRGB.

---

<div class="post-metadata">

**Author:** ![tagno25](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tagno25/32/28302_2.png) [@tagno25](https://community.frame.work/u/tagno25)\
**Post date:** [January 27, 2026, 6:07am UTC](https://community.frame.work/t/guide-how-to-install-openrgb-on-fw16/53358/46 "2026-01-27T06:07:16Z")

</div>

I have fixed the key name and position issues in direct mode!!! 😄  
Key layout/spacing is not perfect, and suggestions welcome.

My [Github repo](https://github.com/tagno25/qmk_firmware) has been updated and I have created a release ([v0.3.2](https://github.com/tagno25/qmk_firmware/releases/tag/v0.3.2)) on Github with pre-compiled u2f files that have been fixed.

---

<div class="post-metadata">

**Author:** ![TechPriestNhyk](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/techpriestnhyk/32/27853_2.png) [@TechPriestNhyk](https://community.frame.work/u/TechPriestNhyk)\
**Post date:** [June 30, 2026, 2:40pm UTC](https://community.frame.work/t/guide-how-to-install-openrgb-on-fw16/53358/47 "2026-06-30T14:40:39Z")

</div>

This is awesome! I’ve been working my own custom RGB firmware and have ran into a couple bugs. It may be better long-term for me to migrate from my custom solution that only works on FW 16 keyboard and work on pull requests for OpenRGB plugins using a firmware like this to add OpenRGB support instead. Hopefully this all still works with current software/BIOS’s 🙂

---

<div class="post-metadata">

**Author:** ![tagno25](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/tagno25/32/28302_2.png) [@tagno25](https://community.frame.work/u/tagno25)\
**Post date:** [August 2, 2026, 7:06am UTC](https://community.frame.work/t/guide-how-to-install-openrgb-on-fw16/53358/48 "2026-08-02T07:06:41Z")

</div>

Yes, my repo works with the newest BIOS.

I am occasionally attempting to a update the repo to the current version of QMK, but I am having a problem with my keyboard randomly freezing. It doesn’t matter what firmware (even stock firmware) making testing nearly impossible.

[Previous page](https://community.frame.work/t/guide-how-to-install-openrgb-on-fw16/53358.md?page=2)
