Skip to main content
CaseSwitch

Binary Code Translator

Use the CaseSwitch Binary Code Translator to convert UTF-8 text to 8-bit binary bitstrings (and back). Choose Encode or Decode, paste the value, and copy the result. Processing stays in this browser.

Written by the CaseSwitch editorial team. We maintain these tools in the browser so drafts, keys, and images stay on your device.

Last reviewed: 23 July 2026

Processed locally in your browser. Nothing is sent to a server.

Paste or type text to convert. Output stays empty until there is input.

Character count: 0 · Word count: 0 · Line count: 0

Examples

Encode Hi

Input

Hi

Output

01001000 01101001

Decode Hi

Input

01001000 01101001

Output

Hi

Encode A

Input

A

Output

01000001

Encode OK

Input

OK

Output

01001111 01001011

Decode OK

Input

01001111 01001011

Output

OK

How to use

  1. Choose Encode (text → binary) or Decode (binary → text).
  2. For decode, paste 8-bit groups separated by spaces.
  3. Copy the result and check multi-byte characters if you use non-ASCII text.

What this tool is for

Teaching tools and puzzles still use bitstrings (`01001000` for H). This page walks UTF-8 bytes and prints eight bits per byte — or parses space-separated 8-bit groups back to text. It is not machine-code disassembly.

How it works

Encode UTF-8–encodes the text and prints each byte as an 8-bit string separated by spaces. Decode requires groups of exactly eight `0`/`1` characters separated by spaces, rebuilds bytes, and decodes as UTF-8. Wrong-length groups fail.

When to use it

Computer science homework, explaining ASCII vs UTF-8, decoding a bitstring from an ASCII-based puzzle, and round-tripping a short word.

When not to use it

Not a protocol analyzer. Not ARM/x86 disassembly. Multi-byte UTF-8 characters are longer than one 8-bit group — that is correct, not a bug.

How it compares to related tools

Hex to Text is more compact for the same bytes. Morse Code Translator is a different binary-ish language for radio. UTF-8 Encoder shows decimal/hex bytes.

Common mistakes

Forgetting UTF-8 (é is not one ASCII byte). Leaving bits that are not multiples of 8. Omitting spaces between bytes on decode when the parser expects groups.

ASCII is a UTF-8 subset

English letters in UTF-8 use the same single bytes as classic ASCII, so teaching examples look familiar. Accented letters and emoji need more than one byte — encode a sample like café in the UTF-8 tool if you want to see the longer bit pattern.

Group length matters

Decode insists on eight bits per group. Leading zeros count. If a puzzle omits leading zeros, pad each byte to 8 bits before pasting.

Frequently asked questions

Is this ASCII or UTF-8?+

Bytes are UTF-8. Pure ASCII is a subset, so English letters look like classic 8-bit ASCII.

Can I decode binary with spaces?+

Yes. Grouping by byte with spaces is required for decode.

Why did my decode fail?+

A group was not exactly eight `0`/`1` characters, or separators were missing. Fix grouping and try again.

Does it support 7-bit ASCII dumps?+

Pad to 8 bits per byte. This tool expects full bytes.

Is my text uploaded?+

No. Conversion runs in this browser.

Can I translate machine code?+

No. This maps text bytes to bitstrings, not CPU instructions.

Does this tool send my payload to CaseSwitch?+

No. Formatting, encoding, and naming conversions for this page run in your browser after load — your sample stays on the device.

Related tools