Base64 Encode

Base64 Encode turns text or a file into a Base64 string you can paste into code, JSON, an email header or a data URI. Type text and it is encoded as UTF-8, or drop any file into the box and its raw bytes are encoded instead. The tool is free and runs in your browser, so nothing is uploaded.

How the Base64 Encode tool works

Type or paste text and it is converted to UTF-8 bytes first, then encoded. That first step is why text in Urdu, Arabic or Chinese, and even emoji, survive the round trip where plainer tools fail or corrupt them. Or skip the text box entirely and drop a file in. The tool reads the raw bytes of the file and encodes those, which is how people turn a small image or a PDF into a string.

1. Type or paste the text you want to encode, or drop a file into the box.
2. Leave both toggles off for standard Base64, or switch on the URL-safe alphabet or the 76 character wrapping.
3. Watch the counts as you work: bytes in, characters out.
4. Copy the string into your code, JSON, header or document.

Base64 grows data. Three bytes become four characters, so the output runs about a third longer than the input, and the counts under the result show the exact numbers for what you pasted. When the string has to come back one day, the matching Base64 Decode page reverses the trip.

When Base64 Encode is the right tool

Embedding is the everyday job. A developer encodes a small image, an icon or a font, then builds a data URI from the string inside CSS or HTML, so the picture travels inside the document itself and no separate file has to be hosted or fetched.

APIs ask for it constantly. Plenty of services accept a file only as a Base64 string inside a JSON payload, and plenty of older systems pass attachments the same way through email in the wrapped MIME style. The byte and character counts on this page tell you the size of the payload before you send it anywhere.

Tokens and headers round out the list. The URL-safe toggle swaps + and / for – and _ and drops the padding, which is the form a string needs to sit safely inside a web address. Encoding a password never protects it, because anyone who sees the string can decode it in seconds, so treat encoded values as readable text, never as hidden ones.

Base64 Encode rules and honest limits

The first rule is the one people get wrong. Base64 is encoding, not encryption. It changes how bytes are written so they can travel through systems built for text, and it hides nothing. Never use it to protect a password, a key or anything else that needs to stay secret.

Text is always read as UTF-8 on this page. That covers modern writing systems and emoji, and it is the right default for the web. Old systems that expect a legacy charset such as Latin-1 are not covered here, and a string encoded for one of those systems belongs in a different tool.

Files carry a practical limit rather than a hard cap. The whole file is read into your tab, and the string that comes out is about a third longer again. A very large file makes a very long string, and very long strings choke some text fields and clipboards. Encode big files only when the place you are pasting into can take them.

Your files stay in your browser

The encoding runs on your device. Text you type and files you drop are not sent to a server, not stored by ToolPeko and not read by anyone here. There is no account, no daily cap and no file size gate set by us. Close the tab and everything you encoded is gone with it.