We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Look up the mapping between characters and their GBK encodings, with fast two-way search.
GBK extends GB2312, encompassing 21,886 Chinese characters and graphic symbols. You can paste multiple characters for sequential lookup.
Please enter GBK characters to look up.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This page is a two-way lookup for individual characters and GBK byte codes. In character mode, enter Chinese characters or supported symbols to see the character’s internal hexadecimal code, Unicode value, and—where available—Quwei and Guobiao fields. In code mode, submit supported GBK or Quwei values to identify the mapped character. Multiple character or code entries can be looked up together, and duplicate results are removed.
GBK is a legacy multibyte encoding used for Chinese text. A GBK internal code is shown as two hexadecimal bytes, for example B0A1. The lookup relies on the browser’s GBK-compatible decoding support, so a result means that the selected decoder maps that byte pair to a character; it does not establish that a full document or file was encoded correctly.
The internal field is the two-byte hexadecimal pair. Quwei is a decimal area-position code and is available only for entries in the GB2312-range portion shown by the lookup. The Guobiao field is a hexadecimal representation associated with that range; extended GBK characters may have no corresponding Quwei or Guobiao value, so a dash is meaningful rather than a failed result. Unicode is shown as a U+ code point, a different numbering system from GBK bytes.
GBK lookup behavior follows a defined mapping, but legacy encoding implementations can vary in edge cases. WHATWG’s Encoding Standard documents the web-platform GBK decoder and its related mappings. Use the exact encoding expected by the system you are checking before treating a code as interoperable.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Choose Character to Code to search from text, or Code to Character to decode entered code values.
For characters, paste the characters to inspect. For codes, use four hexadecimal digits for an internal code such as B0A1; a four-digit decimal value is treated as a Quwei code. Separate multiple codes with spaces, commas, or semicolons.
Read the internal code and Unicode separately. Check whether Quwei and Guobiao are present; extended entries may not have those fields. Unsupported or invalid items may return no row.
Use cases
See how the tool fits into real work and everyday tasks.
When a log or record gives a GBK byte pair for one Chinese character, enter it in reverse mode to see the browser decoder’s mapped character and compare the returned fields.
Look up a character and compare its GBK internal bytes with its Unicode code point. The separate columns make clear that an encoding byte sequence and a Unicode number answer different questions.
Q&A
Find concise answers to common questions and confusing cases.
No. It looks up characters and code values; it does not upload or transcode files or arbitrary full strings.
Those fields are available only for entries in the applicable GB2312-range area. Some extended GBK characters have an internal code and Unicode value without a Quwei or Guobiao counterpart.
Legacy encoding mappings may vary by implementation, and this lookup uses the browser’s GBK-compatible decoder. Check the intended code page and target system’s decoder when diagnosing old data.
Notes
Review scope, result limitations, and important precautions before use.
A successful character lookup is not a general encoding detector and does not prove that a document, database, or byte stream is valid GBK. Results depend on the browser’s decoder mapping. For production migration, validate the complete data with the specific source and destination encodings, preserve the original bytes, and test the receiving system.
Related
Discover related tools, collections, and available API capabilities.