Skip to content
TypeParser
All tools

Binary ↔ Text

Convert text to/from binary representation.

beats rapidtables.com edge: UTF-8 + custom separator
text
binary
separator
Guide

About Binary ↔ Text

Convert text to UTF-8 binary representation (8 bits per byte) and back. Configurable group separator (none, space, hyphen, custom) for readable output. Handles the full Unicode range — emoji, CJK, Cyrillic — by encoding as UTF-8 first then converting bytes to binary.

Why convert text to binary

  • Educational — understanding how computers represent text
  • Puzzle / cipher — escape rooms, ARGs, capture-the-flag
  • Embedded systems — debugging serial output where bytes appear as bits
  • Curiosity — see what UTF-8 looks like for emoji and CJK

For data-volume use cases (storing or transmitting binary files), Base64 or Hex are dramatically more compact and standard.

What you’ll see

Hi (ASCII): 01001000 01101001 — 16 bits, 2 bytes.

Hi 😀: 01001000 01101001 00100000 11110000 10011111 10011000 10000000 — 56 bits, 7 bytes (emoji is 4 bytes in UTF-8).

漢 (Han): 11100110 10111100 10100010 — 24 bits, 3 bytes.

Common workflows

Demo binary representation. Type a name, watch the binary appear. Educational moment for students.

Decode a binary message. Paste 0s and 1s separated by spaces, get the text. Common in CTF challenges.

Inspect non-ASCII. Type emoji or a non-Latin word, see how UTF-8 represents it. Memorable.

Why this is its own tool

Binary↔text is a one-liner in any language, but having it in a tab is faster than opening a Python REPL. Offered alongside the other escape/encode tools so you can mix techniques (ROT13 → binary → Base64) when building a multi-stage cipher.

Frequently asked questions

Why UTF-8 instead of ASCII?
ASCII covers only 128 codepoints. UTF-8 covers all 1.1 million Unicode codepoints. Modern text needs UTF-8; encoding as pure ASCII loses non-Latin characters.
How is emoji encoded?
Each emoji is 1-4 UTF-8 bytes (most are 4). Each byte becomes 8 binary digits. So 😀 (U+1F600) is the bytes F0 9F 98 80, or 32 binary digits.
What separator should I pick?
Space between bytes for readability ("byte mode"). No separator for compact / machine input. Hyphens or commas for systems that prefer them.
Why is my decode returning gibberish?
Almost always the input length is not a multiple of 8 — pad with leading zeros, or check that the input has not been truncated.
Big-endian or little-endian?
Big-endian (most-significant bit first) is the universal convention for text-binary representation. We do not provide a little-endian toggle because no one uses it for text.
For binary <em>files</em>?
This tool handles textual content. For raw binary files (PNG, ZIP), use Base64 or Hex encoding instead — they are more compact.

Related tools

Last updated: 2025-01-15