Base64 encode / decode
Encode UTF-8 text or decode Base64 back to text.
Result
Start typing and the result appears here. No button needed.
Base64 encode / decode, without the extra steps.
Convert UTF-8 text to standard Base64, or decode Base64 into UTF-8 text. Decoding accepts what people actually paste: standard or URL-safe alphabets, missing padding, and a leading data URI prefix. This is useful for inspecting JWT payloads and interoperability examples. Base64 is an encoding, not encryption.
How to use this tool
- 1Paste text, or Base64 in any common form.
- 2Choose Encode or Decode.
- 3Copy the result.
When Base64 encode / decode is the right tool
- A config or token field expects a Base64 value.
- A log line contains an encoded payload you need to read.
- A small asset needs embedding as a data URI.
- A Basic auth header needs constructing or inspecting.
Base64 is transport, not security
Base64 maps binary data onto 64 safe text characters so it survives channels that expect text. It uses no key and anyone can reverse it instantly, so encoding a password or API key protects nothing at all. Its legitimate uses are embedding binary in JSON, email, and data URIs. Expect roughly a third more size than the input, since three bytes become four characters.
UTF-8, padding, and variants
Text is encoded as UTF-8 first, so emoji and non-Latin scripts round-trip correctly rather than being mangled. Standard Base64 uses + and / with = padding; the URL-safe variant substitutes - and _, and a value produced for a URL may need converting before it decodes here. Whitespace and line breaks inside an encoded blob are generally tolerated on decode.
A few quick answers.
Paste text, or Base64 in any common form. Choose Encode or Decode. Copy the result.
Tool inputs are processed in your browser. Crate has no upload endpoint and no accounts. Downloaded site assets and a cookie-free page-view count still require a connection; your files and text are not included in those requests.
This tool handles UTF-8 text, not arbitrary binary downloads. Invalid Base64 or invalid UTF-8 returns an error. Encoding always produces the standard padded alphabet; decoding also accepts URL-safe and unpadded input.
No. It uses no key and anyone can decode it instantly. It is a transport encoding, not encryption, so never rely on it to protect a credential.
The URL-safe variant swaps + and / for - and _. Convert it back to the standard alphabet before decoding.