Touchscreen Test
Touch each coverage tile and test multi-touch — mouse input never counts.
Requires a touch-capable display
Touch and drag with a finger (or pen — counted separately) to check digitizer continuity. Mouse movement is deliberately ignored: a working mouse never proves a working touchscreen.
No touch or pen input observed yet.
How to Test
- •Drag your finger across every tile until the full grid registers coverage.
- •Open the Multi-Touch tab and place as many fingers as possible to observe simultaneous touches.
- •Mouse clicks are tracked separately and never count as touch verification.
Browser Limitations
- •A single covered tile does not prove the whole screen works — cover every tile.
- •Pen input is reported separately from finger touches.
Troubleshooting Tips
- •Clean the screen; some protectors reduce sensitivity at edges.
- •If no touches register, verify the touch driver in Device Manager or System Settings.
About the Touchscreen Test
The Touchscreen Test listens to the touch events your browser receives from the operating system and shows you exactly where the digitizer reported contact. The coverage grid divides the screen into a 10×10 field of tiles: when every tile has been swept with a finger, the tool reports full observed coverage — the digitizer answered in every region it sampled. That is an observation, not a certification: a dead spot smaller than one tile can still hide between samples. The Multi-Touch tab shows the highest number of simultaneous contacts actually observed at one moment.
It is the quickest way to find large dead zones after a drop, check a screen protector for edge sensitivity loss, or confirm a used phone or tablet accepts real multi-finger input before you pay for it. For defects smaller than one grid cell — a single dead pixel-sized touch failure — the grid is the wrong instrument; judge those visually in a drawing or note app.
Tips for a reliable result
- Use the edge of your fingertip, not a fingernail or a stylus-capacitive glove — capacitive digitizers need conductive contact.
- Sweep the coverage grid slowly and overlap your strokes; a fast flick can skip a tile the hardware actually answers.
- Clean the screen first. Oil and dust change capacitance and can hide a working zone or fake a dead one.
- If you use a screen protector, test with it on — cheap or thick protectors blunt sensitivity near the edges, and that is exactly what the grid exposes.
- Use your bare finger. The coverage grid tracks pen input separately from finger touches, and mouse input is recorded but never counted toward a touchscreen result — a mouse click cannot light up the verdict even on a desktop that also reports pointer events.
- For Multi-Touch, rest several fingers on the glass at once rather than tapping in sequence — only simultaneous contacts count, and the verdict reports the highest count observed in that session.
Common problems and fixes
Some tiles never fill in (dead zones)
Clean the screen and remove the protector, then retest with a slower, overlapping sweep — a missed tile looks identical to a dead one. If the same tiles stay blank on a second careful pass with a bare, clean screen, that is a strong hint of a hardware fault worth documenting while a warranty or return window is open, but confirm it in another app first. Remember the grid samples regions, so a tiny dead spot inside an otherwise-responsive tile can still slip through.
Coverage passes but touches feel wrong in apps
The grid proves response per region, not touch accuracy. Ghost touches, jitter, or a miscalibrated digitizer show up as taps landing elsewhere — restart the device first, then compare against another touch app to separate hardware from software.
Multi-Touch never passes on the browser
Place fingers on the pad before moving them — some devices report new contacts only while a gesture is active. Two or more simultaneous contacts observed at once is a pass; a low observed count does not prove the hardware limit, and browsers cap what they report anyway.
The page scrolls instead of covering tiles
The grid requests exclusive touch handling, but only inside the pad. If scrolling still wins, reload and start the drag from well inside the grid rather than its border.
Notes for specific systems
iOS / iPadOS
- Use Safari — touch reporting in embedded browsers (Chrome on iOS) follows the same system events, but Safari is the reference.
- If touches do not register at all, check that Guided Access or a kiosk profile is not restricting touch to part of the screen (Settings → Accessibility).
Android
- Enable Developer options → Pointer location to cross-check where the system itself sees contact.
- A “Palm rejection” feature can suppress broad contact surfaces — rest fingertips, not the flat of your hand, on the glass.
Windows / Linux touch displays
- External touch monitors need their HID touch connection (USB) seated — the video cable alone does not carry touch.
- If touch lands on the wrong display, realign in Settings → System → Display → Touch (Windows) or your desktop’s tablet/pointer settings (Linux).
FAQ
What does a PASSED coverage result actually prove?
That the digitizer reported genuine touch or pen contact in every one of the 100 grid regions during this session. It is an observation, not a certification: the tool does not test every pixel, and a dead spot smaller than one tile can still exist between samples. It also says nothing about touch accuracy or pressure sensing.
Does the Multi-Touch result show my screen’s maximum touch count?
No. It shows the highest number of simultaneous contacts actually observed in that session — nothing more. Browsers expose no hardware limit, so a device that passed with two fingers is not certified to accept only two, and a higher count elsewhere would not be contradicted.
Why does mouse input never count?
A mouse reports one contact by definition. Counting it would let any desktop claim touchscreen coverage without touching a screen, so the tester tracks it separately and never lets it contribute to a touch result.
Can a screen protector cause dead zones?
It can. Thick glass, poor adhesion, or air gaps at the edges raise the distance between your finger and the digitizer. Retest without the protector: if the blank tiles fill in, the protector is the cause.
Is anything about my touches uploaded?
No. Contact coordinates render locally and vanish when you close the tab — the test runs entirely in your browser.