Use this free mouse button tester online to press each mouse button and see what your browser receives. Check left, middle, right, Back and Forward buttons with live counts, a recent event log and clear browser-limit notes.
Move your physical mouse into the dark test area, then press each button one at a time. This mouse button tester maps the button number exposed by the browser, increments a session count and records the latest event so you can spot a button that never registers or only works intermittently.
Counts stay in this browser tab.
Move here and press every mouse button
On a phone or tablet, connect a physical mouse and use a desktop-style browser for the full button test.
A mouse button tester helps when a click feels inconsistent, a middle button stops working, or a side button behaves differently in a browser and a game. It focuses on observable events, not a hardware guess from color or one click.
Press the main left button several times at a comfortable pace. The tester changes the row to Detected and keeps a count for the current tab. Repeated presses can reveal an event that fails occasionally, but a short browser session is not a switch-lifespan test.
Press the wheel straight down to test the middle button separately from scrolling. A wheel can still scroll while its click mechanism fails, so checking the button row gives a more specific signal than moving the wheel alone.
Right-click inside the dark surface. The page contains the context menu in the test area so you can see the mouse event without leaving the workflow. Test slowly and compare the count with the number of physical presses.
If your mouse has thumb buttons, try Back and Forward after the standard three buttons. Browsers, operating systems, extensions and mouse software can intercept these inputs before a page sees them, so Not tested may describe visibility rather than a confirmed hardware failure.
The result card shows how many button rows have been detected, the latest button name, total presses and the last few events. This makes it easier to compare a normal click with an intermittent click and to repeat the same sequence after changing a setting.
Use a repeatable sequence so the result is easy to interpret. You do not need an account, driver download or special permission to start the local browser test.
Place the pointer over the dark interactive surface. The status changes to show that the test is ready, and the coordinate marker confirms that the page is receiving movement.
Press left, middle and right once, then repeat each two or three times. Watch the matching row, count and latest-button label instead of relying on color alone.
Press Back and Forward if your mouse has them. If the browser does not expose one, read the limitation note and test the same button in another application before drawing a conclusion.
If a button sometimes fails, make a slow set of ten presses and compare the visible count with your physical presses. Keep the browser, operating system and connection unchanged during the comparison.
Use Reset test to clear counts, the event log and the live state. Start again after reconnecting the mouse, changing a driver setting or switching to another browser.
The result is a record of events delivered to this page. It is useful evidence for troubleshooting, but it is deliberately narrower than a hardware certification or a manufacturer diagnostic utility.
You have not produced a visible event for that row in this session. Press the button once and check whether the count changes.
The browser delivered at least one event with the mapped button number. Repeat the action if you are checking an intermittent problem.
A side button or browser gesture may have been handled before the page could receive it. Try another browser or application as a comparison.
The initial HTML shows a clearly marked example state so the page remains understandable before JavaScript receives a real press.
Counts, event names and elapsed times describe this tab. They do not confirm switch wear, debounce quality, physical DPI or behavior inside every game.
A missing row is a reason to investigate, not proof that the mouse is broken. Start with simple checks and compare environments.
Press slowly inside the surface, move the pointer out and back in, then reload the page. If the count still does not change, try another USB port, browser or application.
Back and Forward inputs can be consumed by the browser, operating system, extension or vendor utility. Test them in a text editor or mouse software and treat a page-level miss as a visibility limit.
Avoid pressing while the pointer is outside the surface, check whether another control has focus, and repeat a slower sequence. Remote desktop tools and accessibility software can also change event delivery.
The test surface intentionally suppresses the context menu so the event can be recorded. Move outside the surface if you need the browser menu, then return to continue the test.
A page only reports browser-visible events. Game input layers, drivers, raw-input settings and anti-cheat software can use a different path, so compare the mouse in the application where the problem occurs.
Use the page as a fast, private first check. When a result matters for work or gaming, confirm it in the operating system, the vendor utility and the application that shows the problem.
This page focuses on button events. Use the general Mouse Tester for scrolling, movement, dragging, double-click timing or browser-estimated event frequency.
These answers explain the button map, repeat testing and why a browser may not expose every button.
Move a physical mouse into the interactive test area and press each button. The result card marks the left, middle, right, Back and Forward rows as Detected when the browser receives an event, then keeps a count for the current tab.
Press each button slowly and compare the visible count with your physical presses. Repeat an intermittent button several times, then confirm the result in another browser or application because a web page only sees browser-delivered events.
Yes. Press the wheel straight down inside the test surface. The middle-button row is separate from scrolling, so you can distinguish a wheel that moves from a wheel click that registers.
Back and Forward buttons may be handled by the browser, operating system, extension or mouse software before the page receives them. Test the same button in another application and treat a missing web event as a visibility limitation.
No. Detected means the browser received at least one event. It does not prove switch durability, debounce quality, cable health, wireless stability or identical behavior in a game.
The counters and event list stay in the current browser tab for this session. Reset test or closing the page clears the local state; the normal button test does not need an account, upload or test endpoint.
A touch screen does not provide the same five physical button events. Connect a mouse and use a desktop-style browser, but expect some side buttons or browser gestures to remain unavailable to the page.
Repeat the test in the game, the operating system and any vendor utility. Games may use raw input or remapping layers that do not match the normal browser event path, so the page is a first diagnostic rather than a final hardware verdict.
