Skip to main content

Base64 Encoder/Decoder

Convert text to Base64 and back

Enter text to encode

Supports UTF-8, Latin-1, and Hex text encoding with standard or URL-safe Base64 variant. All processing happens locally in your browser.

About Base64 Encoder/Decoder

Encode text or binary data to Base64 and decode Base64 strings back to their original form, entirely in your browser. Base64 is a binary-to-text encoding scheme that represents binary data using a set of 64 ASCII characters, making it safe for transport in text-based systems like email, JSON, HTML, and URLs. This tool supports standard Base64 and the URL-safe Base64 variant (Base64url), and can handle both text input and file uploads. All encoding and decoding runs client-side — your data never leaves your device.

How to Use Base64 Encoder/Decoder

  1. Paste your text or upload a file in the input area.
  2. Select Encode to convert to Base64, or Decode to convert Base64 back to the original.
  3. Choose between standard Base64 and Base64url format if needed.
  4. Copy the result from the output area using the copy button.

Base64 Encoder/Decoder FAQ

What is Base64 used for?

Base64 converts binary or text data into ASCII-safe output for transport and storage in text-based systems like JSON payloads, email attachments (MIME), data URIs in HTML/CSS, and HTTP headers.

Is Base64 encryption?

No. Base64 is an encoding scheme, not encryption. Anyone can decode a Base64 string without a key. It is used for safe transport of data, not for securing it.

What is the difference between Base64 and Base64url?

Base64url replaces + with - and / with _ to make the output safe for URLs and filenames. It also typically omits padding characters (=).

Can I encode files with this tool?

Yes, you can upload a file and the tool will encode its binary content to Base64. This is useful for embedding images or other assets as data URIs.

Why does Base64 increase the size of data?

Base64 represents every 3 bytes of input as 4 ASCII characters, resulting in roughly a 33% size increase. This trade-off provides text-safe representation of binary data.