Skip to content
Free developer tool

Base64 encoder

This Base64 encoder converts text into Base64, a way of writing any bytes using only 64 safe letters, digits and symbols. Developers use it to put text into data URLs, config files, HTTP headers and APIs that only accept plain characters.

  • Runs in your browser
  • Free, no account needed
  • Copy or download the result
Private: runs on this device

Input

16 characters

Result

SGVsbG8sIHdvcmxkISDwn5GL

Example

Input
Hello, world! 👋
Result
SGVsbG8sIHdvcmxkISDwn5GL

How to use the base64 encoder

  1. Type or paste your text into the Text to encode box.
  2. Pick an Alphabet: Standard Base64 or Base64url.
  3. Pick a Padding option: Keep = padding or Omit padding.
  4. Press Run, then use Copy result or Download.

How it works

Your text is first turned into UTF-8 bytes, so accented letters and emoji encode correctly.

Base64url swaps + for - and / for _, so the result is safe inside URLs and file names.

Omit padding removes the trailing = signs, which some formats such as JWTs leave out.

Text containing an unpaired surrogate (a broken half of an emoji) is rejected with an error.

Base64 is an encoding, not encryption. Anyone can decode it, so it does not hide secrets.

Everything runs in your browser. Your input is not uploaded or stored.

Questions and answers

Is Base64 encryption?

No. Base64 only changes how bytes are written. Anyone can decode it without a key, so it gives no secrecy.

What is the difference between Base64 and Base64url?

They work the same way but use two different characters. Standard Base64 uses + and /, while Base64url uses - and _ so the output can sit in a URL without extra escaping.

Why does my Base64 end with = or ==?

The = signs are padding that bring the length up to a multiple of 4. Choose Omit padding if the system you are feeding wants them removed.

Is my text uploaded?

No. Encoding happens in your browser and your text is not sent anywhere.

All 100 SnowRock tools