- Top Pick: NZXT Kraken Elite 280 RGB (2024)
- Runner-up: NZXT Kraken Elite 240 RGB (2024)
- Also consider: ASUS ROG Ryujin III 360 ARGB Extreme White Edition
An AIO liquid cooler in a Linux gaming PC usually arrives with a quiet catch: the pump curve, the radiator fans and the lighting all belong to a Windows application. NZXT wants CAM, Corsair wants iCUE and ASUS wants Armoury Crate, and none of those suites runs on Linux. Without them, the cooler falls back to whatever behaviour its firmware shipped with — rarely the behaviour you would have chosen.
liquidctl is the open-source answer: a cross-platform command-line tool and driver library that talks directly to USB-connected coolers and fan controllers, with no vendor account and no background suite. This article explains what it controls, why its supported-device list is the only specification that matters, how it relates to CoolerControl, how installation and permissions work, where its limits sit, and five pieces of hardware verified against that list.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
liquidctl is a free command-line tool that controls supported AIO liquid coolers, fan and lighting controllers and some power supplies on Linux: pump speeds, fan channels, coolant-temperature curves and, on some models, lighting. Support is strictly per exact model. NZXT Kraken, Corsair Commander and Hydro, ASUS Ryujin and Aquacomputer devices headline the list, so check your model there before anything else.
What liquidctl actually controls
The workflow is deliberately small. One command lists every compatible device the tool can see, another reports live status — coolant temperature, pump speed, fan speeds — and a third writes settings: a fixed duty for a pump, a curve for a fan channel, a colour for a lighting channel.
Two ideas sit underneath. First, liquidctl replaces the vendor application, not the kernel: these USB devices are not exposed by the standard hardware-monitoring drivers, which is the gap the project fills. Second, most settings are written to the device itself, so a curve set once keeps running independent of any daemon — and everything is scriptable.
The supported list is the specification
liquidctl does not support brands; it supports exact models, and the project’s own device list is the document to trust. The headline families are:
- NZXT: Kraken X and Z generations, Kraken 2023 standard and Elite models, the Kraken Elite 2024 RGB line and Kraken 2024 Plus, plus the Smart Device V2, RGB & Fan Controller and Control Hub.
- Corsair: Hydro Platinum and Pro XT coolers, iCUE Elite Capellix coolers via their bundled Commander Core, the Commander Pro, Core, Core XT and ST controllers, Lighting Node Pro and Core, and the HX and RM i-series power supplies.
- ASUS: the ROG Ryujin II 360 and the Ryujin III 360 family, including the EVA, Extreme and White editions.
- Aquacomputer: the Octo and Quadro fan controllers, the D5 Next pump and the Farbwerk lighting controllers.
- Also listed: EVGA CLC coolers, the MSI MPG Coreliquid K360 family, and Lian Li’s GA II LCD cooler and Uni Fan controllers.
Anything not named there is unsupported, however similar its name looks: a different size or refreshed edition can be a different device to the driver.
Curves, pumps and lighting: what the settings do
On coolers, the valuable channel is usually the pump, which liquidctl can hold at a fixed duty or hand a profile. Fan channels accept a fixed duty or a curve expressed as pairs of coolant temperatures and duty steps: the documented Kraken example walks fan duty up as the liquid warms — the right input for a radiator, because coolant temperature moves smoothly instead of spiking with every CPU burst the way a core sensor does.
The Commander Core family shows how per-device the details get. The manual gives the Elite Capellix coolers and the Commander Core, Core XT and ST six fan channels each, with a pump channel on the plain Commander Core bundled with the coolers — and states plainly that lighting channels are not yet supported on that family. The older Commander Pro adds two lighting channels to its six fan channels. Aquacomputer’s Octo exposes eight fan channels and the Quadro four, again without lighting. Screens vary just as much: the Ryujin III’s display is not yet supported even though its pump channels are.
liquidctl or CoolerControl
These two are layers of one stack, not rivals. CoolerControl is the graphical daemon most Linux gamers meet first: it draws curves against CPU, GPU and coolant sensors and applies profiles at boot. For USB coolers and controllers, CoolerControl builds on liquidctl as its driver layer, which is why liquidctl devices appear inside CoolerControl’s device list next to motherboard fan headers.
Choose liquidctl alone for the smallest footprint, for setting a device once and letting firmware hold the setting, or for scripting a headless machine. Choose CoolerControl on top for mixed-sensor curves — case fans that follow whichever of the CPU or graphics card is hotter.
Installing it and the permissions step
liquidctl is packaged for the major distributions and can also be installed from PyPI with pip. Two steps matter more than the package source. Some devices need a one-time initialise pass before they accept settings. And because the tool talks to hardware directly, the manual notes that root privileges are generally required unless you install the udev rules the project ships, which grant your user access to the devices. Install the rules, reconnect the device, and the listing command should show your cooler unprivileged. Secure Boot does not enter into it: this is a userspace tool, not a kernel module.
Honest limits
Support depth is uneven by design. A model can expose its pump and fans while its lighting or screen stays out of reach, as the Commander Core and Ryujin examples show, and firmware revisions occasionally change what a device accepts. New hardware arrives release by release, so a just-launched cooler may not be listed yet. Devices with no USB control path at all are out of reach entirely: a sealed AIO on motherboard headers belongs to the header’s driver, not to this list. And nothing here tunes the curve for you; a badly chosen profile is applied just as faithfully as a good one.
Five supported devices worth building around
Each product below is named on liquidctl’s supported-device list; the remaining specifications are the makers’ published figures.
NZXT Kraken Elite 280 RGB (2024)
The current Kraken flagship in its 280 mm size, from the family liquidctl added as the Kraken Elite 2024 RGB line. Expect pump and fan control through the tool; treat the big display as a bonus.
Specs:
- Radiator: 280 mm with a single-frame F280 RGB Core fan unit
- Pump: NZXT Turbine pump
- Display: 2.72-inch IPS LCD, 640 by 640
- Sockets: AMD AM5 and AM4; Intel LGA 1851, 1700, 1200 and 115X
- Model number: RL-KR28E-B2
- liquidctl support: Kraken Elite 2024 RGB family
NZXT Kraken Elite 240 RGB (2024)
The same Elite generation in the smaller 240 mm format, for cases that cannot take a 280. It shares the Turbine pump, the large display and the same liquidctl support entry as its sibling; only the radiator and fan frame shrink.
Specs:
- Radiator: 240 mm with a single-frame F240 RGB Core fan unit
- Pump: NZXT Turbine pump
- Sockets: AMD AM5 and AM4; Intel LGA 1851, 1700, 1200 and 115X
- Model number: RL-KR24E-B2
- liquidctl support: Kraken Elite 2024 RGB family
ASUS ROG Ryujin III 360 ARGB Extreme White Edition
ASUS’s flagship 360 mm cooler, and the clearest example of partial support done honestly: liquidctl lists the Ryujin III 360 family including the Extreme and White editions, documents pump and pump-fan channels, and states that the screen is not yet supported. Buy it for the pump hardware; let the LCD wait.
Specs:
- Radiator: 360 mm
- Pump: Asetek Emma Gen8 V2 with a three-phase motor
- Fans: three magnetic daisy-chained ROG MF-12S ARGB Extreme fans
- Display: 3.5-inch IPS LCD, plus an embedded VRM fan
- Sockets: AMD AM5 including Ryzen 9000; Intel Core Ultra and LGA 1700
- liquidctl support: pump and pump-fan channels; screen not yet supported
Corsair iCUE H100i Elite Capellix XT
A 240 mm cooler that ships with a Commander Core controller in the box — the part liquidctl talks to. The manual covers the Elite Capellix H100i by name: the bundled controller exposes six fan channels and the pump channel, while its lighting channels are not yet supported. On Linux this is a fan-and-pump purchase, not a lighting one.
Specs:
- Radiator: 240 mm with two AF120 RGB Elite fans
- Controller: iCUE Commander Core included in the box
- Sockets: Intel LGA 1700, 1200, 115X and 2066; AMD AM5 and AM4
- Model number: CW-9060068-WW
- liquidctl support: fan and pump channels via the Commander Core; lighting not yet supported
Corsair Commander Core XT
The standalone hub for a case full of Corsair fans. liquidctl lists the Commander Core XT with six fan channels, making it the tidy way to move case-fan control off a crowded motherboard and into the same tool that runs the cooler. Its lighting channels stay iCUE-only on Linux for now.
Specs:
- Fan channels: six 4-pin PWM channels
- Lighting: two channels for Corsair RGB devices under iCUE
- Sensors: two repositionable temperature probes included
- Connections: internal USB 2.0 header with pass-through, SATA power
- Model number: CL-9011112-WW
- liquidctl support: six fan channels; lighting not yet supported
How to choose
Start with the listing command, not the shopping list: install liquidctl, connect the hardware you already own, and see whether it appears. If you are buying new, match the full model name on the project’s list — generation, edition and size all matter, and a White or Extreme variant is only covered where the list says so. Decide next which channels you need: pump and fan control is the mature core almost everywhere, while lighting and screens are the features most often still missing. Finally, choose your layer: liquidctl alone for set-and-forget settings, or CoolerControl above it for sensor-mixed curves.
Who should skip this
Skip liquidctl if your cooler or controller is absent from the supported list — no configuration makes an unlisted device appear. Skip it if your AIO has no USB connection and lives entirely on motherboard headers; that is hwmon territory. Skip the command line entirely if you will never open a terminal: CoolerControl’s window, using the same driver layer, is the honest recommendation. And skip it if your build’s point is a synchronised lighting show across one vendor’s ecosystem, because the Windows suites still do that job more completely.
FAQ
How do I know whether my cooler is supported?
Run the device listing after installing liquidctl and compare it with the project’s supported-device list. The exact model name and generation must match; a near-identical name from a different year is a different device to the driver.
Can liquidctl damage my cooler with a bad setting?
liquidctl writes the speeds and curves you give it to the device, so treat pump settings with the same care you would in the vendor’s own software: keep the pump running, change one channel at a time, and watch temperatures afterwards.
Why does my Commander Core lighting not respond?
Because, per the manual, lighting channels on the Commander Core family are not yet supported, while the fan channels and, on the cooler-bundled unit, the pump channel are. That is a documented limitation, not a fault in your setup.
Final verdict
liquidctl is one of the quiet success stories of Linux gaming hardware: a scriptable tool that hands AIO pumps, radiator fans and controller hubs back to the player. Its discipline is its strength — the supported list is exact, the documentation says what is missing as plainly as what works, and CoolerControl turns the same drivers into a graphical curve editor when you want one. Check your model against the list, install the udev rules, and your cooler’s behaviour becomes a decision you made, not a default you inherited.











