1. Input→ 2. Transform→ 3. Copy

Base64 / URL / HEX Encoder

Six operations, unicode and emoji safe, auto-detect, live as you type.

Text & dev tools

Input 0 chars · 0 bytes
UTF-8 aware — हिंदी, 中文 and 🚀 all work.

Overrides the tabs while active.

Off = single scrollable line (easier to select).

Any file → data:mime;base64,… — for embedding in CSS/HTML. Images also show a preview.

Output —
// output appears here
Pick an operation and type above.

Which operation do I need?

  • Base64 — data URIs, basic-auth headers, email attachments.
  • Base64URL — JWTs and URL-safe tokens (uses -_ instead of +/, no padding).
  • URL encode — making a string safe inside a link: spaces → %20, & → %26.
  • HEX — byte-level inspection: A → 41. For debugging encodings and binary data.
  • Data URI — Advanced section converts any file to an embeddable Base64 string.

Base64/URL — FAQ

Base64 vs URL encoding — when do I use which?

Base64 turns binary/text into safe-to-transmit ASCII (data URIs, basic-auth headers, JWT parts). URL encoding makes a string safe inside a URL. If your output will live in a link or query string, use URL encode — or Base64URL if it's a token.

What's Base64URL and why does JWT use it?

Standard Base64 contains +, / and = — all meaningful inside URLs, which breaks tokens. Base64URL swaps them for -, _ and drops padding, so the output can sit in a URL unescaped. That's the JWT standard (RFC 7515).

Is Base64 encryption?

No — it's encoding, not encryption. Anyone can decode it instantly. Never treat Base64 as a way to hide secrets; use it for transport, use real encryption for secrecy.

Does it handle emojis and non-English text?

Yes — encode goes through UTF-8 first, so हिंदी, 中文 and 🚀 all round-trip correctly. Decode expects UTF-8-safe Base64, the standard everywhere.