Encoding List

Enter a short text to compare the encoding results for Unicode, UTF-8, UTF-16, and ASCII, GB2312, GBK, GB18030, and Big5 character by character, while retaining the encoding purpose quick reference.

Local browser processing
This page has passed the public directory check; full functionality is available after enabling JavaScript.
User Guide

How to use the encoding list

The input text is processed only in the current browser using a locally fixed code table; it is not uploaded or saved.

  1. Enter short text

    Enter or paste up to 64 Unicode scalar values; whitespace, duplicate characters, and the original order are all preserved.

  2. Compare character by character

    View each character’s Unicode, UTF-8, UTF-16, and bytes in each legacy encoding; hexadecimal values use uppercase consistently and are separated by spaces.

  3. Copy or clear

    The current results can be copied as TSV for easy pasting into a table; the Clear button also removes the lookup results.

Limitations and Notes

  • The GB2312 column strictly uses GB2312-1980 character-set mapping; the GBK, GB18030, and Big5 columns use the Web-compatible algorithm of WHATWG Encoding. These standards are not interchangeable.
  • Big5 The lookup includes common HKSCS extensions in the WHATWG index; GB18030 uses fixed indexes and range tables, but this tool is not a file-encoding compliance checker.
  • Unmappable characters are explicitly shown as “unsupported” rather than being replaced with question marks or replacement characters to fabricate a successful result; the lookup results also cannot be used to infer the original encoding of an unknown file.

FAQ

Why are the bytes for the same character different in different encoding columns?

Each encoding uses its own character set and allocation rules; identical or different bytes do not mean that the encodings are equivalent.

Why do Emoji have results in only some columns?

Unicode, UTF-8, UTF-16, and GB18030 cover a larger range of characters; ASCII, strict GB2312, Web-compatible GBK, and Big5 do not cover all emojis.

Is the lookup content sent to the server?

No. The mapping data and calculation logic are loaded locally with the page, and both input and results remain in the current browser.

Page feedbackFound an issue or have suggestions for improvement?
Feedback features need to be used in the online version

Please enable JavaScript in the online version before submitting; local features of the current tool or example are not affected.

Go to the online version for feedback