You view pen and touch info in Windows through Settings > Bluetooth & devices > Pen & Windows Ink, or by opening the Pen & Windows Ink control panel, which lists paired pens, battery level, pen shortcuts, and handwriting settings. Touch and pen hardware details also appear under Device Manager > Human Interface Devices, where each HID-compliant pen and touchscreen digitizer is enumerated separately. On macOS and iPadOS, equivalent information lives in System Settings > Apple Pencil or the Bluetooth pane. The exact location depends on your operating system and whether your device uses a Microsoft Pen Protocol, Wacom, or Apple digitizer.

What "pen and touch info" actually reports

A pen and touch info panel is not a single sensor readout. It is an aggregation layer that queries several independent subsystems and displays their combined state. Understanding what each layer reports explains why the panel sometimes shows a pen as "connected" while pressure or tilt data is missing.

The first layer is the digitizer firmware. A touchscreen or pen display contains an analog sensor grid that samples at a fixed rate, typically between 120 Hz and 360 Hz depending on the panel. That firmware converts raw capacitance or electromagnetic resonance changes into coordinate packets. The operating system never sees the analog signal, only these packets.

The second layer is the HID descriptor. Each pen and touch digitizer exposes a USB Human Interface Device descriptor that declares which capabilities it supports: X/Y position, pressure, tilt, barrel button, eraser, hover range, and contact count. Windows reads this descriptor to decide which fields to populate in the pen and touch info view. If the descriptor omits a field, the panel shows it as unavailable even when the hardware can physically measure it.

The third layer is the driver and API stack. Microsoft Pen Protocol devices rely on the inbox HID driver, while Wacom and some OEM pens install a vendor driver that adds features like Express Keys or radial menus. The pen and touch info panel reflects whatever the active driver exposes, so two identical pens on two machines can display different capability sets.

The practical consequence is straightforward. When you view pen and touch info and a field is blank, the cause is usually the descriptor or driver, not a broken pen. Checking Device Manager properties for the HID-compliant pen device shows the raw capability report, which is the ground truth the settings panel summarizes.

Why the panel separates pen and touch

Pen and touch are reported separately because they are physically different sensing technologies sharing one glass surface, and they have different latency, precision, and palm-rejection profiles.

Capacitive touch detects the change in capacitance when a finger touches the panel. It reports contact geometry, which is why a fingertip produces a larger contact patch than a stylus tip. Active pen digitizers use either electromagnetic resonance, where the pen draws power from the panel's field, or an active electrostatic scheme with a battery in the pen. The panel distinguishes pen from finger by signal signature, tip size, and often a hardware sync channel.

Latency numbers illustrate why the separation matters. Finger touch on a typical laptop panel reports at 60 Hz to 120 Hz with end-to-end latency around 30 ms to 60 ms. An active pen on a modern tablet reports at 240 Hz with latency as low as 9 ms on Apple Pencil second generation and comparable figures on high-refresh Windows pen displays. Mixing the two streams would force the slower touch rate onto the pen path.

Palm rejection depends on this separation. When the digitizer firmware confirms an active pen is in range, it suppresses touch contacts above a size threshold or within a radius of the pen tip. The pen and touch info panel lets you confirm that pen detection is active, which is the precondition for palm rejection to engage. If the panel shows no pen while you write, palm rejection is not running and stray palm marks will appear in ink.

A counterintuitive detail: a pen can be "paired" over Bluetooth for shortcut buttons while its tip position still streams over the digitizer's separate wired or inductive channel. Pairing status in the panel tells you about the button radio, not about whether ink will appear. Ink requires the digitizer link, which is independent of Bluetooth.

Quantified context: what the numbers mean

The values shown when you view pen and touch info are only meaningful against known ranges. Here is how the common fields map to real hardware behavior.

Pressure levels are reported as a maximum, usually 1,024, 2,048, 4,096, or 8,192 levels. These are 10-bit to 13-bit values. A 4,096-level pen resolves about 0.024 percent of full scale per step; in practice the limiting factor is the sensor's physical noise floor, not the bit depth. A pen advertising 8,192 levels rarely delivers more usable resolution than a good 4,096-level pen.

Sampling rate appears in reports per second. Typical values are 120 Hz, 133 Hz, 240 Hz, and 360 Hz. At 240 Hz, the interval between samples is about 4.2 ms. Reported latency figures of 9 ms to 20 ms combine sampling interval, processing, and display scan-out, so a higher report rate alone does not guarantee lower perceived lag.

Hover distance is the height above the glass at which the pen is still detected. It ranges from about 5 mm to 15 mm on active pens; passive electromagnetic pens often hover farther. Hover range determines when the cursor appears and when palm rejection activates.

Battery level for Bluetooth-paired pens is reported in coarse steps, often 5 percent or 10 percent increments, because the Bluetooth GATT battery service uses a single byte. A pen showing 90 percent may be anywhere from 86 to 94 percent. Do not treat it as precise.

Data source What it reports Typical granularity Where to see it
Settings pen panel Paired pens, battery, shortcuts Coarse battery, feature list Bluetooth & devices > Pen & Windows Ink
Device Manager HID node Descriptor capabilities, power state Per-field presence Human Interface Devices
Vendor driver app Pressure curve, button mapping High, adjustable OEM or Wacom utility
Diagnostic tools Report rate, raw coordinates Per-sample HID logging utilities
Bluetooth settings Pairing, signal Connection state Bluetooth & devices

Timeline: how pen and touch info changes over a session

The information you see is stateful. It changes as the pen moves in and out of range, as drivers load, and as power management suspends devices.

Time point Event What the panel shows
Boot HID enumeration Pen and touch devices listed; pen status "not connected" until in range
Driver load Vendor driver attaches Additional fields appear, such as pressure curve or shortcuts
Pen approaches Hover detection engages Pen status becomes active; palm rejection arms
Pen tip contact Contact and pressure stream Pressure and tilt fields populate in real time
Pen leaves hover Out-of-range timeout, typically 3 to 10 seconds Pen status returns to inactive; touch resumes normally
Idle timeout Power management suspends HID device Device may show as powered down until next input
Bluetooth sleep Pen button radio sleeps Pairing shows connected but unresponsive until wake

The out-of-range timeout is the field most often misread. Users see the pen shown as disconnected a few seconds after lifting it and assume a fault. In reality the digitizer has simply stopped reporting a pen in range, which is the designed behavior that returns the surface to full touch and palm input.

Edge cases and red-flag warnings

Most pen problems are configuration or driver issues, but a few patterns indicate hardware faults that no setting will fix.

Pen detected in Device Manager but never reports position: the digitizer antenna or pen coil has failed; test with a second pen before assuming the tablet. Pressure appears in the panel but ink shows no pressure variation: the application is not querying the pressure API, not a hardware fault. Pen works but touch does not, or the reverse: the shared digitizer controller may have one channel down; check firmware updates first. Battery drains from 100 to 0 percent within days while idle: the pen's Bluetooth radio is not entering sleep; a firmware or pairing reset is warranted. Random cursor jumps to a corner: often a stuck touch contact interpreted as a finger, which the touch info view will show as a phantom contact. Pen works on one account but not another: per-user driver or pen settings corruption; recreate the pen profile.

The professional caveat worth stating plainly: a clean pen and touch info panel proves the operating system received a valid descriptor and a live device. It does not prove the pen's pressure sensor is calibrated or that the digitizer's linearity is within specification. Those require a test pattern and a known-good reference pen, which is why repair technicians keep both on hand.

Misconceptions about pen and touch info

The most common misconception is that the pen and touch info panel is a diagnostic tool. It is a configuration and status view. It does not measure accuracy, jitter, or linearity, and it cannot tell you whether a 4,096-level pen is performing to spec. Use a drawing test and a straight-edge calibration pattern for that.

A second misconception is that higher advertised pressure levels always mean better drawing feel. Usable pressure resolution is bounded by sensor noise and by the pressure curve the driver applies. Many artists prefer a well-tuned 2,048-level pen over a poorly tuned 8,192-level one. The panel's number is a ceiling, not a delivered experience.

A third misconception concerns pairing. Bluetooth pairing in the pen panel is for shortcut buttons and find-my-pen features on some platforms. It is not required for ink. Disconnecting Bluetooth does not stop the pen from writing; it stops the buttons from working. Users who "forget" a pen in Bluetooth and then find it still writes are seeing correct behavior.

A fourth misconception is that the touch info view lists every finger the panel can track. Most panels track 10 simultaneous contacts, but the HID descriptor may report a lower maximum, and the panel displays only what the descriptor declares. A panel reporting 5 contacts may still physically track 10; the difference is a firmware choice, not a limitation you can change.

Finally, users often conflate "pen support" with "pressure support." A device can accept pen input as a simple pointing device with no pressure or tilt, which is common on older or budget touchscreens. The pen and touch info view will list the pen but show pressure and tilt as unavailable, which is the accurate signal that you have position-only pen input.

Practical actions: verifying and fixing pen and touch info

Start with the operating system view, then descend to the device level only if the summary is wrong or incomplete.

Open Settings and navigate to Bluetooth & devices > Pen & Windows Ink. Confirm the pen is listed. If it is not, the digitizer has not detected it; check that the pen has a working battery or is charged. Open Device Manager and expand Human Interface Devices. Look for HID-compliant pen and HID-compliant touch screen entries. Open Properties > Details and read the device description and capability fields to see which features the descriptor declares. If a vendor driver is installed, open its utility and confirm the pressure curve and button mapping. A reset to defaults resolves many "pressure stopped working" reports. Test with a second known-good pen. If the second pen reports correctly, the first pen's coil or battery is the fault. If neither works, the digitizer or its cable is suspect. Update the digitizer firmware from the device manufacturer. Firmware fixes for palm rejection and hover timeout are common and are not delivered through Windows Update. If touch reports phantom contacts, disable touch in the pen panel temporarily to confirm the pen path is clean. Phantom contacts with pen only indicate a digitizer fault.

Thresholds to act on: a pen that fails to appear within 15 mm of the glass is out of hover range or dead. A battery that falls below 20 percent in under a week of light use points to a sleep bug. A report rate that drops below half its rated value under load suggests USB or power throttling, not a pen fault.

Limitations: what this information cannot tell you

The pen and touch info view cannot certify accuracy, linearity, or jitter, and it cannot distinguish a marginal digitizer from a good one. Those are analog properties measured with test patterns, not descriptor fields. It also cannot tell you whether an application will honor pressure; that depends on the app's API support, not on the panel.

Cross-platform comparisons are limited. Windows exposes a relatively rich pen and touch info surface through Settings and Device Manager. iPadOS exposes Apple Pencil settings but far less raw descriptor detail. macOS exposes Bluetooth and tablet settings but not a unified pen and touch capability view. A user comparing "pen info" across platforms is comparing three different abstractions, not three measurements of the same thing.

Finally, the information is only as current as the driver and firmware loaded at that moment. A panel that looks correct can still hide a stale firmware bug that appears only under sustained input. When behavior and the panel disagree, trust the behavior and test with a known-good reference device.