← Every block

Base64 Encoder & Decoder

Encode and decode Base64, including URL-safe. Nothing is uploaded.

Try one

Need to chain this with something else? Open in bode →

About Base64

What Base64 is for

Base64 rewrites arbitrary bytes using 64 characters that survive text-only channels: A–Z a–z 0–9 + /. It exists because e-mail, JSON, XML and URLs were designed for text, and raw bytes break them.

It costs roughly a third in size — three bytes become four characters — so it is for getting data through a text channel, not for storing or sending it efficiently.

It is not encryption

Anyone can decode Base64. There is no key and no secret. A password or an API key that is "Base64 encoded" is stored in plain text with an extra step.

The one common exception looks like an exception and is not: HTTP Basic auth sends user:password Base64-encoded, which is why it is only safe over HTTPS — the transport does the protecting, not the encoding.

URL-safe, and padding

+ and / have meaning in URLs and filenames, so the URL-safe alphabet replaces them with - and _. JWTs use it; so do many APIs.

Standard Base64 pads to a multiple of four with =. URL-safe output usually drops the padding, and decoders are expected to add it back — this one does, so a value copied out of a token decodes without hand-editing.

Common questions

Is Base64 a way to hide data?
No. It is an encoding, not encryption — decoding needs no key and takes one step. Use it to move bytes through a text channel, never to protect them.
Why does my encoded string end in = or ==?
Padding. Base64 works in groups of three bytes; when the input does not divide evenly, one or two = characters make up the length. URL-safe values often omit them, and this decoder adds them back for you.
Can I Base64 encode a file?
Yes. Open it with the File block and wire its output in. Bear in mind the result is about a third larger than the file, so a large one gets unwieldy quickly.