Home     All Utilities


Base64 Encode/Decode

Latest version: v1.0

Windows XP, Windows Vista, Windows 7, Windows 8

Cost: $0 (Free)


Was this application useful to you? Support it by making a donation.

Donations of any size are welcome and greatly appreciated.

Base64 Encode/Decode

Use Base64 Encode/Decode to encode to the Base64 encoding or decode from.

This application is a desktop version of our online tool for encoding/decoding Base64 formatted texts.

The application looks identical to our web version of Base64 Encode/Decode. Click on the following screenshots to see how it appears on a Windows 7 desktop:

Webatic Base64 Encode/Decode screenshot 1 Webatic Base64 Encode/Decode screenshot 2 Webatic Base64 Encode/Decode screenshot 3

Notice: This application uses regular visual controls to show text. It is meant to handle human readable characters. ASCII control characters or unicode characters out of the ordinary viewable range may not be handled correctly.

Documentation / Manual

How to convert plain text to Base64

Type your text, or copy/paste, to the text box on the top, then click the "Encode" button.

You can optionaly use the "Chunk" text box to split the encoded text to chunks of a fixed number of characters. You can simply enter the size of your chunk and hit the "Encode" button.

How to convert Base64 encoded text to plain text

Type your text, or copy/paste, to the text box on the bottom, then click the "Decode" button.


After encoding to Base64, I don't get the same results compared to other conversion software

The reason for this problem might involve a number of issues regarding characters that are non-viewable by humans.

One common case is the control (and non-viewable) character for changing the line. In MS Windows this is usually CR/LF (aka \r\n, aka ASCII 13 10, aka ASCII 0x0d 0x0a) whereas in Unix, Linux, Mac it usually is just LF (aka \n, aka ASCII 10, aka ASCII 0x0a). Practically speaking, when you copy/paste multi-line text from MS Windows, you may get a different Base64 encoded result from someone who would do the same on an Apple Mac.

Another common case that may cause problems is related to the character set you are using. For example you are most probably using an ANSI character set and that would give you a different result from the case you would use a Unicode character set (common case in websites).

After decoding from Base64, I get a shorter result than I expected

Following the spirit of the answer to the previous issue, non-viewable characters are most probably causing this problem. A probable case would be to have a null character (0x00) that ends the character string prematurely.

My text contains non-regular characters and I don't get the expected encoding or decoding result.
How do I solve it?

As highlighted in the notice above, this application is build to cope with regularly formated texts, viewable by humans. Or in simpler words, texts that do not contain control characters or unicode characters. In order for you to find a final answer to messages with non-regular characters, you must use your programming skills to make a script that makes an appropriate binary/hexadecimal analysis of your use case.