All Tools View Categories About Contact Privacy

Convert Keycodes to ASCII

Convert keyCodes to ASCII characters.

Your input is processed locally in the browser.

Enter keyCodes as decimal numbers separated by spaces or commas.

About Convert Keycodes to ASCII

Convert Keycodes to ASCII Decode decimal legacy DOM keyCode-style values into ASCII characters using the same defined US keyboard reference as the reverse tool.

Use it when inspecting historical keyboard-event logs or old JavaScript data that recorded keyCode values instead of modern event properties.

Start with the built-in sample, then replace it with a short test value that makes the rule obvious. Small examples are easier to verify because you can count the characters, positions, or numeric codes by hand before using longer input.

The input is not a physical scan-code stream and it is not a USB HID report. Keycodes describe a legacy browser event convention, so their meaning depends on the reference mapping rather than the physical electrical signal from a keyboard.

Test a few obvious values such as 65 for A and 32 for space before decoding a larger sequence.

Because keyCode is deprecated, use this converter for analysis or migration of old data rather than designing a new application around it. The transformation happens locally in the browser, so there is no upload step or external conversion service.

Features

  • Accepts decimal keyCodes.
  • Uses an explicit US legacy mapping.
  • Supports common printable characters.
  • Rejects unknown values.
  • Preserves order.
  • Runs locally.
  • Includes sample data.
  • Supports copy/download.
  • Separators can be spaces, commas, or lines.
  • Pairs with ASCII-to-Keycodes.

How to Use

  1. Paste legacy keyCodes.
  2. Run the decoder.
  3. Check the mapping scope.
  4. Review any unknown value.
  5. Copy/download.
  6. Migrate new code to modern keyboard APIs.

Examples

65. A.

32. space.

72 73. HI.

49 50 51. 123.

Unknown. An unsupported keyCode is reported.

Benefits

  • Useful for legacy logs.
  • Explicit mapping.
  • Good for migration work.
  • Local.
  • Deterministic.
  • Easy to inspect.
  • Reversible within the defined map.

Frequently Asked Questions

Is keyCode deprecated?
Yes.
Is it a scan code?
No.
Is it USB HID?
No.
Which mapping is used?
Legacy US keyboard-style keyCode values.
Can modifier state be recovered?
No; these numeric values alone do not carry the full modifier state.
What happens to unknown values?
They are rejected.
Can I copy?
Yes.
Can I download?
Yes.
Can I use this for new browser code?
It is better to use modern keyboard event properties.
Does input upload?
No.