Free embeddable keyboard tester widget

What your readers get

The widget is a compact version of our full online keyboard tester, the same engine, trimmed to three layouts: a tenkeyless ANSI board by default, a 60 percent layout for tight columns, and a Mac compact board for visitors on Apple keyboards. It listens to raw physical key codes, so it tells left Shift from right Shift, works with any language layout, and is not fooled by remapping software. Every detected key stays green, and progress is remembered even if the visitor switches layouts mid-test, which is exactly where most free testers fall over.

It also does the two things a basic key-highlighter cannot. First, chatter detection: if one physical press registers twice within 45 milliseconds, the key is flagged red, a strong sign of worn or dirty switch contacts rather than a fast finger. Second, a live rollover counter: visitors hold down as many keys as they can and see how many register at once, a quick check for 6-key versus n-key rollover. For deeper diagnostics you can link readers to our dedicated ghosting and NKRO test, chatter test and latency test.

Who this widget is for

• Tech bloggers and reviewers. Writing about a keyboard, a switch, or a fix guide? Let readers verify their own board inline instead of bouncing to another site. Pairs well with links to our switch library and keyboard size guide.
• IT help desks and MSP knowledge bases. "Is the keyboard broken or is it the software?" is a ticket you close every week. Embed the tester in your KB article and the user answers that question themselves before the ticket is even opened.
• Repair shops and refurbishers. Put it on your intake page so customers can confirm dead keys before booking, or run it on the bench as a fast pre- and post-repair check.
• Schools and computer labs. A no-install way for students or lab admins to sweep a room of machines for failed keys at the start of term.

Terms of use, short version

The widget is free for any site, personal or commercial, with unlimited traffic. In return, the small attribution bar inside the widget, "Keyboard tester by keyboardsimulators.com", must remain visible and unmodified. Do not crop it out with CSS, cover it with overlays, or strip the link. That credit is how the project stays free, so please leave it alone. You may resize the iframe, place it anywhere on your page, and embed it on as many pages as you like. We serve the widget from our own infrastructure and keep the URL stable, so updates and fixes reach your page automatically with zero maintenance on your side.

Privacy

Everything runs in the visitor's browser. Key presses are never transmitted anywhere. In browsers that allow storage inside an embedded frame, test progress lives in localStorage on the visitor's own machine so they can resume a half-finished sweep. Safari blocks storage for third-party frames, so its visitors start fresh each time. There are no accounts, no cookies required for the tester to function, and no third-party trackers inside the frame.

Tips for a clean embed

Keep the width at 100 percent of your content column and the height at 720 pixels; that fits the tenkeyless layout plus the toolbar and status notes comfortably. A column narrower than about 900 pixels will scroll the board sideways inside the frame, which is deliberate: shrinking it further would put 1u caps below a usable tap size. The widget ships in our dark theme, which sits well on both dark and light pages thanks to the rounded border in the snippet. The loading="lazy" attribute means the frame only loads when a reader scrolls near it, so it costs nothing on page load. Keep allow="fullscreen" as well: full capture mode runs fullscreen so it can grab system keys like Esc and Alt+Tab, and a frame without that permission is not allowed to go fullscreen. Drop the attribute and the widget hides the full capture button rather than shipping one that does nothing when clicked. And remind readers to click inside the widget once before typing, since browsers only deliver key events to a focused frame.

Frequently asked questions