WebToolArcHow binary bits become Base64
Base64 encodes bytes, not an abstract stream of unbounded bits. First establish 8-bit byte boundaries, then Base64 takes three bytes (24 bits) at a time, divides those bits into four 6-bit values, and maps each value to one character in the 64-character alphabet.
Byte alignment comes before Base64 padding
If a binary text string contains 13 bits, the missing three bits are part of the source-byte interpretation problem. That is different from Base64 = padding, which is added only after the byte sequence is known. This Studio therefore rejects incomplete bytes by default and records any explicit zero-padding transformation separately.
Standard Base64 vs Base64URL
Standard RFC 4648 Base64 uses + and /. Base64URL uses - and _ so the encoded value is easier to place in URLs and filenames. URL-safe output often omits =, but alphabet choice and padding choice are separate decisions.
Why encoded data grows
Every three source bytes become four Base64 characters. For large inputs that is roughly 33% size growth before line breaks or a Data URI prefix. Small inputs can have a larger percentage overhead because the final group still occupies two to four Base64 characters.
File bytes and bit text are not the same input
A file containing the characters 01000001 has eight ASCII bytes unless you explicitly interpret those characters as a textual bitstream. File mode encodes the raw file bytes; bitstream mode interprets 0 and 1 as bit values. Keeping those modes separate prevents a common conversion mistake.
Can I paste spaces between bytes?
Yes. Whitespace and common visual separators are ignored. Invalid characters are reported by their raw input position.
What does the sextet table prove?
It exposes each 24-bit group, its four 6-bit chunks and the exact Base64 characters they select, making the algorithm auditable rather than a black box.
Can I use URL-safe Base64?
Yes. Switch the alphabet to Base64URL and independently choose whether trailing = padding is kept.
Does the tool upload files?
No. Local file bytes are read by browser APIs and converted on-device. There is intentionally no remote URL-fetch mode on this focused page.
Is Base64 secure?
No. Base64 is reversible encoding and provides no secrecy. Use appropriate cryptography when confidentiality or integrity is required.
Why show SHA-256?
The digest is calculated over the raw source bytes so you can compare the exact payload across representations. It is evidence of byte identity, not encryption of the content.