Numeric input fails
use only the notation and separators documented for this tool. An out-of-range or incomplete byte is invalid.
Encode binary bytes as standard or URL-safe Base64 while preserving the source representation. Review, copy or download the result.
This page encodes binary bytes into Base64 without applying format-specific validation or transformation. Use Standard or URL-safe output according to the receiving protocol, then copy or download the value.
Convert now
Enter or upload
Paste text or choose a file
Choose an action
Encode, decode or inspect
View results
Review output and byte details
Input bytes
101010 111100 110101 ...
Split into 6-bit groups
101010 111100 110101 ...
Convert to indexes
42 60 53 ...
Base64 characters
q 8 1 ...
Paste the byte sequence using the notation described for this tool.
Keep Encode selected and choose the output option shown by the tool.
Review the output and byte information, then copy or download the result.
The parser reads 0 and 1 as byte-aligned 8-bit groups, strips allowed whitespace, and rejects a total bit count that is not a multiple of eight.
Use Standard Base64 for the normal RFC 4648 alphabet. Use URL-safe only when the receiving system expects Base64URL; padding rules can differ by protocol.
Record byte order separately. Base64 preserves sequence, but it does not explain whether a multi-byte number is big-endian or little-endian.
Typical workflows include:
Important constraints:
use only the notation and separators documented for this tool. An out-of-range or incomplete byte is invalid.
verify byte sequence, endianness and field boundaries; Base64 does not store numeric meaning.
The parser reads 0 and 1 as byte-aligned 8-bit groups, strips allowed whitespace, and rejects a total bit count that is not a multiple of eight.
Use the exact byte notation described for this tool. Decimal, binary, hexadecimal and octal inputs are handled by separate converters, and the wrong notation is rejected.
Standard Base64 uses + and /. Base64URL uses - and _ and may omit padding; choose the form required by the receiving system.
No. It preserves the byte sequence only. Record endianness, signedness and field boundaries separately when they matter.
Continue with the localized page that matches the next operation:
Paste your input above, run the conversion, and copy or download the result.