Converter
Base64, UTF-8, UTF-16, ANSI, Hex & Every Format In Between
Convert text between any two encodings, directly - no plain-text stopover required
Results are provided for informational purposes only and may contain errors. Please verify important information independently. Use of this tool is at your own risk.
About these encodings
This tool covers 30 formats across a few different categories: character encodings (UTF-8, UTF-16, UTF-32, ANSI/Windows-1252, ISO-8859-1) that determine how text becomes bytes in the first place - the source of most "mojibake" garbled-text bugs when the wrong one is assumed; binary-to-text encodings (Base64, Base32, Base58, Base85, Hex, Quoted-Printable) used throughout programming and data transfer; classical ciphers (ROT13, ROT47, Atbash, Bacon's Cipher) and historical codes (Morse Code, Baudot Code, Tap Code) that predate computing; and a few practical/novelty formats (NATO Phonetic Alphabet, Leetspeak, Reverse Text). Every format converts directly to every other - for example Hex to Morse - without needing plain text as a visible intermediate stop, though that's exactly what happens internally: your input is decoded down to plain text, then re-encoded into the target format.
What the Text Encoding Converter does
The Text Encoding Converter converts text directly between 30 formats: Base64, Base32, Base58, Base85, hex, binary, octal, URL and HTML entities, UTF-8, UTF-16 and UTF-32 bytes, Latin-1 and Windows-1252, plus ciphers and codes such as ROT13, Atbash, Morse, NATO and Braille.
Any format can go to any other, for example Base64 straight to hex, without a visible plain-text step in between. Internally the input is decoded to text first and then encoded again, so invalid input is reported instead of producing garbage.
When to use it
- Debugging garbled characters (mojibake) by looking at the actual UTF-8 or UTF-16 bytes of a string.
- Decoding a value that was Base64- or URL-encoded by another system; for single steps the Base64 Decoder and URL Decoder pages are quicker.
- Teaching or puzzles: Morse code, ROT13, the Atbash cipher or binary representations of letters.
- Encoding text for a URL, an HTML attribute or an email header where special characters must be escaped.
Worked example
Hi! · text → Base64
SGkh
Hi! · text → hex
486921
Hi! · text → binary
01001000 01101001 00100001
SGkh · Base64 → hex
486921
SOS · text → Morse
... --- ...
Hello · text → ROT13
Uryyb
Common questions about the Text Encoding Converter
What is the difference between UTF-8 and Latin-1?
UTF-8 can represent every Unicode character and uses one to four bytes per character. Latin-1 uses one byte and only covers Western European letters, so characters such as € or Hebrew letters cannot be represented.
Is ROT13 encryption?
No. ROT13, ROT47 and Atbash are simple letter substitutions that anyone can reverse instantly. Use them for spoilers or puzzles, never to protect data.
Why do binary results have spaces?
Each byte is shown as a group of eight bits separated by a space, which makes it easy to count bytes and spot characters that take more than one byte in UTF-8.
Is this tool free?
Yes, it's free to use. No signup, no email required. Get results on this page.
How do I get my result?
Use the tool on this page. Your result appears here; no email delivery is required.