Text to binary and binary to text

Convert UTF-8 text to eight-bit binary bytes and back.

Your files are processed here, on your device

We do not send your file or text contents to a processing server. No account is needed and there is no daily operation quota. Individual tools have size limits to protect your device’s memory.

A connection is needed to load the site and its resources. Hosting may receive technical visit data. Favorites store only tool identifiers in this browser.

How we handle your data →

How to use this tool

  1. Choose text-to-binary or binary-to-text conversion.
  2. Paste text or a complete sequence of eight-bit bytes.
  3. Apply, inspect the result and save a copy before switching modes.

An example you can verify

Check the UTF-8 byte representation of a short text.

Example input

Hola

SettingsText → UTF-8 binary.

Expected result

01001000 01101111 01101100 01100001

Decoding these four bytes restores Hola. An accented letter can occupy several bytes; one character does not necessarily equal one group.

Text to binary and binary to text: uses and practical guidance

Text and binary conversion exposes the bytes UTF-8 uses to represent a string. Every group contains exactly eight digits because it represents one byte rather than necessarily one visible character. Basic letters in Hola use one byte each. An accented letter, ideograph or emoji may require several bytes. This distinction explains why texts with equal character counts can occupy different byte counts. The tool does not process complete binary files or interpret file format headers; it converts a text string to its UTF-8 representation and converts valid UTF-8 bytes back to text.

To encode, paste the exact string you want to represent and select text-to-binary mode. Spaces and line endings in the source are data and receive their own bytes. Output separates groups with spaces for readability. Pasting that output into the reverse mode recovers the original string, including its spaces and line endings. No terminating null byte is added. A Unicode byte-order mark that is actually part of the string is retained during decoding rather than silently removed as an invisible header. This makes the conversion suitable for examining text representation without intentionally changing the supplied content.

Decoding accepts only zeros, ones and whitespace separators. Supply separated groups or one continuous bit sequence, provided the total number of bits is divisible by eight. Incomplete bytes, 0b prefixes, commas and other symbols are rejected. The resulting bytes must also form valid UTF-8. For example, 11111111 alone cannot represent a valid UTF-8 character and causes an error. Damaged byte sequences are not silently replaced with substitution symbols, since that would conceal the fact that the supplied string cannot be recovered under the selected encoding. Check whether the source uses another encoding before treating such an error as a problem with the original text.

Binary representation does not encrypt or protect information. The digits may be inconvenient to read, but the same content can be recovered without a password. Do not confuse this operation with Base64, hexadecimal or legacy encodings such as Windows-1252; these are different representations and are not automatically detected. Each operation supports one hundred thousand bytes. Binary output uses considerably more text because each byte requires eight digits and a separator. Try an accented word and an emoji to check Unicode behavior before converting a larger block. Save output before changing modes or clearing the page, and retain the original text whenever exact recovery matters.

Settings and limits

Choose a conversion direction. Text uses UTF-8, with eight binary digits per byte. To decode, use zeros, ones and whitespace; bit count must be divisible by eight and bytes must form valid UTF-8. Maximum 100,000 bytes.

Frequently asked questions

Is this encryption?

No. It is another representation of text that anyone can convert back.