Mouse Test — Check Every Button.
Press each button on your mouse — left, right, middle, and the two side buttons — and watch it light up on a live diagram. Spin the wheel to confirm both scroll directions, and read every event as it fires. A fast way to prove a button works, or catch one that doesn't.
Press any button or spin the wheel
Online mouse test.
Every press and scroll shows up on the diagram and in the log — nothing is uploaded.
Before you trust the result
- Click firmly and fullyA real fault stays silent even on a firm, deliberate press. A button that only registers sometimes points at a worn switch — confirm it on the double-click test.
- Watch down and up separatelyA healthy button fires one "down" when you press and one "up" when you release. A missing "up", or extra events, is a switch that's bouncing.
- Side buttons may be claimed by the browserBack and forward buttons often trigger browser navigation before this page sees them. If they don't light up, they may still work — they're just being intercepted.
- Right-click is held here on purposeWe suppress the context menu on the diagram so your right-click registers. Elsewhere on the page, right-click behaves normally.
How to use the mouse test
- 1Press each button once. Left, right, then the scroll wheel as a middle click. Each region on the mouse diagram fills with colour while the button is held and clears when you let go.
- 2Try the side buttons. If your mouse has back and forward buttons, press them too. They light up when the browser lets the event through — the log records exactly which button number fired.
- 3Scroll both ways. Roll the wheel up and down; the Scroll readout shows the direction and the middle region flashes. This confirms the encoder works in both directions.
- 4Read the log. Every press, release and scroll appears in the event log with its button number. If a click is missing or doubled, run the double-click test; if the wheel skips, try the scroll test.
How the mouse test works
Your browser turns every physical click into a mousedown event when you press and a mouseup when you release, each tagged with a button number: 0 is left, 1 is the middle/wheel click, 2 is right, and 3 and 4 are the back and forward side buttons. This page listens for those events, lights the matching part of the mouse diagram, and writes a line to the log — so you see exactly what your hardware sent.
Scrolling fires a separate wheel event whose deltaY is negative when you roll up and positive when you roll down. That's how the Scroll readout knows the direction without any driver access.
Two things sit between the switch and this page. Your browser may claim the side buttons for back/forward navigation and the right button for its context menu before the event reaches JavaScript — this page holds the context menu on the diagram so right-clicks register, but it can't always stop side-button navigation. So a button that doesn't light here isn't automatically broken; it may just be intercepted upstream.
When to run a mouse test
Buying used
Check every button and both scroll directions on a second-hand mouse before you pay — a dead middle click or side button is easy to miss otherwise.
A button feels dead
Confirm whether a press registers at all. If the diagram never lights for that button, the switch or its solder joint has likely failed.
After remapping
Set up custom side-button actions in software? Verify the raw button still fires here, separate from whatever macro it now triggers.
New mouse setup
First thing after plugging in: confirm all five buttons and the wheel are recognised by the browser and OS.
Troubleshooting ghost clicks
Watch the log while you hold still. Events appearing on their own point to a failing switch or electrical noise.
Checking a laptop trackpad
Left, right and tap-to-click all surface here, so you can verify a trackpad's buttons the same way as a mouse.
Mouse test glossary
- mousedown / mouseup
- The browser events fired the instant a button is pressed and released. A healthy click produces exactly one of each.
- Button number
- How the browser labels which button fired: 0 left, 1 middle, 2 right, 3 back, 4 forward.
- Middle click
- Pressing the scroll wheel straight down. It opens links in new tabs and closes tabs, and registers as button 1.
- Side buttons
- The extra thumb buttons (back and forward) on many mice. Browsers often use them for navigation, which can hide them from tests.
- Context menu
- The right-click menu. Web pages can suppress it so a right-click can be measured — which this test does on the diagram only.
- Wheel event
- The scroll event, carrying a deltaY value: negative up, positive down. It's separate from any button press.
Frequently asked questions
Why don't my side (back/forward) buttons light up?
Most browsers map the two thumb buttons to page navigation, and act on them before a web page ever sees the event — so pressing "back" may just send you to the previous page instead of registering here. This page tries to hold those events, but browsers don't always allow it. If your side buttons work for navigation, they're physically fine; they're simply being intercepted upstream. Mouse software that remaps them to keystrokes will make them show up as key presses rather than buttons.
Why does right-clicking not open a menu on the mouse diagram?
That's deliberate. To measure a right-click, the page suppresses the context menu inside the diagram area so the button-2 event can register and light up. Everywhere else on the page, right-click works normally. If you want the menu back, just right-click outside the diagram.
A button registers sometimes but not always — is it broken?
That's the classic signature of a worn mechanical switch. Intermittent presses, or one physical click showing up as two events, mean the switch contacts are degrading. Run the double-click test to measure it precisely: gaps under about 80 ms between two clicks you meant as one confirm the switch is chattering.
My scroll wheel click (middle button) doesn't work. What now?
Press the wheel straight down without rolling it — a middle click is button 1 and should light the wheel region and log a "Middle down" event. If nothing registers, the wheel's click switch may have failed even though scrolling still works, since scrolling and clicking use different mechanisms inside the wheel assembly.
Does this test work with a laptop trackpad or a drawing tablet?
Yes for the basics. A trackpad's left and right clicks (and tap-to-click) fire the same mousedown/mouseup events, so they light the diagram. Multi-finger gestures and pen pressure use different APIs and won't all appear here. For touch-surface behaviour, the scroll test covers two-finger scrolling.
Is anything about my mouse or clicks sent to a server?
No. Every event is read and displayed in your browser and never leaves your device. There's no account, no upload, and nothing stored beyond your theme and language preferences.