Unicode Converter
Convert between characters and Unicode code points, HTML entities, CSS/JS escapes, Python/Java literals, and UTF-8/16/32 byte sequences.
How to Use
-
1
Enter your character or text
Type or paste any character, word, or phrase into the input field. A single code point is also accepted as U+0041, 0x41, A, A, \u0041, \u{1F600} or \U0001F600.
-
2
Read every format at once
Each character gets its own card listing the character, its U+ code point, decimal value, HTML decimal and hex references, CSS, JavaScript, Python and Java escapes, URL encoding, and its UTF-8, UTF-16 and UTF-32 bytes. There is nothing to select.
-
3
Copy the value you need
Click Copy next to any row to put that one value on your clipboard.
About
Unicode conversion bridges the gap between the abstract identity of a character and its concrete binary representation in various computing contexts. The Unicode Standard assigns a unique code point to every character across all of the world's writing systems, symbols, and emoji — 154,998 characters in Unicode 16.0 spanning 168 scripts. Understanding how these code points translate into bytes, escape sequences, and markup forms is fundamental to building software that handles multilingual text correctly.
Different encoding formats serve different purposes. UTF-8 is the dominant encoding for the web and file storage, using 1–4 bytes per code point while remaining backward-compatible with ASCII. UTF-16 is used internally by JavaScript, Java, and Windows, representing most characters in 2 bytes but requiring surrogate pairs for supplementary characters. HTML numeric character references (&#decimal; or &#xhex;) and named entities (&, ©) embed characters safely in markup. CSS escapes (\000041) and JavaScript \uXXXX and \u{XXXXX} sequences are necessary for embedding characters in stylesheets and scripts respectively.
Practical knowledge of Unicode conversion prevents common bugs: mojibake occurs when a byte sequence encoded in one format is decoded as another; incorrect URL encoding causes broken links; truncating UTF-8 strings at byte boundaries rather than code point boundaries corrupts characters. Tools that expose every encoding representation at once allow developers to audit every layer of a character's representation at once, making it easier to trace encoding errors from HTML source through JavaScript runtime to database storage.