As an Amazon Associate we earn from qualifying purchases.
The right mechanical keyboard software is the tool your manufacturer documents for your exact keyboard and intended task. Start with the model, revision, layout, operating system, and connection mode. Then find the official instructions for changing key output, configuring lighting, or updating or recovering firmware.
This guide is for keyboard owners who want to identify that official route before changing settings. It uses Wooting and Corsair examples to explain what a support document establishes—and which details still need confirmation for your setup.
Quick takeaways
- Match the complete model name to official support instructions before choosing software.
- Check browser and device-access requirements before treating a detection problem as a firmware problem.
- Preserve settings and confirm onboard-memory limits before expecting a configuration to work with its desktop app closed.
Editorial method: This guide uses official support excerpts captured on October 15, 2026. Its recommendations come from documentation, without hands-on software testing. Exact current operating-system requirements, license terms, and privacy practices remain checks for the version you intend to use.
In this guide: Identify your keyboard · Choose your task · Official model examples · Check access · Preserve settings · Firmware prerequisites · FAQs
Identify your keyboard before choosing software
Build a short identification record before searching for a download. Use the full model designation shown on your keyboard, packaging, or purchase record, then compare it with the manufacturer's support documentation. If the hardware revision is unclear, record it as unknown and ask the manufacturer whether it affects tool selection.
Use this worksheet to keep confirmed details separate from assumptions. It is a preparation tool, not a compatibility test.
| Detail | What to record | What needs confirmation |
|---|---|---|
| Exact model | Complete product name, including suffixes | Does the official document name this model? |
| Hardware revision | Revision or variant, if identified | Does the manufacturer distinguish revisions? |
| Physical layout | The keyboard's layout designation | Does the relevant process require a layout choice? |
| Operating system | Name and installed version | Does the current tool support this version? |
| Connection mode | The connection you intend to use | Is that mode supported for configuration? |
| Intended task | Key output, lighting, profiles, or firmware | Does the official guide address this task? |
| Software version | The version offered through official support | Do its requirements and instructions match your setup? |
The layout field deserves particular attention before recovery. Wooting's reset and recovery documentation requires the correct ANSI or ISO layout selection and separately names the 60HE and 80HE. A familiar software name does not replace those model and layout checks.
Apply the same standard to a tool described as open source: require official evidence for your keyboard. Treat the tool's name or license as insufficient confirmation of model support.
Match mechanical keyboard software to your task
Write down the result you want before opening a configuration tool. “Swap two keys on my Mac” is a clearer starting point than “change my keyboard firmware.” It helps you find the relevant instructions and avoid choosing a more disruptive process without a documented reason.
Remapping: change what a key does
Remapping changes the output assigned to a key. Wooting's Mac modifier-key article distinguishes changing Option and Command through macOS settings from changing the keyboard's keymap in Wootility and saving it to the keyboard. Those approaches have different consequences when moving between operating systems.
Decide whether you want the change associated with one computer's settings or with the keyboard's saved mapping. Also keep the printed key label separate from the desired output: describe the behavior you want in your notes. That makes the support question more precise than saying a key is simply “wrong.”
Lighting and profiles: choose settings and where they live
A profile groups settings you want to preserve or reuse. For Corsair's documented hardware-profile workflow, lighting and actions can be stored onboard and used without iCUE running in the background. Hardware actions have fewer options than software actions, however, so the location of a saved setting affects expectations. See Corsair's Device Memory Mode guidance.
Define the goal as precisely as possible: for example, “keep this lighting configuration when iCUE is closed.” Then check whether your exact device supports that result through its hardware-profile workflow.
Firmware: use the separate update or recovery documentation
Treat firmware updates and recovery as a separate task category. Wooting provides a model-specific recovery guide with layout and profile-preservation considerations. Locate the applicable official procedure before beginning firmware work; this selection guide does not provide flashing commands or restore-key sequences.
What the official model examples establish
The examples below show how to connect a model to a documented tool or workflow. They are bounded examples, not a full compatibility list.
| Keyboard | Officially documented association | Boundary to check |
|---|---|---|
| Wooting 60HE, all variants, and Wooting 80HE | Wooting names these models separately in its Wootility recovery documentation. | Confirm the exact model, layout, and applicable software instructions; this does not establish every feature or OS combination. |
| Corsair K70 RGB MK.2 | Corsair's model-specific support article names iCUE and the Key Assignments area. | This establishes the model/tool association, without confirming every current version requirement or another K70 variant. |
For a K70 RGB MK.2 owner, the documented starting point is iCUE. The cited article concerns macros, but its role here is only to establish that exact model's association with the software. Macro programming requires its own task-specific instructions.
For a Wooting 60HE or 80HE owner, the recovery documentation supplies a model-specific reference. Use it alongside the relevant configuration and access guidance. Neither example establishes support for an unnamed keyboard simply because its branding or appearance is similar.
Check browser and device access
If Wootility Web cannot detect your keyboard, review its access requirements before choosing different software or beginning recovery. Wooting's detection article names Chromium-based browsers—Chrome, Microsoft Edge, Vivaldi, and Opera—and excludes Safari and Firefox for that web workflow.
The same article describes a request for permission to connect to the keyboard. It also directs Linux users to device-access guidance involving udev rules. Browser support, authorization, and Linux device access are therefore separate items to check.
Use this order when gathering troubleshooting information:
- Browser: Compare the browser you are using with the official web-tool requirements.
- Permission: Establish whether the requested keyboard connection has been authorized.
- Linux access: If applicable, consult the device-access guide linked from Wooting's detection article.
- Remaining problem: Record the model, software version, connection mode, and exact error before seeking further support.
Wooting's article also points readers toward desktop Wootility when they do not want a Chromium-based browser. Check the desktop release's current requirements separately. The browser guidance does not establish a universal operating-system or version guarantee for either route.
Preserve profiles and check what runs onboard
Before a reset or another change that could affect your settings, identify the preservation method documented for your tool. Keep a record of the profiles and behaviors you want to retain. Then distinguish a saved backup from the settings available on the keyboard itself.
Wooting: check whether local profiles are available
Wooting's recovery article describes preserving previously local profiles through the Inactive Profiles area before a reset. The relevant condition is prior local use of Wootility. Do not assume the same profile-preservation opportunity exists when those local profiles are absent.
Before proceeding, locate the documented preservation guidance and establish which profiles are available. Treat this as preparation for the exact recovery procedure, without assuming that every setting will be retained or that recovery will succeed.
Corsair: separate exported files from onboard profiles
Corsair documents iCUE profile import and export, including saving an export to a chosen destination. That establishes an export workflow. It does not establish that every exported feature works on every device or remains available with iCUE closed.
Separately, Corsair's hardware-profile documentation describes onboard lighting and actions, fewer hardware-action options, and a profile-slot count that depends on device storage. Check those limits for your exact keyboard before planning which settings to carry between computers.
Practical example: Suppose you want a Corsair keyboard to retain lighting on a work computer where iCUE will not be running. Use the hardware-profile guidance to check whether that lighting behavior can be saved onboard for your device. An exported profile file alone does not answer the question. Keep separate notes for “saved as a file” and “confirmed available without iCUE.”
Prepare before firmware work or a download
Before firmware work, assemble the documents and settings information you will need:
- Exact model instructions: Confirm that the official update or recovery guide applies to your keyboard.
- Layout confirmation: Resolve any required physical-layout selection, including ANSI or ISO where specified.
- Profile preservation: Identify the supported backup or preservation method and its limits.
- Recovery reference: Locate the official recovery guidance before starting the change.
Wooting's recovery documentation illustrates why model, layout, and preservation checks belong together. It supplies prerequisites to verify, rather than a recovery-success guarantee.
For downloads, begin with the manufacturer's official support route and follow its current software links. Confirm the actual release's operating-system requirements, license, and privacy information before use. Those details are not established by the support excerpts cited here; leave an unanswered field unconfirmed instead of substituting assumptions or an unofficial mirror.
Frequently asked questions
Can I use iCUE for any mechanical keyboard?
Require an official support entry for your exact keyboard before selecting iCUE. The evidence here connects the Corsair K70 RGB MK.2 to iCUE through Corsair's model-specific article. It does not establish support for another manufacturer's keyboard or every similarly named Corsair model.
Does Wootility Web work in Safari or Firefox?
Wooting's captured detection guidance excludes Safari and Firefox for Wootility Web and names supported Chromium-based browsers. Check that requirement alongside keyboard-connection permission and, on Linux, the linked device-access guidance. Desktop Wootility has separate requirements to confirm for your operating system and version.
Will my settings work after I close iCUE?
Check whether the particular settings are supported and saved as hardware profiles on your device. Corsair documents onboard lighting and actions that work without background iCUE, but hardware actions have fewer options and storage limits vary. Its Device Memory Mode article does not promise every software feature will remain available.
What should I ask support if compatibility is unclear?
Send the full model designation, any known revision, layout, operating system and version, connection mode, and intended task. Ask which official tool and release support that combination. For a detection problem, include the exact error and browser or app version. Keep unknown details explicitly marked so support can resolve them.
Your next step
Choose mechanical keyboard software by matching your exact model, your task, and the documented access requirements. For the examples here, consult Corsair's K70 RGB MK.2 iCUE instructions or Wooting's relevant Wootility guidance, then verify the remaining details for your setup. Complete the identification worksheet before downloading software or changing settings.
Sources
The following official support excerpts were captured on October 15, 2026; that is the evidence capture date, not a claimed publication or revision date.
- Wooting: Wootility Doesn't Detect My Wooting Keyboard.
- Wooting: How to reset, recover or restore my Wooting.
- Wooting: How to Swap Around Option/Command and Backslash/Backtick Key on Mac OS.
- Corsair: How to: Record macros for your K70 RGB MK.2.
- Corsair: iCUE: How to: Import and export iCUE profiles.
- Corsair: iCUE: How to configure hardware profiles/Device Memory Mode.