How it works
Text is encoded as UTF-8 before Base64 conversion. Base64 is an encoding, not encryption.
UTF-8 text ↔ binary bytes ↔ Base64.
Debugging scenario
Encode a short UTF-8 fixture containing ASCII, Chinese text and an emoji, then decode it and compare Unicode code points. When debugging an API, first determine whether it expects standard Base64 or Base64url and whether padding is required.
How to interpret the result
A successful round trip confirms this browser converted the selected text representation consistently. Base64 changes representation, not confidentiality or integrity. Binary files decoded as UTF-8 can become corrupted, and the URL-safe alphabet differs in the characters used for indices 62 and 63.
Input reference
- Mode
- Example default: Encode
- Input
- Example default: Sample input included
Common mistakes
- Pasting secrets, credentials, customer records or other production data into a browser tool or shareable URL.
- Using Base64 as encryption or confusing standard Base64 with unpadded Base64url.
- Treating a convenient preview as validation by the target runtime, parser, database or security control.
Before using the result
- Reduce the input to a synthetic example that still reproduces the behavior.
- Compare bytes, alphabet and padding requirements with the receiving protocol implementation.
- Add the accepted input and expected output to the project regression tests before release.
Questions to check before production use
Is Base64 secure?
No. Anyone can decode it. Do not use it to protect secrets.
Are Unicode characters supported?
Yes, the tool converts UTF-8 text before encoding.
Independent developer utility. Review output before using it in production.