- Home
- GPU Overclocking Software
- TuxClocker
TuxClocker
What it is
TuxClocker is a free GNU/Linux program for monitoring and controlling hardware, built from a D-Bus daemon and Qt graphical interface. It can handle any number of devices at once; users select a device node to read or change its properties. NVIDIA features include fan control, clock and power-limit controls, temperature and utilization readings, and VRAM monitoring. Voltage setting and reading are available for 600–900 series GPUs under Xorg. AMD support includes fan and clock editing, performance parameter control, voltage and VRAM monitoring, and voltage-frequency curve editing on applicable GPUs. CPU features include frequency and utilization monitoring, governor settings, frequency limits, power-use monitoring and energy-power preferences. A prebuilt tarball is available from the release page, along with packages for openSUSE Tumbleweed. NVIDIA editing requires Coolbits; AMD editing requires the amdgpu.ppfeaturemask boot parameter. Optional dependencies connect NVIDIA support through libnvml and libxnvctrl, AMD support through libdrm, and improved AMD names through python-hwdata. The project uses GPL-3-only licensing and lists support for platforms beyond Linux as a possible future improvement.
For and against
For
- Can manage multiple devices at once
- Includes NVIDIA, AMD and CPU controls
- Offers a prebuilt tarball and openSUSE Tumbleweed packages
- Licensed under GPL-3 only
Against
- Focused on GNU/Linux
- NVIDIA editing requires Coolbits
- AMD editing requires a boot parameter
The verdict
TuxClocker combines hardware monitoring and controls in a daemon and Qt interface, with features spanning supported NVIDIA, AMD and CPU properties. GPU editing depends on the relevant system configuration.
Who it suits
TuxClocker suits GNU/Linux users who want to monitor or adjust supported GPU and CPU properties. Some editing functions require vendor-specific configuration.
Plans and prices
TuxClocker
GNU/Linux · GPL-3 only · hardware-specific GPU/CPU support
Read 1 Oct 2026 · github.com
On the record
- AMD support
- Supported AMD features include fan control, clock editing, performance parameter control, voltage monitoring, VRAM monitoring and voltage-frequency curve editing on applicable GPUs.github.com · read 1 Oct 2026
- CPU monitoring
- CPU features include frequency and utilization monitoring, governor settings, frequency limits, power usage monitoring and energy-power preference settings.github.com · read 1 Oct 2026
- Device properties
- Users can read and write device properties by selecting a node to edit.github.com · read 1 Oct 2026
- Installation
- The project provides a prebuilt tarball from its release page and distribution packages for openSUSE Tumbleweed.github.com · read 1 Oct 2026
- Integrations
- Optional dependencies integrate NVIDIA support through libnvml and libxnvctrl, AMD support through libdrm, and prettier AMD names through python-hwdata.github.com · read 1 Oct 2026
- License
- TuxClocker is licensed under GPL-3 only.github.com · read 1 Oct 2026
- Maintainer contact
- The maintainer lists Discord, Matrix and email contact details on the GitHub profile.github.com · read 1 Oct 2026
- Multi-device support
- The program supports any number of devices at once.github.com · read 1 Oct 2026
- NVIDIA support
- Supported NVIDIA features include fan control, clocks, power limits, temperatures, utilization and VRAM monitoring, with voltage setting and reading for 600–900 series GPUs under Xorg.github.com · read 1 Oct 2026
- Platform limitation
- The project lists support for more platforms than Linux as a possible future improvement, indicating current focus on GNU/Linux.github.com · read 1 Oct 2026
- Prerequisites
- NVIDIA editing requires Coolbits, while AMD editing requires the amdgpu.ppfeaturemask boot parameter.github.com · read 1 Oct 2026
- Purpose
- TuxClocker is a hardware controlling and monitoring program consisting of a D-Bus daemon and Qt GUI.github.com · read 1 Oct 2026
- Support
- Project questions and suggestions can be discussed through bridged Matrix and IRC chats.github.com · read 1 Oct 2026
- Translations
- Translations use GNU gettext and can be contributed through Weblate or locally via pull requests.github.com · read 1 Oct 2026
