Touchscreen Test

Browser touch events are useful for functional checks but do not replace manufacturer calibration or hardware diagnostics.

Touch, tap, or use a pen here

0Active contacts

0Maximum contacts

—Last pointer type

—Last pressure

What the browser can measure

Start with a functional check, measure only what the browser can actually expose, then retest after one change.

ConnectChoose the actual browser-visible device or grant permission when required.

TestConfirm basic signal, input, output, preview or display behavior.

MeasureUse browser-exposed levels, timing, resolution, FPS, axes or event data.

DiagnoseCompare the symptom with the specific diagnostic instead of relying on one number.

RetestRepeat after changing the device, cable, permission, browser or system setting.

Pre-call Mic Webcam Keyboard Mouse Gamepad Display Permissions

Browser boundary
These tools observe browser APIs and local media/event streams. They cannot certify hardware condition, bypass denied permissions, or expose measurements the browser/OS does not provide.

Touch coverage, multi-touch & event evidence

Map contacts across the test surface, inspect pointer events, and export a local evidence log. The grid is a coverage aid—not a hardware calibration certificate.

0 / 50Coverage cells hit

0Max simultaneous contacts

0Pointer events logged

50Untested cells

Time	Event	ID	Type	X/Y	Pressure

Touch or drag across the main test zone above to build a coverage map.

What this tool checks

Map browser-visible touch/pointer contacts and movement locally to help inspect dead zones and multi-touch behavior.

How to use the result

Browser touch events are useful for functional checks but do not replace manufacturer calibration or hardware diagnostics.

Privacy & browser limits

Device streams and input events used by this page are handled in your browser unless the page explicitly says otherwise. Permission, label, timing and hardware-field availability depend on the browser and operating system.

Observed touch contacts are separated from touchscreen capability claims

Pointer events and navigator.maxTouchPoints are both surfaced. Mouse/pen events are not counted as proof of touch hardware, and absent events do not certify a dead screen region without controlled testing.