Reconstruct readable text from a list of numeric character codes. Accepts codes separated by spaces, commas, semicolons, or newlines, making it easy to paste exports from spreadsheets or log files.
Decoding rules
Each token must parse as a finite integer. Valid values are converted with String.fromCodePoint semantics so supplementary-plane characters (above U+FFFF) can be rebuilt when a single large code point is supplied. Tokens that are empty or non-numeric trigger a localized validation error instead of silently producing corrupted output.
When to use it
Reverse engineer numeric dumps, recover messages from legacy mainframe exports, verify round-trips after encoding with the companion text-to-codes tool, or demonstrate that text is just numbered symbols.
Limitations
If your source encoded UTF-16 surrogate pairs as two separate decimal values, you must supply them in the correct order ā the decoder does not merge arbitrary pairs automatically. Out-of-range or negative code points are rejected. Combining characters are not normalized; you receive the exact sequence implied by the numbers.
Example
For example, enter the default sample values on the form and compare the output with a known reference; adjust one input at a time to see how the result changes.