Multitouch Test
Use the multitouch test to inspect simultaneous contacts inside the active area. System gestures and browser limits may hide touches the hardware supports.
Dedicated multi-touch surface
Touch traces are not uploaded or persisted. Scrolling is blocked only inside the active surface.
What this page helps you test
Use the multi-touch tester to observe how many simultaneous contacts this browser receives. Keep fingers inside the test surface; reserved system gestures and browser limits can differ from the touchscreen's hardware capacity.
Guides for this tool
See how this check fits into real troubleshooting workflows.
If the result is not what you expected
Interact once
Press a controller button so the browser is allowed to expose the device.
Reconnect directly
Reconnect the controller or touch device and avoid an unreliable hub.
Check the mapping
Unknown mappings can move controls to different raw button or axis indices.
How it works
- Enter the dedicated touch area and place one or more fingers on the screen.
- Active pointer IDs, positions, and observed regions update locally.
- Clear or exit to discard the gesture trace while retaining only summary counts.
What this result cannot prove
- Some mobile browsers expose only limited pointer information or reserve system gestures.
- Scrolling and zoom are prevented only inside the active test surface.
Related tools
Frequently asked questions
Why does the multitouch test show fewer fingers than expected?
Keep all contacts inside the test area and avoid screen edges reserved for system gestures. Repeat in another browser if possible. The count describes contacts delivered to this page, not the touchscreen’s certified hardware limit.
Is the Multi-touch Test private?
Yes. Test input is processed in this tab and is not uploaded by this tool.
Why can browser results differ from another app?
Browsers, operating systems, permissions, device routing, and background load can all change what is exposed and measured.