ToolWox
Log inSign up

Base64 Encode

Base64 Encode turns any text — including emoji, accented characters and CJK — into a Base64 string. It supports both the standard +/ alphabet and the URL-safe base64url variant used in tokens and query parameters.

Encoding runs entirely in your browser, so the text you paste never touches a server. That makes it safe for snippets that contain credentials, payloads or other sensitive data.

Standard Base64 with the +/ alphabet and = padding. Handles full Unicode (emoji, accents, CJK).

Text input
Base64 output

How to use Base64 Encode

  1. 1

    Choose an alphabet

    Pick Standard for classic Base64, or URL-safe to get base64url (- and _ instead of + and /, with padding removed).

  2. 2

    Paste your text

    Type or paste into the input box — the Base64 output updates instantly as you go.

  3. 3

    Copy the result

    Use the Copy button to grab the encoded string.

What is Base64?

Base64 is an encoding that represents binary data using 64 printable ASCII characters. It is not encryption — it is a reversible way to move arbitrary bytes through systems that only handle text, such as JSON fields, email bodies, and data URIs.

Encoding inflates the size by roughly 33%, because every three bytes become four characters. That overhead is the trade-off for being able to embed binary safely inside text-only formats.

Standard vs URL-safe Base64

Standard Base64 uses + and / and pads the end with =. Those characters have special meaning in URLs and filenames, so they must be percent-encoded when used there.

The URL-safe variant (base64url) swaps + for - and / for _, and usually drops the = padding. It is what JWTs and many APIs use so the value can sit in a URL or path segment untouched.

Frequently asked questions

Does Base64 encrypt my data?
No. Base64 is encoding, not encryption — anyone can decode it. Never use it to protect secrets; use it only to transport data through text-only channels.
Does it handle emoji and non-English text?
Yes. The text is encoded as UTF-8 first, so emoji, accents and CJK characters all round-trip correctly.
Is my text sent to a server?
No. Encoding happens entirely in your browser.

Last updated: