Toolza guides / developer

Encode UTF-8 Text as Base64

Round-trip a text value through Base64 without mistaking its encoded representation for encrypted or compressed data.

Use the interactive tool ↓

Decide whether your input is text or binary

This utility converts text to UTF-8 bytes before Base64 encoding. In the reverse direction, it decodes bytes as UTF-8 text. It is useful for readable text payloads; it is not a file uploader or a general binary-file recovery workflow.

Try it here

Base64 Encoder / Decoder

Processed on your device. Your files never leave your browser.
Open the standalone Base64 Encoder / Decoder tool →

Reproduce a small round trip

With Encode selected, enter Hello. The expected output is SGVsbG8=. Select Decode, paste that output into the input, and expect Hello again. Copy the output rather than replacing characters by eye.

A non-ASCII character may use several UTF-8 bytes, so character count is not the byte count used by Base64. Encoding can make the representation longer; it does not compress the original value.

  1. Select the direction before entering data.
  2. Paste a small known value first.
  3. Copy the result into the reverse mode.
  4. Compare the recovered text, including spaces and line breaks.

Understand padding and alphabet differences

Standard Base64 uses letters, digits, + and /, with = padding where needed. This decoder removes whitespace before decoding, which can help with wrapped text. It does not automatically remove a data: URL prefix or turn an entire URL into its embedded payload.

Base64URL replaces some alphabet characters and often omits padding. Do not assume every Base64URL value can be pasted unchanged into this standard decoder. JWT segments use Base64URL; JWT Decoder is a more suitable inspection tool for those structured tokens.

Troubleshoot damaged output

If decoding fails, check for a prefix, missing copied characters, or the wrong alphabet. If output contains replacement characters, the decoded bytes may not be valid UTF-8 text. That does not establish that the Base64 envelope itself was corrupt: binary bytes can be valid Base64 without being readable text.

Keep the security distinction clear

Anyone with the encoded text can reverse an ordinary Base64 encoding. It provides neither confidentiality nor a signature proving who created the value. Use fictional examples when inspecting an unfamiliar environment. The conversion runs in the browser; website requests for assets and analytics are separate from the text-processing operation.