Touchscreen Test: Check Every Part of Your Phone Screen

A touchscreen fault rarely announces itself clearly. One corner stops responding, a swipe stutters halfway, or the keyboard misses letters only when you type quickly. Because we adapt unconsciously — pressing harder, avoiding a corner, retyping — a fault can persist for weeks before anyone tests it properly. A systematic touchscreen test removes the guesswork: it checks every part of the screen, including the edges and corners people normally ignore, and produces a visible record of exactly where the screen responds and where it does not.

The Touchscreen Test is a browser-based test: you touch and drag across the screen, and it paints the areas your touches cover, so uncovered areas stand out as untested or unresponsive zones. It runs entirely in your browser on your own device, it does not install anything, and it does not need an account. Because it is a device test, the results describe the device in your hand at this moment, not a server or a website. Test with clean, dry hands, remove any case that covers the screen edge if you can, and remember that a screen protector can itself cause problems, which the test helps you separate from a genuine screen fault.

Before testing, prepare the device briefly. Close apps that might interfere, turn off any pointer or accessibility overlay that draws on screen, and clean the screen with a soft, dry cloth, because dirt and moisture create false dead spots. Note the device's current state: is a protector fitted, is the screen cracked, has the phone been dropped or exposed to water recently? Those facts matter when interpreting results, because a crack over a zone explains a dead spot, while a dead spot on a pristine screen points to a hardware or software fault that deserves a different response.

Painting the screen: the full-coverage method

The core method is simple: paint the entire screen, slowly and systematically, like colouring a map. Start in one corner and drag in overlapping rows across the whole display, covering the middle, the edges and all four corners. Slow, deliberate strokes matter more than speed, because a fast flick can skip over a small dead zone without revealing it. Pay special attention to the edges, where faults most often appear: the top edge near the camera, the bottom edge near the navigation bar, and the curved edges of phones with curved displays, where touches near the border sometimes register inconsistently.

When the painting is complete, look at the uncovered areas. A small uncovered patch that you simply missed is not a fault; repaint it deliberately and see whether it fills. A patch that stays blank despite repeated, firm touches in exactly that spot is a dead zone, and its size and position are the facts to record: take a screenshot of the painted screen, note the zone's location in plain words such as "upper-left corner, about a centimetre square", and test again after restarting the device. A dead zone that survives a restart is a hardware problem in most cases, while one that disappears after a restart was more likely a temporary software glitch.

Also test taps, not only drags. Some faults affect only quick taps, while drags register normally, and the reverse also occurs. Tap a grid of points across the screen, including the corners, and confirm each tap registers. Then test common gestures: swipe in all four directions, pinch to zoom, and a two-finger scroll. A screen that paints perfectly but stutters on swipes may have a software or performance issue rather than a touch hardware fault, and that distinction guides what you do next.

Worked example: a phone that misses the top-right corner

Suppose a phone owner notices that the send button in a messaging app sometimes needs two taps. She runs the touchscreen test and paints the screen carefully. The whole display fills except a patch in the top-right corner, roughly the size of a fingertip, which stays blank despite repeated touches. She restarts the phone and tests again: the same patch stays blank. She then removes the screen protector and tests a third time: the patch fills normally. The fault was the protector, not the screen — perhaps a bubble or a damaged edge lifting slightly over that corner.

The example shows why testing in stages matters. Had she gone straight to a repair shop, she might have paid for a screen replacement she did not need. Had she stopped after the first test, she would have concluded the screen was faulty. The staged approach — test, restart and retest, remove the protector and retest — isolates the cause with almost no cost, and it produces a clear story to tell a repairer if the fault does persist: "the zone fails with and without the protector, and after a restart", which is far more useful than "the screen sometimes doesn't work".

If the zone fails at every stage, the next step depends on warranty and value. A phone under warranty should go to the manufacturer or seller with the screenshot as evidence. An older phone may justify a repair quote, but compare the quote with the phone's value before committing, because screen replacement on some models approaches the cost of a replacement device. Back up the phone before any repair, since repairs sometimes require a factory reset or involve data risk.

Multi-touch, gestures and false results

Multi-touch testing checks whether the screen tracks several fingers at once, which matters for gaming, pinch zoom and multi-finger gestures. Place two or three fingers on the screen and move them independently; the test should show separate, stable points for each finger. Ghost touches — points that appear without a finger, or a point that jumps wildly — are a fault signal, and they often worsen with heat or while charging. If ghost touches appear only while charging with a particular charger, try a different charger and cable before concluding the screen is faulty, because poor-quality chargers are a known cause of erratic touch behaviour.

False results have several common causes. Wet hands or a wet screen create erratic input. A case pressing on the screen edge can create phantom touches near the border. Gloves, unless designed for touchscreens, block input entirely and look like a dead screen. Accessibility settings that change touch sensitivity, or a recently installed app that draws over other apps, can also interfere. When results look strange, eliminate these variables one at a time — dry hands, no case, no overlay apps — and retest. A test is only as trustworthy as its conditions, and a few minutes of preparation prevents a misleading conclusion.

Also remember that a touchscreen test checks input, not display quality. Dead pixels, discolouration, flicker and brightness problems need different tests, and a screen can pass a touch test while failing a display test, or vice versa. The Dead Pixel Test checks display pixels, and the Multi-Touch Test gives a dedicated multi-touch check with more fingers. For an overall device check, see A2Z Device Health Check Guide.

FAQs

How often should I test my touchscreen? Whenever you notice missed taps, after a drop or water exposure, when buying a used phone, and after fitting a new screen protector. A quick test takes a minute and catches problems while they are still easy to document.

Does pressing harder help a dead zone? No, and it can damage the screen. A genuine touch sensor either registers a normal touch or it does not; extra force does not repair it, and on a cracked screen it can worsen the damage.

Can software fix a dead zone? Occasionally, when the cause is a software glitch, a stuck process, or a miscalibrated setting, a restart or a software update resolves it. A dead zone that survives a restart, a software update and protector removal is almost certainly hardware, and no app can restore a failed sensor region.