Binary encoder.

Binary is the alphabet of two digits, 0 and 1, the bits a computer stores. Written out, a byte is eight digits: the letter A, 65, is 01000001. There is nothing to decode but the grouping, and nothing shorter: a binary string is eight times the size of the bytes it shows.

Every byte is written as its eight bits, most significant first, usually with a space between bytes so the groups can be read. The output is 700% larger than the input, eight digits for every byte. The decoder takes the digits with or without spaces, as long as there are eight per byte.

Learning how computers store text and numbers, reading a bit field or a flag byte, checking a protocol's bit layout, digital electronics homework, and showing a child what a letter looks like to a machine.

Technically, since it is only digits; practically no one sends a URL eight times longer than it needs to be.

It is the least efficient encoding by far and the only one that shows every bit. Use it to see or teach; use hex to read bytes at a glance and Base64 to carry them.

No. Binary is an encoding, not encryption: it changes how bytes are written, not who can read them, and anyone can decode it with no key. Encrypt first (AES, age, a library's sealed box) when the content needs protecting, then encode the ciphertext if it has to travel as text.

Type or paste into the input and the Binary appears as you type: "A" becomes 01000001. Text is encoded as UTF-8 bytes, so accents and emoji come out the same as in every language's standard library. Copy the result, download it as a text file, or press Swap to decode it back.

Drop a file onto the input or choose one with the button, and its bytes are encoded directly, not as text. Any file the browser can hold in memory works; a few hundred megabytes is fine, and the result is eight times the size.

A space between bytes shows where each one starts and is how a textbook writes it. Without spaces the output is one run of digits, which some tools expect. The decoder reads both, counting eight digits per byte.

Nothing leaves your browser. The text or file is read into memory on your machine and the encoding is computed there, in plain JavaScript; the page makes no request with it. Load the page, go offline and it keeps working.

No. The Binary encoder is free and opens without a sign-in, an account or an install.

Nothing. The Binary encoder holds your input in the page's memory, so closing or reloading the tab clears it, and it saves nothing in this browser.

The bar has one choice: Spacing, a space between bytes or one run of digits.

Binary output is 8 characters per byte, 9 with the spaces between bytes, and the status line under the result shows the bytes in, the characters out and the percentage.

The text is encoded as UTF-8 bytes first, so accented letters, other scripts and emoji round-trip through the decoder unchanged. Each of those characters takes more than one byte, which makes the output longer than the character count suggests.

Press Swap once there is a result and the same tool becomes the Binary decoder, with the output moved into the input. The decoder shows the original text again.

Closest to the Binary encoder: Binary decoder, File to Binary, Binary to file, Hex encoder. Each opens on its own page, free and in the browser.

The Binary encoder is one of 32 in its group. The group's page, /tools/encoding, lists them all.

The tool is free. Its interface is built from shadcn.io's own components (Button, Input, Slider and the rest of the registry under /ui), which come in React, Vue, Svelte and Solid. Pro adds the blocks and templates for the product around it.