GBK Encoding Range Quick Reference
Enter a short text, query the actual bytes and single- or double-byte type according to WHATWG Web-compatible GBK, and indicate whether it uses the same byte sequence as this page’s GB2312 mapping.
How to use the GBK encoding range quick reference
GBK bytes are calculated using a local, fixed index in the current browser; no input content is uploaded.
Enter short text
Enter up to 64 Unicode scalar values; whitespace, duplicate characters, and order remain unchanged.
View Web-compatible bytes
View uppercase hexadecimal bytes and single-byte or double-byte types character by character, and whether the WHATWG GBK output is exactly the same as the byte sequence mapped by this page’s GB2312.
Linked range description
Single-character lookup locates the relevant range; results can be copied as TSV, and unmappable characters are explicitly displayed as “unsupported”.
Limitations and Notes
- The lookup uses the GBK encoding algorithm of WHATWG Encoding; it is not equivalent to all Windows CP936, operating-system code pages, or vendor-specific extensions.
- The euro sign is encoded as the single byte 80 according to Web compatibility rules; WHATWG explicitly excluded U+E5E5 is displayed as “unsupported”.
- “Identical byte sequence” compares only the output of WHATWG GBK for an individual character with the mapping of this page’s GB2312; it does not mean that arbitrary GBK byte streams can be decoded by GB2312.
FAQ
Why is the euro symbol displayed as 80?
This is a special single-byte mapping defined by WHATWG for GBK Web-compatible encoding, not a strict GB2312 mapping.
Why are emojis unsupported in GBK?
Web-compatible GBK mainly covers ASCII and existing double-byte indexes; it cannot represent all Unicode scalars.
How is the identical byte sequence indication calculated?
The tool separately calculates WHATWG GBK and this page’s ICU/IBM 5478 round-trip GB2312 mappings; it is marked as “Yes” only when both can encode the character and their byte sequences are exactly identical.