ByteNows. DIGISCOPE
中文 / EN Browse briefs

TOOLBOX

Device checks, compare and build calculators

Six free checks for new screens, keyboards, mice and PC builds — every test runs locally in your browser, nothing is uploaded.

free · no sign-up · no uploads

Suggested order for a new device

  1. Screendead pixels
  2. Displayrefresh rate
  3. Inputkeyboard · mouse
  4. Audiomicrophone
  5. BuildPSU wattage
Device CompareTwo phones or laptops, every spec side by side with launch prices. Spec-by-spec diff Dead Pixel TestEight solid colors fill the screen in turn. Scan the surface: a dot that stays lit or dark where it shouldn't is a defective pixel. 8 fullscreen colors Refresh Rate TestStart the test to sample frame intervals for about 4 seconds and estimate your display's refresh rate; the moving blocks below make high-vs-low refresh differences visible. Measured Hz + motion blocks Keyboard TesterClick the test area, then press keys one by one — pressed keys stay highlighted while the panel shows the key code and running count. 104/87 keys · Mac/Win Mouse Button TestClick each button in the test area; the panel shows per-button counts and the last interval, with sub-80ms chatter flagged in red. Chatter check · wheel count Microphone TestGrant access and speak — the meter and waveform should move. Record 10 seconds to hear playback. All audio stays in your browser. Level meter · local playback PSU CalculatorPick CPU, GPU and the rest of your build — the tool sums each part's draw and recommends a PSU tier with 1.35× headroom. 270+ models with TDP

Frequently asked questions

What order should I check a new device in?

Outside-in works best: dead pixels → refresh rate → keyboard and mouse buttons → microphone; for PC builds add the PSU estimate. Every tool runs in the browser — nothing to install.

Do these tools upload any data?

No. Every check runs locally in your browser: no uploads, no accounts, no logs — closing the page erases everything.

Can I use these tools on a phone?

Yes. Dead-pixel and refresh-rate tests work on phones and tablets; iPhone Safari lacks the Fullscreen API, so the tools fall back to a maximized window with identical logic. Keyboard/mouse tests target desktop devices.

I found a problem — what's next?

Photograph or screen-record it with the location marked, and use the return window first. Each tool page explains how to tell normal variance from a real hardware fault.