Base64 encoder & decoder

Base64 encoder & decoder features

• 01

  Standard and URL-safe Base64

  Toggle between the classic Base64 alphabet (+, /, padding) and the URL-safe variant (-, _, no padding) used by JWTs, OAuth, and signed URLs. The same tool handles both without any dependency lookup.

• 02

  Full UTF-8 support

  Non-ASCII text — emoji, Cyrillic, Chinese, Arabic — encodes and decodes correctly because Handytool uses native TextEncoder and TextDecoder under the hood. No more "malformed UTF-8" errors from older Base64 tools.

• 03

  Private by design

  Encoding and decoding happen entirely in your browser. Nothing is uploaded, logged, or stored. Paste API tokens or secret strings safely — they never leave your device.

Base64 encoder & decoder FAQ

What is Base64 and when should I use it?

Base64 represents binary data as printable ASCII characters. It's used to embed images in CSS, send binary payloads over JSON APIs, store credentials in HTTP headers, and encode JWT claims. It's not encryption — anyone can decode it — but it's useful whenever a channel only accepts text.

What is URL-safe Base64?

Standard Base64 uses + and / characters that have special meaning in URLs. URL-safe Base64 replaces them with - and _ and drops the trailing = padding. JWTs, OAuth tokens, and signed URLs all use this variant. Toggle the option on when working with those formats.

Does Handytool handle Unicode and emoji correctly?

Yes. The encoder converts your text to UTF-8 bytes first using the browser's TextEncoder, so emoji, accented characters, and non-Latin scripts encode and decode losslessly.

Is Base64 encryption?

No. Base64 is encoding, not encryption — it's fully reversible by anyone. Use it to transport data safely through text channels, not to hide secrets. For actual secrecy, use real encryption (AES, RSA, TLS).

Is my input uploaded to a server?

Never. The encoder runs entirely in your browser using the built-in btoa / atob and TextEncoder APIs. Nothing is sent to a server, logged, or stored.