How are multi-byte characters handled?

They are split into their bytes per the chosen encoding — an emoji is four bytes in UTF-8 or two 16-bit units in UTF-16. The Byte table shows exactly which bytes belong to which character.

Do I have to tell it whether my input is binary or hex?

No. Bytes → Text detects the base from the digits, group widths and any 0x / 0b / 0o prefix, and shows its confidence. If the guess is wrong, pick the base explicitly.

What does strict ASCII do?

It rejects any character above U+007F when encoding and any byte above 0x7F when decoding, telling you where the offending character is — useful for validating protocol data.

What is the hex dump view?

The classic layout used by hexdump and xxd: an offset column, 16 bytes in hex, and the printable ASCII on the right, for the current bytes in either direction.

What are the bit operations for?

Invert flips every bit (bitwise NOT), reverse bit order mirrors each byte (LSB-first data), and swap byte pairs converts between UTF-16 LE and BE or other 16-bit little/big-endian layouts.

Text to Binary

Encode text as bytes in binary, hex, octal or decimal — using UTF-8, UTF-16 LE/BE, Latin-1 or strict ASCII — or paste bytes in any base and get the text back. The reverse direction detects the base automatically (with a confidence score and manual override) and accepts 0x/0b/0o prefixes, separators or continuous digit strings. Choose the separator, add language prefixes, split bytes into nibbles or group 8 or 16 per line. The Hex dump view shows offsets and an ASCII column, and the Byte table shows every character with its code point and bytes. Bit operations (invert, reverse bit order, swap byte pairs) apply in either direction, and files up to 5 MB can be dropped in directly.

Runs locally in your browser

Large inputs? Open fullscreen for room

Text

0 chars · 1 line

Binary bytes (UTF-8)

Output will appear here…

Output base

Encoding

Separator

Prefix

Group

Split bytes into nibbles (0100 1000)Invert bits (NOT)Reverse bit order per byteSwap byte pairs (16-bit endianness)

UTF-8: ASCII is one byte; accented letters two; CJK three; emoji four. The default for the web, JSON and files.

Number Base Converter

Convert between binary, octal, decimal, hex and any base 2–36, with a bit grid, bitwise ops and IEEE-754.

Unicode Escape / Unescape

Convert text to \uXXXX, \u{…}, \x, U+, &#x…;, Python, Go or CSS escapes and back, and inspect every code point for invisible or look-alike characters.

Base64 Encode / Decode

Encode text, hex or any file to Base64 (and Base32, Base58) and decode back — with data URIs and image preview.

Byte / Data Size Converter

Convert data sizes between SI and binary units side by side, and calculate transfer times.

How to use Text to Binary

1Pick Text → Bytes or Bytes → Text and paste your input, or drop a file to convert its raw bytes.
2Choose the encoding (UTF-8, UTF-16 LE, UTF-16 BE, Latin-1 or strict ASCII) — characters the encoding cannot represent are reported with their position.
3In Text → Bytes, choose binary, hex, octal or decimal output, the separator, an optional 0x / 0b prefix, nibble splitting and 8- or 16-per-line grouping.
4In Bytes → Text, leave the input base on Auto — the detected base and confidence appear in the stats — or select it explicitly if the guess is wrong.
5Switch to Hex dump for offsets plus an ASCII column, or Byte table to see each character with its code point and bytes; use Swap (⌘⇧S) to go back the other way.

About Text to Binary

Text to Binary is part of FizzKit — a collection of focused developer and ad-tech tools. Because everything runs locally, it works offline once loaded and never exposes your data to a remote server.

Frequently asked questions

By default, yes. You can also choose UTF-16 LE or BE, Latin-1 or strict ASCII; the encoding applies when decoding too.

Related tools