NextTabletDriver: An Open Source Driver Built for Low Latency
iSweat
August 25, 20264 min read9 views
Tablet drivers are the kind of software you only think about when something goes wrong. A hundred milliseconds of extra lag, an active area that never quite maps right, or one more background app eating your RAM. NextTabletDriver was built to fix exactly that.
What it is
NextTabletDriver is an open source, user mode drawing tablet driver written in Rust. It positions itself as a modern alternative to OpenTabletDriver, aimed at digital artists and osu! players who need consistent, low latency pen input on Windows and Linux. The project pairs a compact Rust input pipeline with a native egui interface, so the app itself stays light while it handles device polling, mapping, and OS injection.
Why it exists
The project describes itself as a replacement for vendor-specific drivers: instead of running whatever software ships with a given tablet brand, the goal is one driver that behaves the same way across devices and operating systems. That focus shows in the project layout too, with input polling, mapping, and OS injection kept in a small, dedicated engine rather than spread across a heavier application.
What it does well
Low latency. Optimized polling, high-priority input threads, and a compact Rust pipeline keep the delay between pen and cursor low enough to disappear.
Precise mapping. Active area, target display selection, rotation, aspect ratio locking, and edge snapping are all configurable, so the tablet surface maps to the exact pixels you want.
Custom themes. Interface themes are plain JSON: full color palettes, spacing, semantic colors, and even the opacity of the osu! playfield overlay.
Built-in telemetry. A live console, performance panels, the Devocub Antichatter filter, and a HandSpeed WebSocket output are included for anyone who wants to inspect what the driver is actually doing.
Cross-platform. Windows is handled through native input APIs, Linux through uinput. Same driver, same behavior, either OS.
Supported hardware
Tablet support comes from community maintained JSON configuration files rather than hardcoded device logic. Families with existing definitions include Wacom, Huion, Kamvas, XP-Pen, UGEE, Gaomon, VEIKK, Artisul, Parblo, XenceLabs, and UC-Logic, among others. Adding a new device means contributing a config file, and a parser implementation when the device needs one, not a low level driver rewrite.
Getting it running
On Windows, the installer or portable build comes straight from the releases page, or through Winget with winget install iSweat.NextTabletDriver. On Linux, there is an AUR package for Arch, a .deb for Debian based distributions, and an AppImage that runs almost anywhere. Generic Linux installs need udev rules for HID access and a user added to the input group, both handled by a script in the repository.
Building from source only needs Rust 1.96.1 or newer, pkgconf, and hidapi, plus a handful of Linux libraries (gtk3, libxkbcommon, libglvnd, wayland) and uinput support for the desktop build. From there, cargo build --release --locked produces the binary.
Open source, from day one
NextTabletDriver is MIT licensed, and the whole project lives on GitHub: the driver code, the tablet definitions, the themes, all of it. Issues and pull requests are open, and the maintainers point to tablet configuration updates, parser fixes, Linux packaging, theme examples, and UI polish as good starting points for new contributors.
For anyone tired of bloated vendor software, or just looking for a driver that treats latency as a first class concern, NextTabletDriver is worth a look. The project is still young, ten stars and two forks at the time of writing, but the groundwork is already there: a real Rust input pipeline, a wide hardware config library, and a genuinely cross-platform design.