Touch Support describes whether a browser (or browser profile) reports the ability to handle touch input - like from a touchscreen. This includes:

• Detecting touch events (tap, swipe, pinch).
• Recognizing multi-touch gestures.
• Reporting the maximum number of touch points the device can handle (e.g., one finger, two fingers, ten fingers).

For example, a smartphone usually reports full touch support with multiple touch points, while a traditional desktop computer with only a mouse typically reports no touch support.

Why Touch Support Matters

Websites and applications often check touch support to decide how to display content:

• A mobile site may use swipe-friendly layouts.
• A desktop site may rely more on hover or mouse events.

But beyond usability, these signals can also be used in fingerprinting and bot detection.

Touch Support as a Fingerprinting Signal

Scripts can easily query whether a browser claims to support touch. They may check:

• Does the browser report touch events?
• How many touch points are supported?
• Are gestures like pinch or zoom available?

These answers can act as unique identifiers because the combination of device type, OS, drivers, and hardware affects them.

Examples of suspicious mismatches

• A browser profile reports touch support but the environment clearly isn’t a touch device (e.g., a Windows server VM).
• The profile claims support for 10 touch points, but only a mouse is ever used.
• The User-Agent string indicates a desktop, while the touch support flags suggest a tablet or phone.

Such inconsistencies can raise red flags for detection engines and make the profile more fingerprintable.

In Short: Touch Support is the browser’s way of telling websites if it can handle touchscreen input. While it helps sites adapt layouts, it’s also a fingerprinting vector. If the reported values don’t match the rest of the profile, it can trigger detection.

What Kameleo Offers

Because Kameleo aims for realistic browser behavior when building its virtual profiles, touch support is set or masked in a way that matches the profile’s device type (desktop vs mobile) to avoid anomalies.

Why It Matters

If touch support is inaccurately reported (or inconsistent), websites or detection systems may detect automation. Properly configuring touch support helps ensure the profile looks genuine for the intended device type, minimizing detection risk.