A practical used-phone inspection checklist
A structured visual and browser-based inspection, with clear gaps that a phone test cannot verify.
Published 24 October 2026 · English · Our method & limitations
Before starting
Ask the owner’s permission and agree what you can inspect. Check the physical condition, buttons, ports and camera glass in good light. Note any visible damage before running software checks. A successful browser test cannot prove ownership, repair history, water resistance or authenticity.
Work through functions in order
Begin with screen colours, touch coverage and multitouch. Then record and replay a short microphone sample and check speaker output. Inspect front and rear camera previews. Try motion, location, Bluetooth and flashlight only where the browser supports them. Finish with a refresh-rate observation if relevant to your purchase.
For each test, record Working, Issue or a skipped/unsupported outcome honestly. Keep a short note of what happened. Do not turn an untested feature into a pass just to complete the report. Revisit unexpected results once under the same conditions.
Check outside the browser too
With the owner’s permission, inspect charging, physical buttons, calls and mobile data using the appropriate device functions. Review any battery information exposed by the operating system, but do not interpret Phone Test as a battery-health measurement. Confirm account-removal and activation requirements through the manufacturer’s own process before taking ownership. Never ask for another person’s password or sign-in codes.
Compare repeatable symptoms
If an observation fails only in the browser, compare it with the built-in app. For example, compare a camera preview problem with the phone’s camera app, or microphone silence with its recorder. Record disagreements instead of choosing the result that looks more reassuring.
Use the report as a record
Save the report only if you need it and review its contents before sharing. It documents your observations at a particular time; it is not a certificate, valuation, warranty or guarantee against hidden defects. An unresolved issue is a reason to ask further questions before deciding, not something a green checkmark elsewhere cancels out.
Continue learning
How to check a phone screen and touchscreen
Inspect solid colours, touch coverage and simultaneous contacts, then distinguish repeatable symptoms from browser limits.
Read guide →AudioTest a phone microphone and speaker step by step
Record and replay a short sample, check speaker output, and isolate permission or audio-routing issues before suspecting hardware.
Read guide →Camera & connectivityCamera, GPS and Bluetooth checks: understand browser limits
Separate unavailable browser features from phone faults when checking cameras, location, Bluetooth, motion and flashlight.
Read guide →How Phone Test worksHow Phone Test tests work and what results mean
Our browser-based test method, evidence limits, content sourcing and correction process.
Read guide →Found an error? Send a correction with this guide’s title and the behaviour you observed.