Whatever you send lands directly with the people who build KeyProbe. No bots, no ticket maze, no auto-replies — one short message, one human reading every word of it. Tell us what your keyboard did, or didn't do, and we'll take it from there.
Most messages to KeyProbe start one of three ways: a key on our keyboard tester isn't behaving, something looks wrong in your browser, or you have an idea you can't shake. All three belong here. KeyProbe does one job — press a key, watch it light up, know it works — and when any part of that breaks on your machine, we genuinely want the details.
Maybe the E key registers twice. Your arrow keys highlight in the wrong order. The on-screen layout doesn't match the physical board in front of you, or a worn key on a five-year-old laptop refuses to appear at all. Those specifics are gold: they often expose the exact bug other visitors are hitting silently.
Not sure it counts as a bug? Contact us anyway. Questions about how the tester works, requests for a missing layout, even opinions on the dark, neon-accented design are just as useful as a formal bug report. If it bugs you, it matters to us.
Nearly everything in our inbox fits one of three buckets — pick whichever matches yours.
A key that won't highlight, inputs that register twice, a layout rendering incorrectly, the tester freezing mid-session. Tell us what you pressed, what you expected, and what happened instead — that trio is usually all we need to reproduce it.
Testing on a compact 60% board, a battered laptop, an AZERTY or QWERTZ layout, or a browser we haven't tried? Keyboards and browsers don't always agree, and your edge-case report makes KeyProbe sturdier for everyone who follows.
Want a press counter, sound feedback, or a better fit for your workflow? Suggestions genuinely steer the roadmap. Tell us what would make KeyProbe the first tab you open the moment a key starts acting up.
The fastest route to a fix is describing the scene of the accident. Include your browser, your operating system, your keyboard type, and the exact key or key sequence that failed. 'The E key doesn't register in Firefox on Windows, wireless board' gets action; 'testing is broken' gets questions. A screenshot works too, if that's easier to capture.
One hard rule: never paste passwords, payment details, or any other sensitive keystrokes into a message, even as an example. The tester runs entirely in your browser, so there's no reason we'd ever need that data — the same privacy-first thinking that shapes the tool shapes how we handle every contact message. The privacy policy page spells out exactly what we do and don't collect.
After your note arrives, a human takes over. We split reports into quick fixes and bigger projects, chase the tricky ones on our own machines, and fold strong ideas into future updates. No account, no ticket number, no technical jargon required — plain language from anywhere in the world is perfect.
Fix in progress or not, your keyboard is waiting. Head back to the tester, put every key through its paces, and tell us anything that feels off.
Use the contact form on this page and describe the failing key, your browser, your operating system, and your keyboard type. The more precise your report, the faster we can reproduce and fix the issue — no account or ticket system required.
Yes — layout requests and feature ideas are among our favorite messages to receive. Whether it's a regional layout, a press counter, or sound feedback, tell us what you want to see. Some of our best roadmap items started as one person's message.
No. KeyProbe runs entirely in your browser, so your keystrokes never leave your device. When you contact us, we see only what you deliberately write in your message. The privacy policy page explains exactly how information is handled.
Your browser and operating system, your keyboard type (mechanical, membrane, laptop, wireless), and a step-by-step account of what happened. Name the specific key if one failed. That detail usually turns a vague glitch into a fixed bug in a single exchange.