nvibrant-tui
Control NVIDIA Digital Vibrance from your terminal — per display, with sliders, and persistent across reboots.
No more commands on every login. Set it once, enable autostart, and forget about it.
Install
pipx install nvibrant-tui
Then run:
nvibrant-tui
Your displays show up as sliders. Drag them or use the keyboard, hit Apply, and your settings are saved. Next login they'll be right where you left them — or enable Autostart and they'll be applied automatically before you even open the TUI.
Using pip instead of pipx?
pip install nvibrant-tui
Controls
| Key | Action |
|---|---|
← / → |
±1 |
Shift+← / Shift+→ |
±64 |
0 |
Reset this display to 0 |
Ctrl+S |
Apply |
a |
Toggle auto-apply |
l |
Link all displays |
b |
Toggle autostart |
Ctrl+Q |
Quit |
Auto-apply pushes changes to the driver as you move the slider, with a short debounce so it doesn't spam it on every tick.
Link all ties all displays together so one slider moves them all — useful if you want a uniform look across monitors.
How settings are saved
Values are written to ~/.config/nvibrant-tui/config.json only after nvibrant confirms the apply succeeded. You'll never end up with a saved state that wasn't actually applied.
Autostart installs ~/.config/systemd/user/nvibrant.service — a one-shot service that fires after your graphical session starts. If you update your GPU driver or reinstall nvibrant, toggle Autostart off and on again to regenerate it pointing to the new binary.
Requirements
- NVIDIA GPU with a working driver
- Wayland session
- Python 3.10+
- systemd user session (only needed for Autostart)
Development
git clone https://github.com/enrialonso/nvibrant-tui
cd nvibrant-tui
python -m venv .venv && .venv/bin/pip install -e ".[dev]"
.venv/bin/nvibrant-tui
.venv/bin/pytest
Acknowledgements
nvibrant-tui is a frontend for nvibrant by Tremeschin, which does the actual work of talking to the NVIDIA driver. None of this would exist without it.
License
GPL-3.0 — see LICENSE.
Metadata
Release files for nvibrant-tui 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nvibrant_tui-0.1.1.tar.gz | 166.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nvibrant_tui-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 176.2 kB
Release files / nvibrant_tui-0.1.1.tar.gz
| Download URL | nvibrant_tui-0.1.1.tar.gz |
|---|---|
| Size | 166.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e20e02269acddd219ca514e47906d2e8c3a9aee55155a389b8d2e26035699cce
|
|
BLAKE2b-256 checksum How to use checksums |
b33d9d0b8de3d49aa45bca805cd9428d58fc7974c8ac8d5ddd7ef706e84b4d03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 17, 2026.
Transparency logRelease files / nvibrant_tui-0.1.1-py3-none-any.whl
| Download URL | nvibrant_tui-0.1.1-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2a2774c5a38b4c6928faedad21732e72ff28c6d1622ae5a3e4336ef00c6fe130
|
|
BLAKE2b-256 checksum How to use checksums |
f7cbc126b51a6e4550ec255b0ed1c4a5df853ed58f74bced4410896f8e0417e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 17, 2026.
Transparency log