Browser keyboard check

Test your keyboard, one browser event at a time.

Press common keys and combinations to see what this browser receives. The test stays local, starts only when you focus the test area, and does not build a history of the text you type.

Runs in your browserNo keystroke uploadNo account needed

Keyboard test workspace

StatusReady — click or Tab to the test area when you want to begin.Keys are observed only while the test area has focus.
Tested0 / 0
Held now0
Max together0
Click or Tab here, then press keysTab always remains available so you can leave the tester.
Browser-observed input only

Some Fn, media, browser, accessibility, and operating-system shortcuts may be intercepted or transformed before a web page receives them.

Current browser event

Event
—
Key
—
Code
—
Location
—
Repeat
—
Modifiers
—

Recent key events

Latest 20

    History keeps physical code/state facts only. Printable key values are shown only for the current event and are not retained as a typed-text transcript.

    How to use it

    A quick keyboard check in three steps.

    1. 01

      Focus the test area

      Click the keyboard area or reach it with Tab. BeanNest does not listen for keys elsewhere on the page.

    2. 02

      Press keys and combinations

      Held keys turn orange; observed keys remain marked. Try Shift, Ctrl, Alt, arrows, function keys, and the numpad you actually use.

    3. 03

      Read the browser facts

      Compare key, physical code, location, repeat, and modifiers. Reset whenever you want a clean pass.

    What the result means

    key and code answer different questions.

    key is the value the browser interprets after layout and modifiers.code identifies a physical keyboard position such as KeyA or ShiftLeft. They can differ when you change keyboard layouts, use Shift, or type through an input method.

    What “tested” and “max together” can tell you

    A tested key is one whose browser event reached this focused page. Max together is the largest held-key set the page observed during this session. It is useful troubleshooting evidence, but it is not a certification of NKRO, anti-ghosting, switch health, firmware, or electrical behavior.

    Your keystrokes stay in this tab

    BeanNest does not upload key values, key codes, modifier combinations, or the event history. The recent list intentionally omits printable key values and disappears when the page is reset or closed.

    Why does a key not appear?

    First click the test area again, then try the key by itself. The browser, operating system, keyboard firmware, accessibility software, or an Fn layer can intercept or transform some keys before a page receives them. Testing in another browser or a plain text editor helps narrow the problem.

    Why do left and right modifiers sometimes differ?

    Browsers can report a location for left, right, or numpad variants. BeanNest shows that browser-reported location when it is available instead of guessing from the printed key label.

    Does this prove my keyboard has no ghosting?

    No. The page can show only the simultaneous events that reached the browser. Missing or present events are useful clues, but they do not certify the keyboard's hardware rollover specification.

    Does BeanNest record what I type?

    No server or analytics event receives your key data. Only the current key value is shown; the bounded recent list keeps non-text code/state facts so it cannot reconstruct normal typing.

    Keep checking

    More device checks

    Mouse Test

    Check mouse buttons, wheel input, browser double-click events, movement, and hold continuity locally.

    Open tool →

    Sound Test

    Test left and right speaker output, microphone input level, and a short local recording without uploading audio.

    Open tool →