Run a browser-based touch screen test on the device that is failing. Check ghost touch, dead zones, missed taps, edge response, drag trails, and multi-touch without installing an app.
Ready to start. 0% of the grid was covered on pass one. Confirmation pass has not been started yet. No active contacts. No last touch position. No touch evidence yet.
Online Touchscreen Tester
Touch Screen Test
Test your touchscreen online on the affected device. Map missed taps, dead zones, drag trails, edge and corner response, and multi-touch behavior.
It only maps touch reported in this browser — not lock-screen behavior, other apps, or whether a digitizer needs repair.
Use the actual touch surface, not a mouse or trackpad. Trace the center, corners, edges, keyboard area, gesture area, and any spot where touch response feels unreliable. On iPad, use the mobile site on the device itself — desktop-site mode can make touch harder to read.
Hands-Off Ghost Touch Check
Ghost Touch Test
Run the timed ghost touch test when the screen taps, swipes, or drifts by itself. The hands-off check watches for browser-reported touch input while the display is untouched.
A quiet 20-second run cannot prove the cause or rule out intermittent ghost touch that does not appear during this check.
Place the device flat and keep your hands, case edges, cable, and other objects off the glass until the 20-second timer ends.
Touch Screen Test is a working diagnostic, not a quiz. Run it on the failing device itself: the main test maps where touch fails — dead zones, missed taps, weak edges, broken drag trails, multi-touch dropouts — and the ghost touch check catches the opposite problem, input the screen reports when nobody is touching it. You finish with a named verdict backed by numbers, not a vague pass or fail.
Match what you are seeing to the right mode. The result shows what this browser received; it does not name the failed part.
Swipe sideways to compare columns.Scroll table to view all columns.
What's happening table
What's happening
Best mode
A fixed area misses taps or swipes
Main touch screen test
Edges, corners, keyboard, or gesture area miss input
Main touch screen test
Pinch, zoom, drawing, or games feel unstable
Main touch screen test (multi-touch)
The screen taps, types, swipes, or opens apps by itself
Ghost touch test
Touch only misbehaves while charging
Test unplugged first, then compare both modes
Seeing a visible mark, ghost image, or static UI shadow instead of touch problems? Run the burn-in test to check image retention and OLED burn-in before you troubleshoot touch input.
Quick check: is your touch screen working?
Run the main test at the top of this page on the device itself. Cells light up where touch registers and stay blank where it doesn't — if the same spot stays blank after a second pass, you've found a real failure rather than a rushed swipe. The report names a verdict when you finish: possible dead zone, no repeat failure found, or retest needed. Detailed steps follow below.
Before you treat the screen as failed
Many touchscreens that look broken are really an accessory, charger, or software issue. Rule those out before treating the display as failed.
1.
Restart the device, then clean and dry the glass.
2.
Remove stickers, loose protectors, and any case pressing on the edge.
3.
Unplug charging, USB-C, or Lightning accessories.
4.
Retest bare and slowly on the actual touch surface.
5.
If touch works after removing an accessory, swap the outlet, cable, charger, protector, or case before blaming the screen.
How to run the touch screen test
Open this page on the device that's failing and trace the whole surface slowly with one finger. Then retrace whatever stayed blank. A miss that repeats in the same spot is evidence; one rushed swipe is nothing. Swipes are captured as continuous paths, so a gap in coverage points at the glass, not at a missed sample.
1.
Clean, dry, and uncover the screen.
Remove moisture, gloves, loose protectors, and any case pressing on the edge.
2.
Run one broad first pass.
Trace slowly across the center, corners, edges, keyboard area, gesture area, and the spot that fails in normal use. Aim to cover roughly 70% or more.
3.
Run the confirmation pass on missed cells.
Go back over anything the first pass left uncovered. The tool only calls a dead zone when the same area stays unconfirmed twice.
4.
Use fullscreen if edges are cut off.
Browser chrome can steal edge and corner space; fullscreen hands the tool the whole surface.
5.
Check multi-touch if gestures fail.
Place two, three, then five separated fingers if the device supports it, and watch whether contacts drop, merge, or jump.
Multi-touch test: pinch, zoom, and games
Pinch-to-zoom lives or dies on two contacts; mobile games often expect five or more. With the device flat, add fingers one at a time and watch whether any drop off, merge into a single point, or trail behind the rest. Your report shows the highest count the browser saw next to what the device claims to support — a gap between the two numbers is worth screenshotting before a warranty call.
Use fullscreen for edges and corners
Dead zones cluster at edges and corners, exactly where browser chrome steals space. Tap the fullscreen control before you start and those zones get tested against real glass instead of a shrunken canvas. If edges only pass in fullscreen, note that in your result — some cases and curved-edge protectors cause precisely that pattern.
Testing with a stylus or pen
Pens register through the same pointer events as fingers, so active styluses work here without any setup. Trace slow lines across suspected areas and rest your palm on the glass while drawing — good palm rejection ignores the hand completely, while a failing panel may register both. Pressure readouts only appear on force-sensitive hardware; most finger panels report none, and the tool says so rather than inventing numbers.
Ghost touch test: when your screen taps by itself
Set the device down flat, start the hands-off check, and keep every hand and object off the glass for the full 20 seconds. Anything the browser logs in that window came from the screen, not from you.
Set up the device so real touches, moisture, accessories, or charging behavior do not confuse the result.
1.
Clean, dry, and uncover the screen.
Remove moisture, debris, loose protectors, and tight case pressure if safe.
2.
Place the device flat and start ghost mode.
Do not hold the device by the glass or rest a finger near the edge.
3.
Keep hands off during the timed check.
Unexpected dots, traces, or contact counts during the 20-second window are the evidence to note.
4.
Repeat once after changing one variable.
Compare unplugged versus charging, with and without the case or protector, or in another browser if the result is unclear.
Dead zone test: find the spot that ignores your finger
A dead zone is an area that ignores touches you are making — the opposite of ghost touch. This test maps them down to one or two grid cells: whatever stays unconfirmed after the second pass is the pattern that matters.
What dead zones look like in your results
On the grid, confirmed cells turn green; anything left hatched after the confirmation pass failed twice. A connected band running edge to edge is the strongest signal this test can produce, and clusters that touch an edge score higher confidence than isolated interior cells.
Scattered single misses are different. They usually mean rushed technique, moisture, or an unstable grip — which is why the tool asks for the confirmation pass before calling anything.
What causes them: strip, spot, or edge
The shape of the failure hints at the cause long before anyone opens the device. Capacitive digitizers sense in rows and columns, so certain patterns map to specific faults:
Swipe sideways to compare columns.Scroll table to view all columns.
What you saw table
What you saw
Likely cause
What the test shows
Next step
A clean strip across the width or height
Digitizer sense-line failure
Connected band, identical on both passes
Panel replacement quote
Corner cluster after a drop
Pressure crack in the digitizer
Cluster touching an edge, repeats twice
Back up the device, then repair quote
Thin unresponsive band along one edge
Case pressure or protector overhang
Passes bare, fails cased
Reseat or replace the accessory
Whole-screen intermittent failure
Loose flex cable or connector
Random multi-region misses
Service — this one rarely stays software
Pinch loses fingers mid-gesture
Digitizer channel limit or firmware
Observed count below reported max
Compare spec; service if degraded
None of these patterns name the failed part with certainty — that takes bench tools. What they do is turn "my screen is broken" into evidence a repair tech can act on, which is usually the difference between a quoted fix and a guessing game.
Touch sensitivity and response
People mean three different things by "sensitivity": whether light touches register at all, how quickly the screen reacts, and how fast the panel samples finger position. The first is genuinely testable in a browser — coverage gaps show up directly. The other two are not, and honest tools say so.
Sampling rate is how many times per second the digitizer reports position — roughly 60 to 120 on most phones, faster on gaming models. Latency is the delay between contact and reaction. Neither appears in milliseconds here, because browsers deliver input in batches; measuring them properly needs native diagnostics or specialized hardware.
So use this test for what it proves: where touch works, whether traces stay continuous, and how many contacts register together. If traces look smooth here but games still feel laggy, compare your device's refresh and sampling specs and test inside the affected game — that combination separates panel problems from software ones.
Touch screen test codes (*#0*# and friends)
Android brands hide hardware test menus behind dialer codes, and several include a touch sweep. They're free, official, and instantly available — the catch is that every brand uses its own code, some change by model, and none of them produce evidence you can hand to anyone.
Swipe sideways to compare columns.Scroll table to view all columns.
Brand table
Brand
Dialer code
What you get
Samsung
*#0*#
Hardware menu — TOUCH runs an edge-to-edge panel sweep
Xiaomi / Redmi / Poco
*#*#64663#*#*
Hardware item tests, including touchscreen
OnePlus
*#808#
Engineering mode with a touch test module
Oppo / Realme
*#899#
Engineering mode covering screen and sensors
Huawei / Honor
*#*#2846579#*#*
Project menu with hardware diagnostics
iPhone, Pixel, most others
No public code
Built-in diagnostics apps or a browser test like this one
Codes are worth trying first on brands that ship them — they come from the manufacturer and cost nothing. Where they end: they vary by model and region, they disappear on iPhones and Pixels entirely, and nothing they show can be saved or shared. Codes checked against manufacturer documentation August 2026. That's the gap a browser test fills — same device, no memorizing, and a result card attached to the end:
Swipe sideways to compare columns.Scroll table to view all columns.
Capability table
Capability
This browser test
Basic tap-only testers
App or manufacturer diagnostics
Access
Runs in the browser on the affected device, no install.
Usually browser-based, tap checks only.
Usually need an install or a supported device.
Dead-zone mapping
Taps, swipes, traces, plus a confirmation pass.
May only show whether single taps register.
Varies by app; device-specific when available.
Edges and drag trails
Checks corners, edges, gesture areas, and broken trails.
Often weak on trails and edges.
Some test closer to the system layer.
Ghost touch
Hands-off observation mode with honest limits.
Usually missing or informal.
Some devices include related diagnostics.
Android dialer codes (*#0*#)
No code to remember — runs on every brand, right here
Not applicable
Samsung opens a hardware menu via *#0*#; Xiaomi, OnePlus, and others ship their own engineering codes
Limits
Reproduces and documents symptoms; can't name the failed part.
Limits are often unclear.
Only covers supported checks.
What your result means
When a run ends, the tool gives you a named verdict instead of a raw pass or fail, backed by the numbers behind it: first-pass coverage, how much of the missed area you rechecked, the most simultaneous touches seen against your device's maximum, and how many cells failed twice. Here is what each verdict means, how far to trust it, and what to do next.
Swipe sideways to compare columns.Scroll table to view all columns.
Verdict table
Verdict
What it means
How far to trust it
Next step
Possible dead zone
The same area stayed unconfirmed twice
High — the strongest signal this test gives
Retest once more bare and clean, then open the dead-zone guide
No repeat failure found
Everything missed on pass one was covered on pass two
Moderate — reassuring, not proof
Switch to the ghost check if the screen acts on its own
Retest the remaining gap
A few small misses stayed uncovered
Low — inconclusive either way
Redo that patch slowly, ideally in fullscreen
Ghost touch contacts seen
Contacts appeared while nobody touched the glass
Real signal; cause still unknown
Repeat unplugged, bare, and dry before concluding anything
One pass complete
The confirmation pass hasn’t run yet
Not a result yet
Finish the confirmation pass on the missed cells
Preview only
A mouse ran the layout
Nothing was tested
Open the page on the actual touch device
Possible dead zone
High confidence
What you saw
The same strip, corner, or patch stayed unconfirmed after the confirmation pass.
What it means
A localized touch problem is likely, the strongest signal this browser test can give. Confidence is highest when the repeat gap is a connected cluster or sits on an edge. Don't assume it names the failed part or proves warranty status.
Cells missed on pass one were all covered on the confirmation pass.
What it means
No fixed dead area was reproduced this session. A clean run is reassuring but not proof the hardware is perfect. Don't assume intermittent faults, lock-screen, or other-app issues are ruled out.
Next: If the screen acts on its own, switch to the ghost touch test above.
Retest the remaining gap
Low confidence
What you saw
A few cells stayed unconfirmed, but the gap is small or scattered.
What it means
Not conclusive either way. Don't assume a couple of missed cells is a dead zone.
Next: Retest that patch slowly, ideally in fullscreen, before treating it as hardware.
Ghost touch contacts seen
Confirm by repeating
What you saw
During the 20-second hands-off check the browser logged touch contacts while nothing touched the glass, sorted into taps, swipes, and stuck or drifting contacts.
What it means
Possible ghost touch or electrical input noise, and a contact that persists or moves is a stronger signal than isolated taps. The report also flags whether contacts were Localized (consistent with a crack, a pressure point, or a protector edge) or Scattered (more like electrical noise, charging, or moisture). Confidence rises when it repeats after drying the screen, removing the case, and unplugging the charger. Don't assume it identifies the cause or proves a component is broken.
One sweep is done, but the missed cells have not been rechecked.
What it means
This is not a result yet, one incomplete sweep is weak evidence. There is no confidence until the confirmation pass runs. Don't assume an unfinished pass shows a dead zone.
Next: Run the confirmation pass on the uncovered cells.
Preview only (no real touch)
Not a result yet
What you saw
The run used a mouse or trackpad, so it only previewed the layout.
What it means
Nothing about the touchscreen was actually tested. Don't assume a mouse preview reflects touch health.
Next: Open the page on the actual touch device and run it there.
The four things a touch screen test surfaces: a covered, responsive area; a dead zone that ignores touch; a drag trail that breaks; and ghost-touch contacts that appear with no finger on the glass.
Boot Safe mode (hold power, then long-press Restart on most phones) and repeat the same drag path — if the miss vanishes there, a downloaded app is intercepting touch. Some brands also expose dialer codes: *#*#64663#*#* on Xiaomi and Redmi, *#808# on OnePlus. When the same strip fails twice across browsers and apps alike, you're looking at hardware.
iPhone & iPad touch screen test
The classic manual method: open Notes, hold and drag diagonal lines across the screen, and watch for breaks. It works — this test does the same job with two upgrades. Interpolated paths catch gaps that fast Notes swipes sail over, and the confirmation pass stops one rushed line from being called a dead zone. Remember Safari delivers at most 5 simultaneous touches to any website, and use the mobile site rather than desktop-site mode on iPad.
Samsung Galaxy
Dial *#0*# and pick TOUCH to sweep the panel edge to edge — the fastest official check on any phone. Layer Samsung Members diagnostics on top for a recordable result, and check Touch sensitivity under Settings if taps feel weak. Protector fit matters more on curved Galaxy panels than most; test bare once before concluding anything.
Google Pixel
On supported Pixels, run the built-in Touch diagnostics and check Adaptive touch or Screen protector mode — both quietly reshape how edges register. Note whether misses follow one app or appear everywhere; app-only failures point at that app, not the panel. Pixels ship no dialer code for touch, so the browser result carries the evidence load here.
Windows laptops, Surface & monitors
Restart into UEFI and trace the same areas: touch that works there but not in Windows points to a driver or update, not hardware. In Windows, confirm HID-compliant touchscreen is enabled in Device Manager and install optional updates — touch drivers hide there. On external monitors, reseat the USB cable before blaming the panel; touch travels over it.
Chromebook
Restart first, then run the same test in a guest-browsing window to rule out an extension. Install ChromeOS updates next; if touch still fails after that, follow your manufacturer's recovery steps — software is largely ruled out by then.
Save, share, or document your result
When a run ends, tap Save result card. You get a PNG with the verdict and the numbers behind it — coverage, repeat misses, simultaneous touches — stamped with the date. Hand it to a repair shop, attach it to a warranty claim, or send it along in a used-device deal so nobody has to take anyone's word.
The card covers the tool's side. Pair it with a photo of any visible damage and a note of whether the device was charging when symptoms showed — that answers most of what support desks ask first. For the fuller paper trail, document the issue for warranty or support before making permanent changes.
Repair or retest? Knowing when you're done
Retest beats guesswork. When the same verdict survives the rule-out checklist twice, stop testing and act:
Seek official device support when the same area keeps failing after basic checks, ghost touch makes the device act by itself, touch fails system-wide, or built-in diagnostics report a touch problem. If the phone is becoming hard to unlock or control, back up a phone with a broken screen while you still can.
After you document the pattern, compare whether to repair or replace the screen. If there is visible damage, pressure damage, liquid exposure, or a failed repair, also check whether a broken display can be repaired before committing to a service path.
Sources checked
These official device-maker and platform support pages were checked on June 29, 2026 for troubleshooting steps, diagnostics, service limits, and touch settings.
Open this page on the device that's failing, then run one broad pass across the whole surface and a confirmation pass over anything you missed. Use your finger on the actual glass, not a mouse or trackpad, and switch to fullscreen if the browser bar hides the edges. A repeat miss in the same spot is real evidence; one rushed swipe is not.
What is ghost touch?+
Ghost touch is unwanted input: the screen taps, swipes, types, drifts, or opens apps while nobody is touching it. It is the opposite of a dead zone, where an area ignores touches you do make. Use the ghost touch test, flat and hands off for 20 seconds, to see whether the browser logs contacts on an untouched screen.
How do I tell ghost touch from a dead zone?+
Ghost touch is input you did not make; a dead zone is a spot that ignores input you did make. Run ghost mode hands-off for random taps or drift. Run the main touch screen test when a strip, corner, keyboard area, or gesture zone misses taps or breaks a drag line.
How do I test for dead zones?+
Trace slowly across the whole screen on the first pass, then rerun the confirmation pass over any area that did not respond. The tool only flags a possible dead zone when the same cells stay uncovered twice, since a single miss usually just means you rushed. Test bare and clean first, because a case or lifted protector can fake a dead spot.
How do I stop or fix ghost touch?+
Start with causes this test can reveal: dry the screen, remove a tight case or lifted protector, and unplug the charger, then retest. If ghost touch only appears while charging, swap the cable, charger, or outlet. If it keeps happening untouched and bare, it may be hardware, so compare ghost touch after damage and back up the device before it becomes hard to control. This tool documents the symptom; it cannot repair it.
Can a case or screen protector cause missed touches or ghost touch?+
Yes. A lifted or cracked protector, trapped moisture, edge debris, or a tight case pressing the glass can cause missed touches or unstable input. Test once with the device clean, dry, and bare if it is safe to remove the accessory. If touch works bare, refit or replace the accessory before assuming the display failed.
Can this test prove my touchscreen hardware is broken?+
No. It shows whether the browser receives your touches and whether a pattern repeats, but it cannot identify the failed part or separate a display, controller, driver, app, firmware, or accessory issue, and it cannot decide warranty eligibility. Treat a repeatable result as evidence to document, not a diagnosis.
What should I do before trusting a failed touch screen result?+
Clean and dry the glass, remove gloves, unplug charging accessories, and take off a tight case or loose protector if safe, then restart and repeat the same path slowly. One missed swipe is weak evidence; the same missed area or unwanted touch after a controlled retest is what matters.
Why does ghost touch happen while charging?+
A cable, charger, outlet, or grounding issue can inject electrical noise that the screen reads as touch. Unplug and run the ghost touch test again. If it stops unplugged, compare a different outlet, cable, and charger before blaming the screen.
Why does touch work in some apps but fail in the browser test?+
The browser, operating system, an accessibility setting, or the touch-event path can behave differently from another app. Try a second browser or a built-in diagnostic if your device has one. If normal apps also fail in the same physical area, the browser result carries more weight.
Can I use this on iPhone, Android, iPad, Surface, or a touchscreen laptop?+
Yes, as long as the affected device and browser expose touch input to the page. Run it on the actual touch surface, not from another device. For Samsung, Pixel, Surface, and Windows, compare repeat failures against the maker's diagnostics when available.
When should I stop testing and contact support?+
Stop when ghost touch makes the device hard to control, the same dead zone keeps returning, touch fails system-wide, or the trouble started after a drop, liquid, pressure, or repair. Save the result, note whether it was charging, and back up the device while touch still works.
What is the Samsung touch screen test code?+
Dial *#0*# in the phone app to open Galaxy's built-in hardware menu, then choose TOUCH and trace the panel edge to edge. Other Android brands use their own engineering codes — *#*#64663#*#* on Xiaomi and Redmi, *#808# on OnePlus. Codes vary by model and don't exist on iPhones, which is exactly why a browser test that runs identically on everything is worth keeping around.
Can I save or share my test results?+
Yes. After any run, use Save result card to get a PNG containing the verdict, your coverage numbers, simultaneous-touch count, and the date. It is built for handing to a repair shop, attaching to a warranty claim, or proving screen condition in a used-device sale.
Why does my iPhone only register 5 touch points?+
Safari delivers a maximum of 5 simultaneous touches to any web page, even though iPhone hardware tracks more. Seeing 5 of 5 is the browser cap working as designed, not a digitizer fault. Judge multi-touch by whether contacts drop, merge, or misbehave — never by the number alone.
Why does my screen tap by itself?+
That's ghost touch — input the digitizer reports with nobody touching the glass. Common triggers are charger ground noise, moisture, a lifted protector pressing the edges, or a failing digitizer. Run the hands-off check above: device flat, untouched, twenty seconds. Contacts logged in that window came from the screen; repeating the run with one variable changed narrows the cause.
Is there an app for ghost touch?+
Apps exist, but they read the same input layer a website reads — neither sees the digitizer directly. A browser test adds things most apps skip: a timed hands-off watch, a classification of where contacts cluster, and a downloadable result card for your repair quote. No install, no permissions, works on every brand.
Does a dead zone mean I need a new screen?+
Not automatically. A repeating strip or band often means digitizer damage, which usually ends in screen replacement — but edge-only misses can be a tight case or lifted protector, and frozen touch can be software entirely. Work through the rule-out checklist, confirm the pattern twice in this test, then take the saved result card to a repair quote.
How accurate is an online touch screen test?+
Accurate about what it measures: whether touches reach the browser, where coverage breaks, and how many contacts register together — down to roughly one or two grid cells, with swipe paths interpolated so fast strokes cannot fake clean passes. It cannot measure sampling rate or latency in milliseconds, see other apps or the lock screen, or name the failed part. Treat repeated patterns as strong evidence, not a formal diagnosis.
