Overview
Enter a binary value as a string of bits (e.g. "01001000 01101001") and get its Base64 encoding. Critically, the bits are first grouped 8 at a time into the actual bytes they represent, and those bytes are what gets Base64-encoded - the literal characters "0" and "1" that make up the input text are never themselves encoded. That distinction matters: Base64-encoding the ASCII text "01001000" directly would produce a completely different, meaningless result compared to decoding those bits into the single byte 0x48 and encoding that byte. Whitespace between groups of bits is optional and stripped automatically, but the total number of bits must be a multiple of 8 (one full byte) - a stray or missing bit is rejected with a specific error rather than silently truncated or padded. Runs entirely client-side.
Best for: Encoding a raw binary bit sequence (from a protocol dump or bitmask) into Base64 for transport
How to use this tool
- Enter your binary bits. A string of 0s and 1s, optionally grouped with spaces, e.g. 01001000 01101001.
- Bits become bytes. Every 8 bits is read as one raw byte - not eight separate characters.
- Bytes are Base64-encoded. The assembled byte array is encoded to Base64, exactly like any other binary data.
Frequently asked questions
No - that would produce a meaningless result. The bits are first decoded into the single byte they represent (0x48 in this example), and Base64 encoding is applied to that byte, not to the literal digit characters of the input.
It's rejected with a specific error stating the bit count found. A byte is always exactly 8 bits, so a bit count that doesn't divide evenly by 8 means the input is incomplete or malformed, and guessing how to pad it would risk encoding the wrong bytes.
No - it's entirely optional and stripped before parsing, so both "01001000 01101001" and "0100100001101001" are accepted and produce the same result.