Excel can convert individual numbers to binary with the BASE function, but it has no built-in formula for turning a string of text — with letters, accents, symbols, or emoji — into a byte-by-byte binary representation. That gap is what sends most people searching, because BASE works on a single decimal value at a time and outputs a fixed-length string of digits, not the variable UTF-8 byte stream that a real text-to-binary conversion produces. Even the closely related OCT2BIN and HEX2BIN functions are limited to a single numeric input per cell and break the moment you paste in "café", "€", or "😀". A correct workflow treats each character as one to four UTF-8 bytes and prints every byte as eight zero-padded bits separated by a single ordinary space. The result is unambiguous, round-trippable, and works for plain ASCII, accented Latin text, CJK characters, and four-byte emoji alike. The Text to Binary Converter applies exactly that approach in the current tab: it encodes your Unicode input locally with a standards-based TextEncoder, prints each byte as eight bits, and never sends the string to a server.
Why Excel's Built-In Binary Functions Stop at Numbers
Excel ships three conversion functions that look related but are designed for single numbers, not text:
- BASE(number, radix, [min_length]) — turns one decimal integer into a binary, octal, or hexadecimal string of a length you choose.
- DEC2BIN(number, [places]) — the legacy shortcut that only handles decimal-to-binary for numbers up to 511 (2^9 minus 1) in modern Excel and 1023 (2^10 minus 1) in older builds.
- OCT2BIN and HEX2BIN — same pattern, different source base.
Every one of these formulas expects a single scalar value and rejects text. If you drag BASE down a column beside a list of words, every cell either errors out or returns nothing useful, because Excel has no built-in way to read "café" as a sequence of characters, convert each character to UTF-8 bytes, and then write those bytes as eight-bit binary groups. Some workarounds combine BASE with MID, CODE, UNICODE, and array formulas, but they only succeed for ASCII letters — they lose the moment accented characters, multi-byte symbols, or four-byte emoji enter the cell. That fragility is exactly what a dedicated UTF-8 text-to-binary tool is built to avoid.
What the Text to Binary Converter Actually Does
The Text to Binary Converter is a two-mode browser tool focused on the strict UTF-8 byte representation of a Unicode string. In Text to UTF-8 binary mode it accepts any Unicode string up to 20,000 UTF-16 code units, encodes the string with the browser's WHATWG TextEncoder, and prints every byte as exactly eight zero-padded bits joined by a single ASCII space. In UTF-8 binary to text mode it accepts the strict input format described by the regular expression [01]{8}( [01]{8})* and decodes the byte stream back into the original text using a fatal TextDecoder — meaning malformed sequences raise an error instead of being silently replaced by the Unicode replacement character U+FFFD.
Because the encoding is per byte rather than per character, the tool naturally handles every Unicode width correctly: ASCII letters such as "A" become one byte, accented Latin letters such as "é" become two bytes, the euro sign "€" becomes three bytes, and a supplementary emoji such as "😀" becomes four bytes. Nothing is padded, trimmed, or guessed. Input and output stay in the current tab and are not sent to a server, which matters when the strings you are converting are passwords, API tokens, or anything else you would rather not upload.
How to Convert Text to Binary Step by Step
The conversion itself takes three actions. Open the Text to Binary Converter and follow these steps:
- Choose Text to UTF-8 binary if you are starting from a human-readable string, or UTF-8 binary to text if you are starting from a stream of eight-bit groups you want to decode back into Unicode.
- Enter the text or paste your eight-bit byte groups. In the encode direction, paste any Unicode string. In the decode direction, paste groups of exactly eight binary digits separated by one ordinary space, with no prefixes, tabs, commas, leading or trailing whitespace, or seven- or nine-bit groups.
- Select Convert and verify the byte count or the decoded text before copying the result. The byte count is the fastest way to confirm that the output uses the correct UTF-8 width for each character.
For a concrete worked example, consider the two-character string Hi:
- Step 1 — characters to UTF-8 bytes: 'H' = U+0048 → 0x48, 'i' = U+0069 → 0x69.
- Step 2 — bytes to eight-bit binary: 0x48 → 01001000, 0x69 → 01101001.
- Step 3 — join with single spaces: 01001000 01101001.
The result is two bytes, sixteen bits total, round-trippable in either direction. If you paste "01001000 01101001" back into the converter's decode mode, you get "Hi" again, exactly.
UTF-8 Byte Widths at a Glance
The first thing most Excel users notice when they try to encode real words is that one character does not always equal one byte. The table below summarizes the official UTF-8 widths defined by the Unicode Standard and implemented by the WHATWG Encoding Standard used in browsers:
| Character type | Example | UTF-8 bytes | Binary width |
|---|---|---|---|
| ASCII letter or digit | A, b, 7 | 1 | 8 bits |
| Accented Latin letter | é, ñ, ü | 2 | 16 bits |
| Currency and common symbol | € (U+20AC) | 3 | 24 bits |
| Supplementary plane emoji | 😀 (U+1F600) | 4 | 32 bits |
| CJK character | 中, ひ, 한 | 3 | 24 bits |
| Line-feed control byte | \n (U+000A) | 1 | 8 bits |
Excel's BASE function has no notion of this hierarchy, which is why a four-byte emoji always surprises users who assumed everything was one byte. The Text to Binary Converter encodes each character according to its real UTF-8 width, so the byte count you see in the output is the true encoded length. For mixed input — a word plus an emoji plus a CJK character plus a line break — the output simply grows to match the underlying encoding.
Decoding Binary Back to Text in the Same Tool
The reverse operation is just as important as the forward one, especially in a workbook context where you might receive a binary dump and need to confirm what it actually says. Switching the converter to UTF-8 binary to text mode and pasting a strict byte stream decodes it back into Unicode using a fatal decoder. "Fatal" here is the technical term for refusing to substitute the replacement character U+FFFD when bytes are malformed, incomplete, surrogate-encoded, overlong, or out of range — instead the tool raises a clear error.
This behavior is useful in two everyday cases. First, when you have encoded a string yourself and want to confirm a clean round trip — paste the output back into the decoder and check that you got the original characters, byte for byte. Second, when someone hands you a binary dump that was truncated mid-character, such as a four-byte emoji represented by only three groups: the decoder will fail rather than print "?" or U+FFFD, which tells you exactly where to look. The decoder accepts up to 180,000 input characters, and any group that does not match [01]{8} — including ones with a 0b prefix, commas, tabs, or more than one space — is rejected up front. The companion guide How Binary to Text Conversion Works in Plain English walks through the same decoding rules in more depth if you want a longer read.
Staying Strict: Why Exact Grouping Matters
Binary text is ambiguous unless the character encoding and grouping rule are spelled out. The converter picks one convention and enforces it: UTF-8 bytes, exactly eight bits per group, exactly one ordinary space between groups. There is no trimming, no leading-zero padding of partial groups, no merging of consecutive spaces, and no forgiveness for stray line breaks. This strictness is what makes the output reliable for protocol, source-code, and forensic work, where the difference between 01000001 and 1000001 can change the meaning of a byte.
Eight independent golden cases cover the full width spectrum — ASCII, a normal English word, two-byte Latin text, a three-byte currency sign, a four-byte emoji, CJK text, a line-feed control byte, and a mixed-width string — and the expected bytes for each case are written independently of the implementation. The same tests cover the maximum input budgets (20,000 code units for encoding and 180,000 characters for decoding), invalid grouping, repeated spaces, incomplete UTF-8, and exact byte counts. For a deeper technical reference, the WHATWG Encoding Standard defines the UTF-8 encoder used in the browser, and the MDN TextEncoder reference documents the exact byte-for-byte behavior the tool relies on.
Copying Binary Out of Excel Without Breaking It
The most common way an Excel-based workflow fails is not the encoding itself but the handoff. Once you have a clean UTF-8 byte stream, copy or store it only in systems that preserve ordinary spaces and line content exactly. Chat clients, rich-text editors, and some Markdown renderers collapse multiple spaces into one, insert soft line breaks, or strip leading and trailing whitespace — and any of those changes will make the strict decoder reject the stream with a clear error. The fix is almost always environmental: paste into a plain-text field, a code window, or a .txt file rather than a chat box, and verify with the converter's byte count that the group count matches what you encoded.
It is also worth remembering that this is an encoding utility, not encryption. The binary output contains exactly the same information as the original Unicode string and provides no confidentiality, authentication, integrity, compression, or password protection. Anyone who receives the byte stream can read the original text back, so do not treat it as a way to hide a secret. For reversible ciphers, hashing, or authenticated encryption, reach for a different tool in the encoding category — the converter does not parse numeric binary values, files, Base64, hexadecimal, Morse code, or any custom legacy character set, and it will refuse inputs that mix those formats with eight-bit byte groups.
For a deeper look, see Text Steganography for Beginners: A First Walkthrough.