Does my device support touch?
This reports what your hardware supports, not how you are actually interacting with the page. That distinction breaks a lot of sites: a touchscreen laptop reports touch, gets served the mobile interaction model, and then gets used with a mouse. The better question for a layout is whether the pointer is fine or coarse, which CSS can ask directly.
Whether your browser reports touch support is shown above, along with the maximum number of simultaneous touch points it claims. We read this from touch-related browser flags and the maxTouchPoints value, which indicates multi-touch capability.
Touch support is trickier to detect than it sounds. Many laptops now have touchscreens, some tablets attach keyboards, and some browsers report touch capability even when no touchscreen is present, so a positive result does not always mean you are using touch right now. It reflects capability, not your current input method.
The better modern approach, which good sites use, is to adapt to how you are actually interacting (pointer type and hover capability) rather than assuming touch means mobile. This page shows the raw capability signal so you can see exactly what a site would read.
How a website reads this
This is the exact call a page makes. Nothing else is involved, and nothing is sent anywhere: the value is read in your browser and displayed to you.
navigator.maxTouchPointsThe number of simultaneous contact points the hardware reports. 0 means no touchscreen, 5 or 10 is a typical phone or tablet. It says what the hardware can do, not what you are using: a touchscreen laptop driven entirely by trackpad still reports touch points.
- Needs your permission
- No, it is read silently
- Can it be faked
- Partly. Devtools device emulation reports touch points on a desktop machine, and extensions can override the property.
- Contribution to a fingerprint
- About 1 bits, our own estimate. Our estimate. The answer is essentially zero or not-zero for most people, so it splits the population roughly in half rather than finely. How we estimate this.
What you should know
Why sites collect it
Sites use touch support to size tap targets, enable swipe gestures, choose hover or tap interactions, and decide between touch-friendly and pointer-friendly interfaces. It shapes how usable a page feels on your hardware.
Privacy implications
Touch support is a low-entropy signal on its own, a simple yes or no plus a small number. It contributes to device-type inference and thus to a fingerprint, but it does not narrow you much by itself.
How to change or hide it
There is no direct setting to change reported touch support; it follows your hardware and browser. Requesting a desktop site can change related device signals. This is one of the less sensitive things a site can read.
Frequently asked questions
Why does my laptop report touch support?
Many laptops have touchscreens, and some browsers report touch capability regardless. A positive result means the capability exists, not that you are touching the screen now.
How many touch points can devices report?
It varies by hardware. Phones commonly report 5 or 10, while non-touch devices report 0. The number is the maximum simultaneous touches supported.
Sources
Browser behaviour changes and vendors cap these values differently, so the claims above that are not self-evident are checked against the specifications and vendor documentation below.
Last checked on . How these values are measured and estimated is set out on the methodology page.
Something wrong here? Tell us what your browser reports and it gets corrected.