01 Binary, Hex & ASCII Converter

Convert text to and from binary, hexadecimal, octal, and decimal ASCII. Free bidirectional converter with UTF-8 support, padding, separator, and grouping options.

What is Binary, Hex & ASCII Converter?

A free bidirectional text encoder/decoder across binary, octal, hexadecimal, and decimal bases. Type "Hello!" and see "01001000 01100101 01101100 01101100 01101111 00100001" instantly. Paste binary, hex, or decimal codes and decode them back to text. Supports UTF-8 (multi-byte emoji, accented characters) and ASCII-only modes with non-ASCII warnings. Configurable separator (space, comma, newline, none), per-byte zero-padding, and digit-group spacing for human readability. Auto-detects direction (text vs encoded) with manual override. Educational sidebar explains bits, bytes, and UTF-8.

How to Use

  1. Pick a mode tab: Binary (base 2), Octal (base 8), Hex (base 16), Decimal (base 10), or ASCII.
  2. Type text on the left to encode it; or paste binary / hex / etc. on the left to decode (auto-detected).
  3. Adjust encoding (UTF-8 / ASCII), separator, padding, and digit grouping in the settings sidebar.
  4. Watch live updates with stats showing bytes, character counts, and any warnings.
  5. Press Ctrl+K (or click Swap) to flip input ↔ output for chained conversions.

Why convert text to binary in the first place?

Computers store every character as a number, and every number as a sequence of bits (binary digits). The conversion you see in this tool is exactly what happens when your computer saves a text file: each character maps to a code (ASCII or UTF-8), each code is a byte, each byte is 8 bits. Text → binary conversion is useful for: educational (showing students what a character actually "looks like" to a computer), debugging (when a string contains invisible or unexpected characters, the binary reveals every byte), cryptography puzzles and CTF challenges (binary-encoded flags are a common challenge style), steganography (hiding messages bit-by-bit in images), and retro computing / embedded systems (where you might be hand-coding character sequences).

A whirlwind history of character encoding

Computers in the 1960s used a patchwork of incompatible character encodings (EBCDIC, BCD, six-bit codes). ASCII, standardised in 1963 by the American Standards Association, gave the English-speaking world a common 128-character set — letters, digits, punctuation, and control characters. But ASCII only covered English. National extensions (ISO-8859-1 for Western Europe, Shift-JIS for Japanese, GB2312 for Chinese) created a maze of incompatibilities — opening a Russian email in a Greek-locale email client showed gibberish. Unicode, announced in 1991 and developed since, finally unified everything into a single codespace covering ~150K characters from every script. UTF-8, designed by Ken Thompson and Rob Pike in 1993, is the encoding that made Unicode practical: backward-compatible with ASCII (no migration cost for English users), variable-length (1-4 bytes per character), and efficient enough for the web. Today, 98%+ of all text on the web is UTF-8.

Use cases beyond fun and games

  • Steganography — embed binary text into the least-significant bits of image pixels, hiding messages invisibly.
  • Network protocols — when debugging packet contents in Wireshark, you'll see hex bytes; this tool decodes them back to text.
  • Programming education — students new to Computer Science benefit enormously from seeing a string they typed turn into actual bits.
  • Debugging encoding bugs — when a database returns "é" instead of "é", binary view reveals the bytes are Latin-1-interpreted UTF-8.
  • CTF challenges — binary-encoded flags are a common warm-up; this tool decodes them in seconds.
  • Retro / hobbyist hardware — Arduino, Raspberry Pi, and other microcontrollers often display character output bit-by-bit; understanding the conversion is fundamental.

Frequently Asked Questions

What is the difference between ASCII and UTF-8 encoding?

ASCII (American Standard Code for Information Interchange) defines codes 0-127 — basic English letters, digits, and punctuation. Each ASCII character is exactly 1 byte (8 bits). UTF-8 is a backward-compatible superset that covers every character in Unicode (~150K+ characters). ASCII characters take 1 byte in UTF-8, but accented Latin letters (é, ü) take 2 bytes, most CJK characters take 3 bytes, and emoji take 4 bytes. UTF-8 is the standard for modern web and software; ASCII-only is now mostly a legacy / compatibility mode.

Why does my text show 8 binary digits per character?

A byte is 8 bits, and ASCII characters are stored as 1 byte each. So the binary representation of any ASCII character is exactly 8 binary digits (with leading zeros padded if the value is small). "A" is decimal 65, which is binary 01000001 (8 digits, padded). "z" is decimal 122 = 01111010. The padding option in this tool lets you toggle 8-digit padding off (showing minimum-length binary like 1000001 for "A") or on (the default, showing standard 01000001).

Why does my emoji take 4 bytes in UTF-8?

Emoji codepoints live above U+10000 in the Unicode range, which UTF-8 encodes using 4 bytes (4 × 8 = 32 binary digits). For example, 🔥 is U+1F525, which UTF-8 encodes as the byte sequence F0 9F 94 A5 (or in binary: 11110000 10011111 10010100 10100101). When you encode emoji-laced text in this tool, you'll see the byte count grow disproportionately to the character count.

What happens if I paste invalid binary?

The tool warns you in a yellow callout above the output. Common issues: extra characters that aren't 0 or 1, incomplete final byte (e.g., 7 digits instead of 8), or non-ASCII binary in ASCII mode. The decoder tries to be forgiving — strips whitespace and separators, normalises grouping, and recovers from short tokens — but truly broken input produces an empty or partial decode with a warning.

How is octal different from binary or hex?

Octal is base 8, using digits 0-7. Each octal digit represents 3 binary digits, making it a compact human-readable form of binary (used for Unix file permissions: chmod 755 means rwxr-xr-x). Hex is base 16, using digits 0-9 and A-F; each hex digit represents 4 binary digits. Hex is the most common base for raw byte representation in programming. Binary is the underlying form. Decimal (base 10) is the value that humans read as numbers.

Related Tools

  • ··— Morse Code Translator — Translate text to Morse code and back. Free Morse code translator with audio playback (WPM, frequency, volume)
  • 🔐 Caesar Cipher & ROT13 Tool — Caesar cipher encoder/decoder with adjustable shift, ROT13, ROT5, ROT47, Atbash, and brute-force panel showing
  • {} JSON Formatter — Format, validate, and beautify JSON data instantly. Free online JSON formatter with syntax highlighting and er
  • 💘 Secret Crush Detector — Party game: everyone secretly picks a crush with a PIN-protected pick, then reveal mutual matches. 100% privat
  • 🎲 Truth or Dare Generator (Smart Mode) — The smartest Truth or Dare generator online. 200+ prompts across 5 group types (friends/couples/office/family/
  • 📝 Word Counter — Count words, characters, sentences, and paragraphs instantly as you type. Free online word counter with readin
  • 🤖 ChatGPT Humanizer — De-robotize AI text in your browser. 200+ AI-tell swaps, contraction injection, em-dash cleanup, sentence-vari
  • Aa Case Converter — Convert text between UPPERCASE, lowercase, Title Case, camelCase, snake_case, kebab-case, and more.

Related: text to binary, binary to text, ascii to binary converter, binary translator, text to hex, hex to text, ascii to hex, text to octal, text to decimal, binary code translator, utf-8 converter, character encoding tool, free binary converter, string to binary, binary string decoder