Skip to content
Kiln
Tools

Developer

Base64 encoder

Turn text into Base64, or turn Base64 back into text. Standard and URL-safe alphabets are both supported, and the input box is left unchanged.

It runs in your browser. What you enter stays on this device.

The original stays in this box. Encoding uses UTF-8, so accents and emoji survive a round trip.

Off uses standard Base64 (+, /, and = padding). On uses URL-safe Base64 (- and _, with padding omitted).

Examples

Load a sample into the form, then run it.

How to use it

  1. 1Paste text to encode, or Base64 to decode.
  2. 2Choose Encode or Decode.
  3. 3Turn URL-safe on only when you want - and _ instead of + and /.
  4. 4Choose Convert, then copy the result. Choose Clear to empty the box.

When it helps

  • Read a Base64 fragment from a token or a data field.
  • Prepare a UTF-8 string for a system that asks for Base64.
  • Make a short value safe to place in a URL.

Good to know

  • Text is encoded as UTF-8. This page does not use the Latin-1 behavior that corrupts accents and emoji.
  • Decode ignores spaces and line breaks. Other characters that are not in the selected alphabet are rejected.
  • URL-safe output omits = padding. Standard output keeps it.
  • The result is text. This page does not offer a binary file download.
  • The input stays under 500 KB.

Questions

What is the difference between standard and URL-safe Base64?

Standard Base64 uses +, /, and = padding. URL-safe Base64 replaces + with - and / with _, and this tool omits the padding. Pick the alphabet your other system expects.

Is the text uploaded?

No. Encoding and decoding run in this browser. The text is not sent to a server or included in analytics.

Related tools

  • URL encoder

    URL encoder

    Encode or decode a URL component or a full URI in the browser.

    Developer

  • JWT decoder

    JWT decoder

    Decode a JWT header and payload in the browser. The signature is not verified.

    Developer