Touch Screen Tester: Find Dead Zones, Ghost Touches and Multi-Touch Limits
A touch screen tester checks the digitizer instead of the pixels: how many fingers it can track at once, whether every part of the glass responds, and whether the pointer wanders when nothing is touching it. Everything on this page runs inside your browser tab — no app, no account, no input leaving the device.
A touch screen tester is a browser tool that visualizes touch input in real time. It counts simultaneous touch points, draws your finger path to reveal unresponsive bands, and scans a labeled grid so every square can be checked for dead zones. It measures the touch layer rather than pixel defects, and it cannot read the hardware touch sampling rate. Results are computed locally and are never uploaded.
- Input API
- Pointer Events, tracked by pointerId (with Touch Events compatibility)
- Max touch points
- Determined by the device and browser; the page shows the measured maximum, not a fixed claim
- Dead-zone grid
- 8 columns × 6 rows inline; 12 × 8 in fullscreen
- Dead-zone rule
- A square touched three times with no response is flagged as a suspected dead zone — this tool’s rule, not an industry standard
- Cannot measure
- Hardware touch sampling rate (Hz), digitizer model, or absolute pressure
- Data
- All touch input stays in the browser tab; nothing is uploaded or stored
How do I test if my touch screen has dead zones?
Open grid mode and work through the squares systematically. Each square you touch lights up to confirm that the digitizer reported a contact at that exact location. A square that never responds, no matter how firmly or slowly you tap it, is a suspected dead zone. Re-test it three times before marking it: a single miss is more often a dry finger, a case edge, or a missed tap than a hardware fault. Use fullscreen mode for the 12 × 8 grid when you need finer resolution near the edges, where digitizer connectors and screen protectors most often cause trouble.
Keep this separate from what you see on the panel itself. A dark dot that never changes is a pixel problem, not an input problem — pixel-level defects are checked with solid colors, while this tool only listens to where your finger lands. If a region looks discolored but still responds to touch, the digitizer is fine and the display needs a different test.
How many simultaneous touches does my screen support?
Multi-touch mode keeps a live list of active contacts by pointer identifier and records the highest count seen during the session. Place two fingers down, then three, then five; the counter and the colored dots show exactly which contacts the browser is receiving. Most modern phones report between five and ten, but the number you see is a combination of the panel controller, the operating system, and the browser — it is not a hardware specification sheet.
If a sixth finger is silently ignored, that is the reported limit, not necessarily a defect. Game controllers, edge-swipe gestures, and palm rejection can also consume contacts before the page sees them. Test in a clean browser tab with the device flat on a table for the most repeatable result.
Can a browser test detect a faulty digitizer?
It can show the symptoms. A trail that jumps between distant points suggests a grounding or calibration fault; a contact that appears with no finger on the glass is a ghost touch; a line that suddenly ends and restarts is a dead band. None of these require special equipment to observe, and recording them on video is useful evidence for a warranty claim.
What a browser cannot do is measure the touch sampling rate in hertz or identify the controller chip — those values are not exposed to web pages. A screen that fails grid mode consistently, especially along one edge or after a drop, is worth having inspected. For a guided pass over the rest of the display, continue with the screen check wizard.
What each touch test mode tells you
| Mode | What it detects | What it cannot tell you |
|---|---|---|
| Multi-touch | Simultaneous contact limit, dropped contacts | Hardware controller model |
| Draw trail | Unresponsive bands, jumps, drift, ghost touches | Absolute pressure in physical units |
| Dead-zone grid | Location of squares that never respond | Touch sampling rate in Hz |
How to test a touch screen in three steps
- Check multi-touch — Place several fingers down at once and note the maximum simultaneous contacts reported.
- Draw across the glass — Trace slow lines from edge to edge; breaks or jumps reveal unresponsive bands.
- Scan the grid — Tap every square, repeat any miss three times, then flag persistent gaps as suspected dead zones.
Questions fréquentes
What is a touch screen tester used for?+
It checks whether the digitizer reports every touch correctly: how many fingers it can track, whether any part of the glass is unresponsive, and whether touches drift or appear on their own. It tests input, not pixel damage.
How do I find dead zones on a touch screen?+
Use grid mode and tap each square in turn. A square that fails to respond after three deliberate taps is flagged as a suspected dead zone. Fullscreen mode offers a denser 12 × 8 grid for edge checking.
Is a touch screen dead zone the same as a dead pixel?+
No. A dead zone is a place where the glass does not register touch; a dead pixel is a subpixel that stays dark on the display. They come from different hardware layers and need different tests.
Can this tool measure my touch sampling rate?+
No. Browsers do not expose the hardware touch sampling rate in Hz or the digitizer model. The page reports only the events it actually receives from the browser.
Are my touch gestures uploaded anywhere?+
No. All pointer data is processed in the page and discarded when you leave. There is no account, no network request, and no stored trace.