CODDY Tool

Text Converter

Convert text to and from binary, hexadecimal, Morse code and Unicode escapes.

Translate text into other representations and back again. Binary, hexadecimal and decimal byte values, Morse code, JavaScript Unicode escapes and HTML entities — all round-tripping correctly, including emoji and non-Latin scripts.

Everything you enter stays in this browser tab. Nothing is sent to our servers, logged or stored.

Loading tool…

What Text Converter supports

Number bases

  • Text ↔ Binary
  • Text ↔ Hexadecimal
  • Text ↔ Decimal

Codes

  • Text ↔ Morse code
  • Text ↔ Unicode escapes
  • Text ↔ HTML entities

About Text Converter

Text is stored as bytes, and there are several conventional ways to write those bytes down. Binary and hexadecimal appear constantly in programming, debugging and puzzles. Morse code still has a following in amateur radio and in games. Unicode escapes are how you embed an awkward character in source code, and HTML entities are how you write one safely into markup.

Every conversion here goes through UTF-8 bytes, which is what makes emoji and non-Latin scripts round-trip correctly. Implementations built on charCodeAt appear to work on English text and quietly corrupt everything else — a bug you will not notice until someone pastes an accented name.

When decoding fails, you get the specific token that broke and an explanation of the expected format, rather than a blank result.

How to convert text

  1. Choose a conversion

    Binary, hexadecimal, decimal, Morse, Unicode escapes or HTML entities.

  2. Pick a direction

    Encode from plain text, or decode back to it.

  3. Enter your input

    Type or paste. The result appears immediately.

  4. Copy the result

    Copy to the clipboard or download it as a text file.

What each representation is for

  • Binary — one 8-bit group per byte. Teaching, puzzles and low-level debugging.
  • Hexadecimal — two characters per byte. The standard way to display bytes in programming.
  • Decimal — the byte values as ordinary numbers, occasionally required by older systems.
  • Morse code — dots and dashes, letters separated by spaces and words by a slash.
  • Unicode escapes — \u0041 sequences, for embedding awkward characters in source code.
  • HTML entities — & and friends, for writing characters safely into markup.

Frequently asked questions

Does this handle emoji and non-English text?

Yes. Text is converted to UTF-8 bytes before encoding and decoded back the same way, so emoji, accented characters and non-Latin scripts survive a round trip exactly. Tools built on charCodeAt fail on precisely this input.

Why is one character several bytes in binary?

UTF-8 uses one byte for ASCII characters and two to four for everything else. An accented letter is typically two bytes and an emoji four, so each produces that many groups of eight bits.

What format should binary input be in?

Groups of eight ones and zeros separated by spaces, which is what the encoder produces. Commas are also accepted as separators. If a group is not a valid byte, the specific token is reported rather than failing silently.

How is Morse code formatted?

Letters are separated by a single space and words by a slash, which is the common written convention. Morse has no case, so decoded output is lowercase, and it covers letters, digits and common punctuation.

Is any of this encryption?

No. These are all reversible representations with no key and no secret — anyone can convert them straight back. Never use them to protect anything.

All Text Tools

Text Converter is free to use with no account, no watermark and no usage limits. Last updated 14 August 2026.