Input
Mode:
Output
Formatted result will be displayed here
Base64 maps every three bytes of input to four ASCII characters chosen from a 64-character alphabet, letting you carry arbitrary binary or UTF-8 text through channels that only accept plain ASCII. This tool treats your input as UTF-8, encodes it, and returns the standard Base64 string you can paste into headers, JSON fields, or YAML values without worrying about quoting or control characters.
Encode user:password strings into the Base64 blob that Authorization headers expect for quick API testing.
Wrap awkward content with newlines or quotes as Base64 so the surrounding JSON never has to worry about escaping.
Pack short text payloads into query strings where raw bytes would break the URL parser.
Kubernetes secrets and many CI systems expect values in Base64 form, even when the underlying data is plain text.
No. It is an encoding, not a cipher. Anyone with the string can decode it in one step, so never use Base64 to hide secrets.
Those are padding characters that round the length out to a multiple of four. They mean the input length was not divisible by three.
Yes. Text is read as UTF-8 before encoding, so any Unicode character including emoji is preserved through a decode-round trip.
Base64 inflates data by about 33 percent plus up to two padding characters.