Used laptop checklist

Buy Used Laptop Checkup

Use this guided used laptop test before buying to record keyboard, screen, webcam, microphone, speaker, trackpad, WiFi, ports, battery clues and seller-risk checks. Browser checks are approximate and cannot verify exact serial number, SSD health, battery cycle count, activation locks or hidden repair history.

Step 1 of 12

Before you buy

Introduction / honesty checklist

Saved locally in this browser.

Summary Report

Export Laptop Diagnostic Report

Create a laptop diagnostic report or computer diagnostic report online with your checklist results, notes and browser-exposed device information.

About the used laptop checkup

The used laptop checkup is a guided, twelve-step inspection to run before you hand over money for a second-hand machine. It walks you through the checks that catch the expensive surprises — keyboard, screen, webcam, microphone, speakers, trackpad, WiFi, ports, battery clues and seller-risk questions — and records a pass, fail or not-sure verdict plus your notes at every step.

Everything you enter is saved locally in your browser, so you can pause mid-inspection and pick up where you left off, and at the end the tool builds a summary report you can export as TXT, CSV or PDF. That written record is genuinely useful leverage: a documented dead pixel or a failing speaker is a negotiating point, and a seller’s reaction to a methodical inspection tells you something too.

Be clear about the limits. A browser cannot read SSD health, battery cycle counts, activation locks or hidden repair history — so the checklist also prompts the questions to ask and the manual checks to make, from verifying the serial number against the chassis to confirming the seller can log out of their accounts in front of you.

What it looks like in use

Used laptop checkup screen step marked Not Sure with a note about a stuck pixel
One of the twelve steps in the used laptop checkup. Each step explains what to test, links to the right tool, and records pass, fail or not sure with your notes.

Reading your checkup summary

The summary grid shows your pass, fail and not-sure counts across all twelve steps, with a recommendation based on what you recorded. Export the report before you leave the seller.

Good

Every step passes: all keys register, no dead pixels, camera and audio work, WiFi holds a connection, ports function, and the seller answers ownership questions without hesitation.

Average

Mostly passes with a few "not sure" entries or cosmetic issues. Use the notes to price the doubt in — a worn battery or a single stiff key is a discount, not necessarily a dealbreaker.

Poor

One or more hard failures — dead keyboard rows, screen faults, a mic or camera that never works — or a seller who resists basic verification. Walk away or renegotiate substantially; the export report documents exactly why.

What this test checks

  • Guided hardware steps covering keyboard, screen, camera, microphone, speakers, trackpad, WiFi and ports.
  • Seller-risk prompts: ownership proof, serial number match, account sign-out and repair history questions.
  • Battery and performance clues that browser checks can reasonably surface.
  • A locally saved record of every verdict and note, exportable as TXT, CSV or PDF.

How to understand your results

  • A clean pass across all steps means the visible, testable hardware works today — the strongest signal a quick inspection can give.
  • Fails are information, not necessarily dealbreakers: price each one, and treat multiple related fails (keyboard plus trackpad plus ports) as a sign of deeper damage such as a spill.
  • Not-sure verdicts deserve a second look before purchase — they are where post-purchase regrets usually hide.
  • The seller-risk steps matter as much as the hardware ones. A perfect laptop with an activation lock or missing proof of ownership is not a bargain.

Common problems and fixes

No time for a full check

Prioritise screen, keyboard, ports and the seller-risk questions — they cover the costliest faults. The full checkup takes about fifteen minutes.

Seller refuses testing

Treat reluctance to allow a fifteen-minute inspection as a strong warning sign, whatever the stated reason.

Cannot verify battery health

Browsers cannot read cycle counts. Ask for a screenshot of the OS battery report, and note the charge percentage at the start and end of your inspection.

Progress lost between visits

Results save in the browser you used. Use the same browser and device, and export the report before clearing browsing data.

FAQ

Can this check the exact laptop model or serial number?

No. Browser APIs usually cannot read exact model, serial number, SSD health or battery cycle count. Check the serial or service tag manually and use manufacturer tools where possible.

Is this enough before buying a used laptop?

It is a strong practical checklist, but it does not replace professional inspection, proof-of-ownership checks, activation-lock checks or hardware diagnostics.

Is my checkup data uploaded anywhere?

No. Verdicts and notes are stored locally in your browser and only leave it if you export or share the report yourself.

What should I ask the seller before viewing?

Ask for the exact model number, proof of purchase, battery condition, repair history and whether the machine is signed out of all accounts. Evasive answers before the meeting save you a wasted trip.

How do I check for activation locks?

Have the seller sign out of iCloud, Microsoft or Google accounts in front of you, then restart the machine to the login or setup screen. A locked machine is unusable regardless of how well the hardware tests.

What is a fair discount for a fault I find?

Price the repair, not the inconvenience: look up the part and typical labour for your area, then subtract it — a screen with dead pixels or a worn battery each commonly justify a meaningful reduction.

Browser-based test disclaimer

TestMyPC results are browser-based and may vary depending on your device, browser, operating system, permissions, drivers, connection, power settings and connected accessories. Use these tools as practical first checks, then confirm important faults with operating-system diagnostics, manufacturer tools or a qualified technician where needed.