Convert String to Binary

Yes. The tool iterates the input by Unicode codepoint (not by JavaScript char), so surrogate pairs for high codepoints like emoji stay together. Each codepoint is encoded as UTF-8 – 😀 (U+1F600) becomes the 4-byte sequence F0 9F 98 80, shown in the grid. Most “string to binary” converters treat each JS char as one byte and produce wrong results for emoji and non-BMP characters.

Yes – click Swap. The reverse parser is lenient about input formatting: 01001000 01101001, 01001000,01101001, 0b01001000 0b01101001, and 0100100001101001 all decode to Hi. The total bit count must be a multiple of 8; otherwise you get an error like “Total 13 bits – must be a multiple of 8 (last byte is 5 bits)”.

Caught and reported. The decoder uses strict mode (fatal: true) so byte sequences that aren’t valid UTF-8 – for example a lone continuation byte 10101010 with no lead byte – fail with a specific error rather than silently producing the U+FFFD replacement character. This lets you spot data corruption instead of papering over it.

Per-byte adds a space after every 8 bits – most readable for ASCII text. Continuous removes all whitespace – useful when you need a raw bit stream to paste into another tool. Per-character keeps all bytes of one codepoint together with no internal space, with single spaces between characters – useful when you want to see at-a-glance which characters expand into multi-byte sequences.

Hex is the same bytes in base 16, denser, and easier to compare against UTF-8 reference tables. For ASCII, hex byte 41 = decimal 65 = 01000001 binary = letter A. For emoji 😀, hex F0 9F 98 80 is much faster to read than 32 bits of binary. The Copy report includes both.

200,000 characters. Beyond that the per-character grid would slow down browsers (each row is a DOM node) and the binary output becomes too large to handle smoothly. Hit the cap and you get a clear error “Input too large – cap is 200,000 characters”. The grid itself caps at 256 displayed rows with a “… N more characters” note, but conversion still processes the full input.

The Char column substitutes visible glyphs for invisible whitespace so the row isn’t blank: space → · (middle dot), newline → ↵, tab → →. The actual encoded bytes are still 20, 0A, 09 respectively, shown correctly in the Hex and Binary columns. Useful when you’re auditing what’s actually in your text.

No – this tool emits UTF-8 only. UTF-8 is the dominant encoding on the modern web and the natural choice for text-to-binary conversion. If you specifically need UTF-16 or windows-1252 binary output, you’ll need a more specialized encoder – most use cases (debugging encoding issues, learning computer science, archival storage) want UTF-8.

No. All UTF-8 encoding, binary formatting, per-character analysis, and TSV emission run in your browser using the standard TextEncoder and TextDecoder APIs. Open DevTools → Network and confirm zero requests fire – even when you Convert or Download. Safe for sensitive text, secrets, or anything you’d rather not send to a third-party converter.

Yes. Total bundle is about 18 KB. Load once, disconnect, keep using. The conversion is pure local computation – no fonts to fetch (system font stack), no analytics, no API. Useful for offline development, airgapped environments, or when you don’t trust the network you’re on.