Text Encoding Tools — Hex, Punycode, Unicode & More
Hex Encoder
Convert text to hex and hex to text. Essential for embedded programming, serial debugging, and protocol analysis. Free online hex converter.
Punycode Converter
Convert internationalized domain names (IDN) to Punycode and back. Encode Unicode domains for DNS. Essential for multilingual web addresses.
Quoted Printable
Encode and decode Quoted-Printable text for email. Convert special characters to =XX format. Essential for MIME email headers and bodies.
Unicode Escape
Convert text to Unicode escape sequences and back. Supports \uXXXX, \x, HTML entities, and CSS escapes. Essential for developers.
Uuencode
Encode and decode files with UUencoding. Classic Unix binary-to-text encoding for email and Usenet. Includes XXencode variant support.
Text Encoding Formats
Different systems and protocols require text in specific formats. Serial ports use hexadecimal, international domains use Punycode, and programming languages use Unicode escapes. Our tools convert between these formats instantly in your browser.
Hexadecimal Encoding
Hex encoding represents each byte as two characters (0-9, A-F). Essential for embedded programming, serial port debugging, memory dumps, and protocol analysis. Common formats: space-separated (48 65 6C), C array ({0x48, 0x65}), or escape sequences (\x48\x65).
Punycode
Punycode encodes international domain names (IDN) into ASCII. Domain names like münchen.de become xn--mnchen-3ya.de. This allows DNS systems designed for ASCII to handle any Unicode characters.
Unicode Escapes
Programming languages represent Unicode characters as escape sequences. JavaScript uses \u0041 for 'A', Python uses \N{name} notation. Our tools convert between readable Unicode and escape sequences.
Quoted-Printable
Email systems use Quoted-Printable encoding for 8-bit data in 7-bit transport. Special characters become =XX sequences. Headers and body text in non-ASCII languages require this encoding for reliable delivery.
UUencode
UUencode (Unix-to-Unix encoding) was the original method for sending binary files through email. While largely replaced by Base64 MIME encoding, it's still found in legacy systems and Usenet archives.