d3vices

24 instruments · MIT · offline

Find the fault
before the call does.

24 hardware instruments that run inside the page — microphone, camera, screen share, keyboard, sensors, network. Nothing is uploaded, nothing is kept, and the source is on the bench for you to read.

Run the mic testAll 24 instruments
Instruments
24
Bytes uploaded
0
Accounts
None
Works offline
Yes

The rack

24 / 24 AVAILABLE

Audio & video

Microphone test

Check that your mic is heard, see a live waveform, watch the input level and record a short clip to play back.

getUserMedia · AudioContext · MediaRecorder

Speaker test

Play a tone through the left and right channel independently, sweep the audible range and check for a blown driver.

AudioContext

Camera test

See your webcam live, read the resolution and frame rate it actually delivers, and switch between cameras.

getUserMedia

Screen share test

Confirm screen sharing works before a call, and see the resolution and frame rate the capture actually produces.

getDisplayMedia

Display

Display & dead pixel test

Full-screen solid colours, gradients and grids to find dead pixels, backlight bleed and colour banding.

Fullscreen API

Screen information

Resolution, device pixel ratio, colour depth, colour gamut, refresh rate, orientation and safe-area insets.

screen · matchMedia · requestAnimationFrame

Input

Keyboard test

Press every key and watch it light up. ANSI, ISO and JIS layouts, with rollover and ghosting detection.

KeyboardEvent

Mouse test

Every button including back and forward, scroll in both axes, double-click timing and a polling-rate estimate.

PointerEvent · WheelEvent

Touchscreen test

Draw with up to ten fingers at once, see pressure and contact size, and find dead zones in the digitiser.

PointerEvent · Touch Events

Gamepad test

Every button and axis of a connected controller, live, with stick drift measurement and rumble.

Gamepad API · Vibration Actuator

MIDI test

See notes, velocity, CC and pitch-bend from any connected MIDI controller on a live piano roll.

Web MIDI

Performance lab

Click speed test (CPS)

How many clicks per second can you land? 1, 5, 10, 30 and 60 second runs with a saved personal best.

PointerEvent · performance.now

Kohi click test

The 10-second Minecraft PvP standard, scored the way the Kohi server did it.

PointerEvent · performance.now

Jitter click test

Measure a jitter-clicking burst, and see the consistency of your interval, not just the peak.

PointerEvent · performance.now

Reaction time test

Wait for green, then click. Five rounds, with your median and best kept on your device.

performance.now

Scroll speed test

How fast can you spin the wheel? Measures lines per second and normalises across wheel modes.

WheelEvent · performance.now

Sensors & radios

Network test

Latency, jitter, download and upload measured against a real endpoint, plus what the browser reports.

fetch · performance.now · NetworkInformation

Battery test

Charge level, charging state and the time remaining the browser estimates, updated live.

Battery Status API

Location test

Latitude, longitude, accuracy, altitude, heading and speed, watched live as the fix improves.

Geolocation

Motion sensor test

Gyroscope, accelerometer and compass, with a live 3D orientation cube.

DeviceOrientationEvent · DeviceMotionEvent

Ambient light test

Read the ambient light sensor in lux, where the browser exposes one.

AmbientLightSensor

Vibration test

Fire single buzzes and patterns through the vibration motor.

Vibration API

Bluetooth test

Scan for nearby Bluetooth LE devices and read their advertised services.

Web Bluetooth

System

System report

Browser, engine, platform, CPU cores, memory, GPU renderer and the Web APIs this browser actually exposes.

navigator · WebGL · StorageManager

Why another device tester?

Because the ones that exist are closed boxes that ask you to grant camera and microphone access on trust. This one is MIT licensed: the code that touches your devices is the code in the repository, and you can read it before you press start.

It is also a real progressive web app. Install it once and every test keeps working with the network unplugged — which matters, because a broken network is one of the things you came here to diagnose.

Three ways to run it

  • In the browser. Nothing to install. Every test that the browser exposes an API for.
  • Installed as an app. Add to your home screen or desktop, then run it offline.
  • On the desktop. Windows, macOS and Linux builds that also read the things a browser is not allowed to see. Get the desktop app.