Quick reference
| Setting | Value / behavior |
|---|---|
| Example | Hello → SGVsbG8= |
| Encoding | UTF-8 |
| Security | no encryption |
How to use the result
Base64 represents bytes using a restricted alphabet so they can travel through text-oriented systems. It is an encoding, not encryption. Anyone with the value can decode it. This tool first converts text to UTF-8 bytes, then encodes those bytes, so accented characters and emoji are handled consistently. Decode expects UTF-8 text rather than arbitrary binary data. Standard Base64 uses + and /; JWT uses the separate Base64URL alphabet.
Limits and interpretation
Encoding typically increases storage to roughly four characters for every three source bytes, plus padding. Remove surrounding whitespace from a copied value, but do not assume that a Base64-looking string is safe or trustworthy. Invalid alphabet characters and impossible lengths are rejected. If decoding succeeds but the bytes are not valid UTF-8, the tool reports an error instead of replacing characters silently. Use an actual binary decoder for images or archives.
Check against your destination
Run the supplied example first, then replace it with a representative input from your own workflow. Change one parameter at a time so the effect is easy to inspect. Copy or download the output and compare it with a small known case before using it in a larger system. A successful calculation establishes only the behavior described on this page; it cannot check the assumptions or access rules of a remote application. Errors are shown next to the workspace rather than silently returning an empty success.
Local processing and data handling
This tool runs in the browser and does not transmit the entered content to a processing service. No input is saved to local storage, added to the URL or synchronized to an account. The clear control removes the current field and displayed result from this page. Clipboard contents and downloaded files remain under your operating system’s control. Keep original inputs when exact byte preservation matters, and avoid including sensitive tokens or private text in screenshots that you later share.
Frequently asked questions
Does the tool contact my server?
No. It processes the provided input locally and does not execute commands on your systems.
Can I download the result?
Yes. Use the Download result control after a successful run.
What happens to my input?
It remains in this page until cleared or closed. It is not saved by the tool.
About this tool
Built and maintained by Mihai at Void Fabric. This page documents the behavior of the current implementation. Found an error or an unclear assumption? Send a reproducible example with sensitive values removed.
Reference: Void Fabric field notes · Testing and editorial policy