DEV Community

Cover image for Pen Pressure Not Working? Test the Stylus First, Then Fix the Driver or App
keyboardTester.Click
keyboardTester.Click

Posted on • Originally published at keyboardtester.click

Pen Pressure Not Working? Test the Stylus First, Then Fix the Driver or App

Condensed cross-post of the original guide on KeyboardTester.click: Pen Pressure Not Working? Test the Stylus, Then Fix the Driver or App. The full version has per-brand and per-app tables plus a video walkthrough.

A brush that ignores light and firm strokes can fail at several different layers: the pen may be incompatible, the tablet driver may expose the wrong interface, Windows Ink and WinTab may not match the app, or the selected brush may simply not use pressure. Buying hardware before you separate those layers wastes time and money.

This is a reproducible fault-isolation workflow for Windows 10/11 with Wacom, Huion and XP-Pen devices in Photoshop, Krita and Clip Studio Paint. It is based on browser-visible Pointer Events plus current vendor documentation — a fault splitter, not a pass/fail certificate.

Read the browser result before you change anything

Open the free Pen Pressure & Tilt Test and draw three slow diagonals from a light touch to a comfortably firm touch. It shows the Pointer Events data delivered to the browser: pointer type, normalized pressure from 0 to 1, min/max/average, tilt when exposed, and CSV/JSON export. Everything stays on your device.

Interpret it like this:

  • Pointer type is pen and pressure varies — the browser/OS path is receiving analog pressure. The fault is downstream in the app's brush or input API.
  • Pointer type is pen but pressure is fixed at 0 or 0.5 — the browser is not receiving variable pressure. Check driver exposure, the input API, and the vendor tester.
  • Pointer type is mouse or touch — the browser does not see a pressure-capable pen. Confirm an active, compatible stylus and the correct driver.

MDN defines pressure as a normalized 0-to-1 value and notes that hardware without a pressure sensor can report 0.5 while a button is active and 0 otherwise. A changing value shows the browser receives analog pressure; a flat value only shows that this one path does not. It does not certify the hardware.

Windows Ink vs WinTab: make the driver and app agree

WinTab and Windows Ink are two different Windows input paths. Adobe documents Windows Ink as Photoshop's default route on current Windows; Krita exposes an input-API selector; Clip Studio distinguishes WinTab pen tablets from TabletPC devices. The useful rule is agreement, not ideology — the driver and the target app must use a compatible path. If one app fails while the browser and another app work, change only the failing app's profile, restart it, and re-test. Do not disable or enable Windows Ink everywhere as a blanket fix.

Per-app fixes

  • Photoshop — In Brush Settings > Shape Dynamics, set the control to Pen Pressure and test with a pressure-enabled brush. Windows Ink is Adobe's default API; use a documented WinTab alternative only when you intentionally match that path.
  • Krita — Open Settings > Configure Krita > Tablet Settings, choose WinTab or Windows 8+ Pointer Input, restart Krita, and use its tablet tester. Krita recommends switching the API only for troubleshooting.
  • Clip Studio Paint — For a screen/pen tablet use Preferences > Tablet > WinTab; for a tablet PC use TabletPC. Restart and compare another app.

Per-brand drivers

If both the browser and the target app stay flat, open the manufacturer's own pressure tester — that separates what the driver receives from what it exposes downstream.

  • Wacom — Confirm the driver is running, use its diagnostics to test the pen, and verify the app's Windows Ink setting.
  • Huion — Match driver and application protocols, test pressure in the driver, restart it, and reinstall the current official driver if needed.
  • XP-Pen — Use the pressure test in the current PenTablet panel, remove other tablet drivers, and reinstall the current model-specific driver.

Broke right after a Windows update?

Treat the timing as a clue, not proof. Reboot cleanly and confirm the device is detected, restore the matching Windows Ink/WinTab choice you recorded, then clean-install the correct vendor driver (removing conflicting tablet drivers first). Only compare driver versions with evidence — do not install random packages.

When it really is hardware

Escalate only after the browser, the vendor tester, and more than one pressure-enabled app have been compared. Inspect the nib per the manual, reseat the cable, avoid an unpowered hub, try another supported port, and test a known-good pen or a second computer. Replace the tablet only after the cheaper compatibility, settings, driver, nib, cable, and pen checks fail.

Related browser tools

Full guide with tables and video: keyboardtester.click/blog/pen-pressure-not-working-test-fix.php

Top comments (0)