Free display tests that run in your browser. Nothing is uploaded.

Input and geometry

Multi touch test

How many fingers your screen tracks at once, counted as they arrive, and whether each one is followed independently.

Put your fingers here

Contacts now
0
Peak this session
0
Platform maximum, reported
—
Pointer types seen
—
A mouse counts as one pointer, which is a quick way to check the pad is listening.

How to run this test

  1. Put one finger on the pad below and check that a dot appears under it and follows it.
  2. Add fingers one at a time, counting as you go. The live count is how many contacts your screen is reporting at this moment.
  3. Lay all five fingers of one hand down together, then both hands if the screen is large enough.
  4. Compare the peak with the platform figure underneath. They often disagree, and the peak is the one that reflects what actually happened.
  5. Move several fingers at once in different directions. Each dot should follow its own finger without swapping or sticking.

What a problem looks like

The peak stops well below the platform figure
The platform number is a maximum the driver claims, not a promise. Digitisers often report fewer simultaneous contacts than the specification when fingers are close together, and some operating systems reserve contacts for gestures. Try again with fingers spread wide.
A dot disappears while the finger is still down
A contact was dropped. Once is usually a palm being rejected or a finger touching too lightly. Repeatedly, in the same area, points at a digitiser problem, and the touch screen test with its grid is the better page for mapping where.
Two dots swap places or merge
Identity tracking failing. Each contact should keep its own identifier for as long as it is down. Merging when two fingers come close is common on cheaper digitisers and is a real limitation rather than a software fault.
Dots appear offset from your fingers
Calibration or a scaling mismatch. A small constant offset across the whole screen is usually the digitiser; an offset that grows towards the edges is usually the calibration. Neither is something a web page can correct.
Nothing happens at all
Either the device has no touchscreen, or pointer events are not reaching the page. The capability row says which. A mouse works here too, as a single pointer, which is a quick way to confirm the page itself is listening.

What to do next

If the peak matches what your device claims and each dot follows its own finger, the digitiser is doing its job. If contacts drop in one area every time, the touch screen test maps that properly with a grid.

Questions people actually ask

How many touch points should my device support?

Phones and tablets generally report five or ten. Windows laptops with touchscreens usually claim ten. Some budget panels handle two or five. There is no standard, and the figure that matters is the one you can actually reach, which is what the peak here measures.

Why does the platform number differ from what I can reach?

Because they are different claims. The platform figure is what the driver advertises. The peak is what the browser actually delivered while you were touching the screen. Fingers too close together, palm rejection, and gestures the system swallows all reduce the second without changing the first.

How is this different from the touch screen test?

The touch screen test maps your screen with a grid to find dead zones, and lets you draw to check for drift and broken strokes. This one is about simultaneous contacts: how many at once, and whether each is tracked independently. They answer different questions about the same digitiser.

Does a stylus count as a touch point?

It arrives as a pointer, so yes, it shows up here. Many devices treat pen and finger differently and some reject finger contacts while a pen is near the screen, which is palm rejection doing its job. The pointer type is shown for each contact so you can see which is which.

Why do my gestures interfere with the test?

Because the operating system claims some of them before the page sees them. Edge swipes, app switching and notification pulls are consumed by the system, which is why contacts can vanish near the edges. Working in the middle of the pad avoids most of it.