Quick answer
What Multi-Touch Test tells you
Count simultaneous browser touch contacts and compare them with navigator.maxTouchPoints.
- Observed here
- Simultaneous contacts, Maximum observed contacts, Browser-reported maximum.
- A normal result means
- The expected browser event, stream or value reached this page during this session.
- Important limit
- Results reflect events and values exposed by this browser.
- Data handling
- Pointer positions, clicks and touch trails stay in this browser and are not transmitted.
Understanding the result
What a result means
Use repeated observations and compare the live indicators. A normal result means the browser received the expected events or values during this session.
A successful indicator means the expected event or stream reached this page. A missing or unusual value is a reason to repeat the action and compare conditions; it is not, by itself, proof that a component needs repair.
How to use this test
- Read the privacy and compatibility notes.
- Start the test and interact only inside the marked test area.
- Repeat the action several times and compare the live indicators.
- Use the troubleshooting section before deciding that hardware is faulty.
What this test checks
- Simultaneous contacts
- Maximum observed contacts
- Browser-reported maximum
- Per-contact markers
What this test cannot check
Results reflect events and values exposed by this browser.
This test does not certify hardware or replace professional inspection.
System gestures may reserve some multi-finger combinations.
Common problems and troubleshooting
Reload the page, confirm the test area has focus, check browser permissions and connection, then compare a current second browser. If the same fault remains across devices, contact the manufacturer or a qualified technician.
- Confirm focus and support. Click inside the marked test area and review the compatibility status above.
- Check the connection. Reconnect a cable, receiver, Bluetooth device or media device where relevant.
- Review permission and settings. Check the browser site controls and operating-system privacy, input, output or scaling settings.
- Remove competing conditions. Close another app using the device, keep timing pages visible and reduce heavy system load.
- Compare safely. Repeat the same action in a second current browser or another port/computer when practical.
If a consistent problem remains across applications and connections, contact the manufacturer or a qualified technician with the repeatable observations.
Browser compatibility
Uses feature detection. Chrome, Edge, Firefox and Safari can expose different capabilities and permission behavior.
HTTPS is required for camera, microphone and some output-selection features. Background tabs can throttle animation and input timing. Mobile system gestures may reserve some touch combinations.
| Browser | Reference status | Last reviewed |
|---|---|---|
| Chrome | Supported | 2026-08-27 |
| Microsoft Edge | Supported | 2026-08-27 |
| Firefox | Partial | 2026-08-27 |
| Safari | Partial | 2026-08-27 |
Privacy information
Pointer positions, clicks and touch trails stay in this browser and are not transmitted.
The public analytics allowlist does not accept pressed keys, typed text, pointer coordinates, media labels, device IDs, recordings, video frames or controller input. Test results are not written to LocalStorage.
Primary technical references
These specifications define the browser signals used by this test. They document web-platform behavior; they do not certify a particular device.
Frequently asked questions
Is this Multi-Touch Test free?
Yes. The test works without an account, download or payment.
Is my test data uploaded?
Pointer positions, clicks and touch trails stay in this browser and are not transmitted.
Does this result prove my hardware is faulty?
No. It shows what the browser can observe. Repeat the test, compare another browser or device, and seek qualified support when the result matters.
Why might the result differ in another browser?
Browsers, operating systems, permissions, drivers and power-saving behavior expose or schedule device events differently.