Base64
UTF-8 and URL-safe encode/decode for samples and non-sensitive values.
Copies this page address only, without URL inputs, tracking parameters or a section anchor. It does not share calculation results.
Base64, Unicode-safe.
Convert UTF-8 text including Korean, Japanese and emoji. Non-text bytes produce an error instead of altered text. URL-safe variant included.
Input
Getting ready. Input becomes available when the tool is ready. If this message stays, reload or check that JavaScript is enabled. Conversion runs in your browser, but that does not make live tokens, passwords, or private data safe to paste into a website. Use sample or non-sensitive test values only.
Output
Output appears here.
Base64 that doesn’t break on Unicode
The browser’s built-in btoa expects byte-sized characters, so Korean, Japanese, and emoji cannot be passed to it directly. This text tool first encodes ordinary Unicode text as UTF-8. On decoding, it rejects bytes that are not valid UTF-8 instead of silently replacing them; it is not a binary-file converter. Both standard and URL-safe Base64 input are accepted.
Standard vs URL-safe
Standard Base64 uses +, /, and = padding. This tool’s URL-safe mode swaps +// for -/_ and removes padding. That changes the alphabet, not the privacy of the data; check the receiving format’s padding rules before using it.
Use non-sensitive examples
Encoding and decoding run in your browser, but that alone does not make a website safe for live tokens, credentials, or private snippets. Use the built-in sample or non-sensitive test values. Follow an approved local workflow for production secrets.
FAQ
Why is encoded text about a third longer?
Base64 represents every 3 bytes as 4 ASCII characters, so output grows by roughly 33%. That overhead is the cost of being text-safe.
Can it encode files or images?
This tool focuses on text. For data URLs of images, a dedicated file encoder is better — the principle (3 bytes → 4 chars) is the same.