Character Encoding

This subcategory gathers 6 tools for moving between readable text and its technical representation. You can turn UTF-8 text into binary bytes, inspect Unicode code points, list character codes, encode Base32, convert an international domain to Punycode or handle quoted-printable. It suits developers, students and anyone checking an encoding.

To choose, look at the notation you need: binary bytes, U+ code points, decimal and hexadecimal values, Base32, Punycode or quoted-printable. Text and binary is for byte sequences. Unicode Code Points and Character codes help inspect a character. Base32 encoder, Punycode and Quoted-printable target specific formats.

How to use

  1. First decide the target notation: binary bytes, U+ code points, decimal and hexadecimal values, Base32, Punycode or quoted-printable. That points to Text and binary, Unicode Code Points, Character codes, Base32 encoder, Punycode or Quoted-printable.
  2. To inspect a single character, start with Unicode Code Points or Character codes, then compare the values before choosing an encoding.
  3. For a full string, use Text and binary to see UTF-8 bytes, then move to Base32 encoder or Quoted-printable if the transport format requires it.
  4. Before copying an international domain, run it through Punycode and recheck the output, because one wrong character can change the resulting address.

Frequently asked questions

Can I use these tools without an account?

Yes, these tools are free and require no sign-up. They run in your browser, so you can test an encoding or check a character quickly. For sensitive data, keep your usual precautions.

What is the difference between code points and character codes?

Unicode Code Points focuses on U+ notation and character conversion. Character codes shows several representations, such as decimal and hexadecimal, for the same text. Both help you understand how a character is stored or transmitted.

Which tool should I use to check an accented character?

Unicode Code Points and Character codes are the most direct: they show the character value and its representations. Text and binary then helps you see the matching UTF-8 bytes. Compare the results to confirm the accent is encoded as expected.

When should I choose Base32 encoder instead of Quoted-printable?

Base32 encoder fits when the expected format is Base32 as defined by RFC 4648. Quoted-printable targets printable text for transport. Check the format your use case requires, then test a short value before handling longer content.

Tools in the same category