What Is a Keyboard Layout Viewer?
This tool shows which character each physical key on your keyboard actually produces, according to your operating system's currently active layout. In browsers that support it, it reads this directly from the Keyboard Layout Map API. In browsers that don't expose that data, it builds the same picture live from real keydown events as you press keys - either way, nothing on this page is guessed or assumed from a generic layout template.
This matters more than it sounds. Physical key position and printed character don't always match - an AZERTY, QWERTZ, or Dvorak layout puts different characters on the same physical keys as a standard US QWERTY board, and even within QWERTY, punctuation keys shift between regional variants.
How to Use the Keyboard Layout Viewer
- Load the page and check the "Layout API Support" readout to see how your browser is detecting keys.
- If supported, the grid fills in automatically with your system's real layout.
- Press any physical key to see it highlight on the grid and confirm the character it produces.
- Use this to double-check unfamiliar layouts, external keyboards, or software layout switches.
How It Works
Where supported, this tool calls navigator.keyboard.getLayoutMap(), a browser API that
returns the character mapped to each physical key code by your operating system's active layout - no typing
required. Where that API isn't available, the grid instead labels each key using the key
property of real keydown events, so pressing a key fills in exactly what your system reports
for it, live.
Understanding Your Results
- Grid matches what you expect for your language layout - your system layout is being read and applied correctly.
- A key shows a character you didn't expect - you may have a regional layout active (AZERTY, QWERTZ, Dvorak, etc.) rather than standard US QWERTY, which is normal and not a fault.
- Layout API shows "Not supported" - this simply means your browser doesn't expose that specific API; the live key-press fallback still gives you accurate results as you type.
Browser Limitations
The Keyboard Layout Map API is currently only implemented in Chromium-based browsers, and even there, it may require a secure (HTTPS) context and can be restricted in some embedded or sandboxed environments. On unsupported browsers, this tool cannot pre-fill the grid without you pressing each key at least once, since there's no other honest way to know what each key produces.
Common Mistakes to Avoid
- Expecting the grid to auto-fill on every browser - only Chromium-based browsers support the underlying API; others need live key presses.
- Assuming a "wrong" character means a hardware fault - mismatched characters usually mean a different regional layout is active, not a broken key.
- Testing with a virtual keyboard software layer active - some remapping tools change what the browser sees; disable them first for an accurate read of your physical keyboard.
If a key isn't registering at all rather than showing the wrong character, check it with the Keyboard Tester instead.
Frequently Asked Questions
Why does my browser show "Not supported"?
The Keyboard Layout Map API is currently limited to Chromium-based browsers like Chrome, Edge, and Opera. Firefox and Safari don't implement it yet, so this tool falls back to reading your layout live from keydown events instead.
Does this detect my keyboard's physical layout, like ANSI vs ISO?
No, it shows which character each key produces based on your operating system's software layout setting, not the physical shape or size of the keyboard itself.
Is this reading anything from my system beyond the layout map?
No. It only reads the character-per-key mapping through the standard API, or from key presses you make yourself - nothing else about your system is accessed.
Why does a key show a symbol I don't recognize?
This usually means a non-US layout is active, such as AZERTY or QWERTZ, where punctuation and symbol keys are arranged differently than standard US QWERTY.
Is any of this data stored or sent anywhere?
No. Everything is read and displayed locally in your browser and is never transmitted or saved.
Conclusion
Whether you're confirming a new keyboard's regional layout or just curious what a specific key actually produces, this viewer gives you a real, live answer instead of a generic assumption. For confirming that every key registers at all, pair this with the Keyboard Tester.