Base64 Generator

Encode a given string to Base64.

Hash settings

Rounds

1

Change your passwords periodically.

2

Never use the same password on multiple sensitive accounts.

3

Use a password with at least 16 characters. It should contain lowercase letters, uppercase letters, numbers, and symbols.

4

Refrain from saving your password in a web browser (Firefox, Chrome, Internet Explorer, Safari). Instead, use a tool which manages an encrypted password locker.

5

Do not log into sensitive accounts while connected to a public Wi-Fi hotspot.

6

Check that you are using a secure (HTTPS, SSH, SFTP) connection before transmitting your password over the web.

What is Base64 encoding?

Base64 is a way of representing binary or text data using only 64 printable ASCII characters (A–Z, a–z, 0–9, +, /, and = for padding). It's not encryption (anyone can decode it), but it's the standard way to safely embed data (like images, files, or credentials) inside places that only accept plain text, such as JSON payloads, URLs, email attachments, or HTTP Basic Auth headers.

How to use this tool

Type or paste a string into the input field, choose how many rounds to apply, and click Generate BASE64. Multiple rounds re-encode the previous output, which produces progressively longer Base64 strings, useful for testing how your own decoding logic handles nested encoding. Copy the result with the clipboard icon.

Common use cases

Embedding a small image or file directly inside CSS, HTML, or a JSON payload as a data URI.
Encoding credentials for an HTTP Basic Auth header.
Safely including binary data (like a certificate or key) inside a plain-text config file or environment variable.
Preparing an attachment's contents for transport inside an email or API request that only accepts text.

Frequently asked questions

Is Base64 the same as encryption?

No. Base64 is an encoding, not encryption; anyone can decode a Base64 string back to its original form instantly, with no key or password needed. It doesn't add any security, only a text-safe representation of binary or arbitrary data.

Why does the output end in one or two `=` characters?

Base64 encodes data in 3-byte chunks, and = is padding added when the input length isn't a multiple of 3. It tells a decoder how many of the last group's characters are real data versus padding.

Why is the Base64 output longer than my original string?

Base64 trades space for safety: every 3 bytes of input become 4 characters of output, so encoded data is always roughly 33% larger than the original.

Does this tool decode Base64 as well as encode it?

This page only encodes. If you need to convert a Base64 string back to its original text, most modern browsers' developer consoles support atob(), or you can reverse the process with any standard Base64 library.