TestBenchmark logoTestBenchmark

Touch Screen Test

This touch screen test checks whether your phone, tablet or touch laptop actually registers every touch — dead zones, multi-touch limits, tap accuracy, swipe breaks and ghost touches — in one guided check with a plain-English report at the end. One honest limit up front: open this page on the device you want to test, and touch the screen with your finger — a mouse or trackpad cannot test a touchscreen, and this page will not pretend otherwise.

Your screenTouch not detected yet

The line below shows what your browser says about this device: how many simultaneous touch points it supports, and your screen size. Touch the board once and the label updates — a mouse click does not count as touch.

No touch input yet — tap the board below with a finger.

1 · Live touch board

Touch the board and every finger shows up as a numbered circle with its position. Drag to paint the grid — a cell fills the moment a finger registers there. The readouts below track coverage, how many fingers are down right now, and the most you have held at once.

Grid coverage

0%

Cells filled

0 / 200

Touches now

0

Peak at once

0

Touch the board with a finger to begin.

A mouse or trackpad stroke paints faintly and does not fill cells — only a real finger or stylus counts. On a touch laptop, touch the screen itself, not the trackpad: the trackpad only ever reports one pointer.

2 · Guided checklist

Work through the steps in any order — each one ticks itself off as you do it. A step only counts when the screen really does it: five measured taps, a finished grid sweep, two or more fingers at once, four swipe paths, a hands-off ghost watch and a 10-second tap drill.

○ Tap accuracy — 5 targets0 of 5 targets tapped
○ Paint the whole grid0% covered
○ Multi-touch — 2+ fingers at oncePeak 0 fingers
○ Swipe test — 4 directions0 of 4 paths done
○ Ghost-touch watch — 10 seconds, hands offNot run yet
○ Tap-speed drill — 10 secondsNot run yet

3 · Tap accuracy — 5 targets

Press Start and a ring appears in each corner and the centre, one at a time. Tap the middle of the ring with your fingertip — the test measures how far your tap lands from the centre, in pixels and in millimetres. Under 6 px (about 1.6 mm) is accurate, 6–12 px is slightly off, and over 12 px is poor.

Not run yet — five targets, one at a time.

Average offset

—

Worst tap

—

Verdict

—

4 · Dead-zone sweep

Drag your finger slowly across the whole board, row by row, until every cell fills — edges and corners included, since digitizer faults start there. When you have painted all you can, press “Finish sweep”. Any cell still empty after that is named as a suspected dead zone, with its grid position, in the report.

Sweep in progress — paint every cell, then press “Finish sweep”.

5 · Swipe test — 4 directions

Press Start and a guide line appears. Draw along it slowly, in the direction of the arrow, without lifting your finger. The test watches for breaks — places where the trace stops or jumps while your finger is still down — and for how much of the line you covered. Four lines: left to right, right to left, top to bottom, bottom to top.

Not run yet — four paths, one at a time.

Left → right

—

Right → left

—

Top → bottom

—

Bottom → top

—

6 · Ghost-touch watch — 10 seconds, hands off

Press Start, then lift every finger, sleeve and cable off the screen and do not touch it for 10 seconds. If the screen registers a touch while nobody is touching it, that is a ghost touch — it is counted here with its position. If the fault only appears while charging, run the watch again with the charger plugged in.

Not run yet — hands off the screen for the whole 10 seconds.

7 · Tap-speed drill — 10 seconds

Press Start and a target appears on the board. Tap it as fast as you can — every tap moves it somewhere new. The drill counts your taps over 10 seconds and reports taps per second. It is a speed check, not a fault check: a slow count here usually means the target is hard to reach, not that the screen is broken.

Not run yet — tap the moving target as fast as you can.

Taps

0

Taps per second

—

8 · Your touchscreen report

The report reads everything the test has seen so far and names the faulty part — or tells you the screen is healthy. Run the checklist first for a full score; the report also works on partial data and says plainly what was not tested. Copy the text version to paste into a support ticket, a repair-shop message or a sale listing.

Honest limits

A web page only sees the touch points the browser reports. It sees the centre of each touch, not the pressure, the contact area, or the offset between where you pressed and the coordinates it was given. Gestures the operating system takes first — Android's Back swipe from the screen edge, iPad multitasking gestures — and the system bar areas at the top and bottom cannot be tested. Safari on iPhone reports 5 as the maximum number of simultaneous touches whatever the device, and has no fullscreen, so the very top and bottom edges stay partly untested. And a browser test cannot repair a digitizer: it can only show you where the fault is, so you can decide about a repair with evidence in hand.

How to test your touchscreen in 6 steps

1 · Open this page on the device itself. The test can only check the screen it is running on. Open it on the phone, tablet or touch laptop you want to check, in its own browser — a desktop browser cannot test a phone in your hand. Wipe the screen, dry your hands, and remove the case: moisture, grease and a bumper overlapping the edge all change the result.

2 · Tap the five accuracy targets. Press “Start accuracy test” and tap the middle of each ring as it appears — four corners, then the centre. The test measures how far each tap lands from the ring's centre, in pixels and millimetres. If your taps keep landing a few millimetres off in the same direction, the screen's touch calibration is off — or a thick protector is shifting what it feels.

3 · Paint the whole grid. Drag your finger slowly across the board, row by row, overlapping slightly, then repeat with vertical bands — edges and corners included, since digitizer faults start there. When you have painted all you can, press “Finish sweep”. A cell that stays empty after several slow passes from different directions is a suspected dead zone.

4 · Count your multi-touch points. Place fingers down one at a time and watch the peak count climb. Most modern phones reach 10; budget phones and older tablets stop at 5. If the count stops well below five, or fingers already down jump position when you add another, the digitizer is either low-specification or faulty — and games that need a joystick plus buttons will suffer first.

5 · Draw the four swipe paths. Press “Start swipe test” and draw each guide line slowly, without lifting your finger. A line that breaks at the same spot every time you cross it is the classic signature of a broken sensor line — the position stays on the near side, then jumps across all at once.

6 · Run the ghost-touch watch, then read your report. Press “Start 10-second ghost-touch watch” and lift every finger off the screen. Then press “See my touchscreen report” for a score, a plain list of any faults found — with the faulty part named — and what to do about each one. If the fault only appears while charging, run the watch once more with the charger plugged in before you decide anything.

What is a digitizer?

Under the glass of every touchscreen is a transparent sensor layer called the digitizer. It is a grid of fine conductive lines that senses where your finger disturbs a tiny electrical field, and turns that into coordinates the screen can use. It is separate from the display panel underneath, which only makes the picture. When the digitizer fails in one place, that patch of screen stops responding to touch while the picture stays perfectly visible — which is why a screen can look fine and still ignore your finger. A full digitizer failure means no touch input is recognised at all. The two layers are laminated together in modern phones, so a digitizer repair usually means replacing the whole screen assembly.

Dead zones — what causes them

A dead zone is a patch of screen where touch is never registered. The common causes, in order: a cracked digitizer after a drop — even a hairline crack with no visible damage to the glass can sever a sensor line; debris or moisture trapped under a screen protector; a thick or lifting protector that insulates the finger's electrical field; and a loose or damaged ribbon cable connecting the digitizer to the phone. The shape tells you something: a vertical stripe usually follows one damaged column of the sensor grid, a horizontal band follows one row, and a dead corner is often where drop damage concentrates. Before you call it a dead zone, rule out the cheap causes — clean the screen, remove the protector, restart the device, and test again in a different browser. A true dead zone is a cell or patch that never fills despite repeated slow passes directly over it, while the cells around it fill normally.

Ghost touch — causes, ranked

Ghost touch is the opposite fault: the screen registers touches nobody made. The causes rank like this. First, the charger. A cheap, uncertified or failing charger injects electrical noise that destabilises the touch controller's ground voltage — if the phantom taps happen mainly while charging, swap the charger before blaming the screen. Second, a damaged or moisture-contaminated screen protector. Third, extreme heat. Fourth, after a drop, a loose digitizer connector. Software can misfire too, after an OS update — test in safe mode on Android, or after a restart on iPhone, to rule that out. Persistent ghost touch in the same spot, with no charger attached and a clean screen, usually means the digitizer layer is failing and the panel needs service.

How many touch points should your screen detect?

The number of simultaneous fingers a screen tracks is called its multi-touch point count. The table is:

10 points — full multi-touch. Most modern phones and tablets. Pinch, rotate, two-finger scrolling and multi-finger games all work. 5 points — common on budget tablets and older devices. Perfectly usable, and the full score on an iPhone, where Safari reports 5 whatever the hardware. 2–3 points — a very low-cost panel, or a fault. Games and drawing apps suffer. 1 point — the trackpad is being read, not a touch screen. On a laptop this means you are touching the trackpad; touch the screen itself instead. Whatever the number, what matters most is that fingers already down stay put when you add another — if they jump or vanish, something is wrong even if the peak looks right.

Here is a worked example from the accuracy test itself. A target sits at the centre of its ring, and your tap lands 4 pixels to the right and 3 pixels up. The offset is the square root of 4² + 3², which is exactly 5.0 pixels — about 1.3 millimetres at 96 pixels per inch — so the verdict is accurate. The same maths runs on every tap: under 6 pixels is accurate, 6 to 12 pixels is slightly off, and over 12 pixels is poor. And a swipe example: a 680-pixel guide line sampled every few pixels, with the largest gap between two consecutive samples just 12 pixels and 96% of the line covered, passes with no breaks — a gap over 40 pixels while the finger is still down is a break.

Per-device first steps

iPhone / iPad: restart the device, make sure the screen is clean and free of debris or water, disconnect any Lightning or USB-C accessories, and remove any cases or screen protectors. If it works without the accessories, try a different outlet, cable or charger. iPad, several fingers: in Multitasking & Gestures settings, turn off the four-finger and five-finger gestures and count multi-touch again. Galaxy: if you fitted a screen protector, turn on Settings > Display > Touch sensitivity — the phone diagnostics in the Samsung Members app can check the touch screen too. Pixel: on a Pixel 8a or earlier, turn on Screen protector mode in Settings > Display & touch > Touch sensitivity; on the Pixel 9 series, run the touch diagnostic test and see whether Adaptive touch helps. Android in general: turning on Pointer location in developer options draws the coordinates and path of each touch over the screen, and Show taps draws a circle where you touch — compare them with this test at the same spot. Windows touch laptop: restart the device and check for Windows updates; if it is still the same, contact the device manufacturer.

Before you call it dead

Work through this checklist before concluding a zone is faulty — every item here has fooled someone into replacing a good screen. Remove the screen protector — a lifted or thick protector kills touch sensitivity in patches. Clean and dry the screen — moisture and grease cause phantom or missed touches. Restart the device — a glitched touch controller often clears on reboot. Re-test in a different browser to rule out a software issue. Rub from the inside toward the edge — Android's Back gesture steals inward swipes from the very edge, so edge cells must be painted from the inside out. Rotate the screen and finish in one orientation — rotating mid-test changes the cell layout. And look for repeats, not single marks: a swipe break that appears once can be the browser being briefly busy; a break at the same spot every time is the fault.

Repair or replace?

Repair it — or rather, replace the screen assembly — when the phone is under warranty, when the dead zone is small and the rest of the screen is healthy, or when the device is worth more than the repair costs. A dead zone caused by the protector or the charger costs nothing to fix: remove the protector, swap the charger. Replace the whole device when the digitizer fault spreads across the screen, when ghost touch persists on battery with a clean screen, or when the repair costs more than half a new phone. And when you do buy a used phone, run this test before you pay: paint the whole grid, count the multi-touch points and run the ghost watch — a screen that looks fine can still ignore one line or a corner, and a copied report is a written record of its condition at the time of the deal.

What this test cannot see

A web page only sees what the browser passes on. It sees the centre of each touch point, not the pressure, the contact area, or the offset between where you pressed and the coordinates it was given. It cannot test the parts of the screen the operating system claims first — the Back gesture zone at the edges, the multitasking gestures, the system bars. It cannot tell a digitizer fault from a software fault on its own — that is why the checklist asks you to restart and re-test in another browser. And it cannot fix anything: a browser test shows you where the fault is, so you can decide about a repair with evidence in hand, not with a guess.

Frequently asked questions

How do I test my touchscreen online?

Open this page on the phone, tablet or touch laptop you want to check — not on a different device — and work through the checklist: tap the five accuracy targets, paint the whole grid, place several fingers down at once, draw the four swipe paths, then run the 10-second ghost-touch watch. Each step ticks itself off as you do it, and the report at the end gives you a score with any faults named. Nothing to install, no sign-up, nothing uploaded — the whole test runs in your browser.

Why is part of my screen not responding to touch?

The usual causes are physical: a cracked digitizer layer under the glass, debris or moisture under a screen protector, or a loose ribbon cable after a drop. A thick or lifting screen protector can do it too. Before you call it a dead zone, clean the screen, remove the case and the protector, restart the device, and paint the grid again — a real dead zone stays unfilled after several slow passes from different directions, while a cell you simply missed fills on the second try.

How many fingers should my touchscreen detect?

Most modern phones and tablets track 10 simultaneous touch points; budget phones and older tablets often stop at 5, which is perfectly usable. If your screen stops at 2 or 3, or fingers already down jump position when you add another, the digitizer is either low-specification or faulty. One honest note: Safari on iPhone reports 5 as the maximum whatever the device, so on an iPhone a peak of 5 is normal, not a fault. Games and on-screen keyboards suffer most from a low count — mobile games often need 3 to 6 points at once for a joystick plus buttons.

What is ghost touch and how do I test for it?

Ghost touch — also called phantom touch — is when the screen registers touches that nobody made: apps open, the keyboard types random characters, the screen scrolls by itself. The number-one cause is a cheap or uncertified charger injecting electrical noise, then a damaged or moisture-contaminated screen protector, extreme heat, and after a drop a loose digitizer connector. To test it, press “Start 10-second ghost-touch watch” above and lift every finger off the screen. Any touch that arrives while nobody is touching is counted and its position recorded. If it only happens while charging, run the watch again with the charger plugged in.

Can I test a touchscreen with a mouse?

No — and this page is honest about it. A mouse or a trackpad is not touch: it moves a cursor, it does not press the digitizer, so it cannot tell you whether any part of your screen responds to a finger. On this page a mouse stroke paints faintly so you can see the grid, but it does not fill cells and does not count toward any result. To test a touchscreen you have to touch it — open this page on the phone, tablet or touch laptop itself and use your finger or a stylus.

Does the test work on iPhone and Android?

Yes, on both — with two honest differences. On Android, Chrome, Firefox and Samsung Internet all report touch fully, and most phones track up to 10 points. On iPhone and iPad, Safari reports a maximum of 5 simultaneous touch points whatever the device, so a peak of 5 is the full score there, and Safari on iPhone has no fullscreen, so the very top and bottom edges stay partly untested. Windows touch laptops and Chromebooks work too — touch the screen itself, not the trackpad, which only ever reports one pointer.

Why does my screen tap by itself when charging?

That is ghost touch caused by electrical noise from the charger. A cheap, uncertified or failing charger ripples the touch controller's ground voltage, and the digitizer reads that ripple as touches. Unplug the charger and the phantom taps should stop — if they do, the charger is the problem, not the screen. Try a different charger and cable, preferably the one that came with the phone. If the screen still taps by itself on battery power, with a clean screen and no protector, the digitizer layer itself is failing and the panel needs service.

Can a screen protector cause dead zones?

Yes. Capacitive touch controllers work by sensing the tiny electrical field of your finger, and a thick glass protector — especially 0.33 mm or thicker with poor adhesive — insulates that field and raises the touch threshold, so taps in one area go missing or feel sluggish. Cheap films, air bubbles and dust under the film do the same in patches. If the dead-zone grid clears up after you remove the protector, the protector was the cause. Many phones have a fix built in: turn on “Touch sensitivity” or “Screen protector mode” in your display settings and test again before you blame the screen.

How this test works: every number is measured in your browser from Pointer Events — pointerdown, pointermove and pointerup on the board, plus the browser-reported maximum touch points — with no downloads, no sign-up and nothing uploaded. A mouse or trackpad stroke paints faintly and never counts; only a real finger or stylus fills a cell.