How to use
- Pick the tool you need from the sets above. It opens right below, and the part after
#in the address changes so you can share the same view. - Paste the text or code you want to convert. Each tool has a switch for the encode or decode direction, and starts with an example so you see a result right away.
- Copy the result with the copy button. To work in one tool alone, press “Open this tool on its own page”. Every tool also has its own page.
Which tool fits what you see
You can often guess the encoding from how a string looks.
| What it looks like | What it probably is | Tool |
|---|---|---|
SGVsbG8=: letters and digits, often ending in = |
Base64 | Base64 encoder and decoder |
A long text starting with data:image/png;base64, |
An image written as Base64 | Base64 to image |
%EC%84%9C, %20 |
URL percent encoding | URL encoder and decoder |
<, &, 한 |
HTML entities | HTML entity converter |
A domain starting with xn-- |
Punycode for an international domain | Punycode converter |
Text full of \n, \" and \\ |
JSON string escaping | JSON escape and unescape |
한, U+D55C |
Unicode code points | Unicode converter |
01001000 01101001 |
Text written in binary | Text to binary |
48 65 6C 6C 6F |
Hex bytes | Text to hex |
72 101 108 108 111 |
Decimal character codes | Text to decimal, Text to ASCII |
Starts with eyJ and has two dots |
A JWT | JWT decoder |
Dots and dashes like ... --- ... |
Morse code | Morse code translator |
Odd characters such as ë‚´ìš© or ÇÑ±Û |
Text read with the wrong encoding | Mojibake fixer |
Tools in this set
| Set | Tools | What they do |
|---|---|---|
| Base64 | Base64 encoder and decoder, Base64 to image | Exact UTF-8 handling of non-English text and emoji, the URL-safe form, and restoring an image from Base64 |
| URLs, web and strings | URL encoder and decoder, HTML entity converter, Punycode converter, JSON escape, Unicode converter | % encoding, entities like <, xn-- domains, \n escapes, code points and bytes |
| Text and number codes | Text to binary, hex, decimal and ASCII, number base converter | Turning characters into number codes and back, and converting between bases 2 to 36 |
| Tokens, signals and garbled text | JWT decoder, Morse code translator, mojibake fixer | Reading a token and its expiry, Morse code with sound, and restoring garbled text |
Encoding is not encryption
Base64, URL encoding and Unicode escapes only rewrite data in another notation. They do not keep anything secret. Anyone who knows the method can reverse them, and no key is needed. This is how a single character looks in several notations.
| Notation | How 한 looks |
|---|---|
| Unicode code point | U+D55C |
| HTML entity (hex) | 한 |
| HTML entity (decimal) | 한 |
| UTF-8 bytes (hex) | ED 95 9C |
| URL percent encoding | %ED%95%9C |
| Base64 (of the UTF-8 bytes) | 7ZWc |
All of these are the same character. What matters is whether the sender and the receiver follow the same rule. If one side writes UTF-8 and the other reads it with a different character table, the text turns into garbage. To hide a value you need encryption or a hash instead, so use the hash generator or AES encrypt and decrypt.
Frequently asked questions
Does Base64 encrypt my data?
No. Base64 writes bytes using 64 characters (letters, digits, + and /), and anyone can decode it. For example Hello becomes SGVsbG8=, and decoding gives Hello straight back. Storing a password or token as Base64 does not protect it.
What are the %EC%84%9C characters in a web address?
It is URL encoding: a character such as a Korean letter is turned into UTF-8 bytes, and each byte is written as % plus two hex digits. 한 becomes %ED%95%9C. Choose decode in the URL tool to get the original characters back. Encoding a whole address and encoding a single query value are handled differently, and the tool lets you pick the scope.
Is the content of a JWT secret?
No. The first two parts of a JWT are JSON encoded with a Base64 variant (base64url), so anyone holding the token can read them. The JWT decoder shows the contents but does not verify the signature. Never put sensitive data such as passwords in a JWT.
Why does my text show 한 instead of the letters?
A JSON or JavaScript string has written the characters as Unicode escapes. Decode them in the Unicode converter or in JSON escape and unescape to see the letters. To go the other way, turning letters into escaped codes, use the same tools.
My text turned into ë‚´ìš©. Can it be restored?
If text saved as UTF-8 was read with a different character table, yes. Paste it into the mojibake fixer and it tries likely combinations and lists candidates for the original. Text that has already become ? or � has lost the information, so it cannot be restored from the text alone.
Why are there several binary and hex converters?
Tools that turn characters into number codes (text to binary, hex, decimal and ASCII) do a different job from the tool that rewrites a number in another base (the number base converter). For example the character A is hex 41, binary 01000001 and decimal 65 as a UTF-8 byte. The number 255, on the other hand, is FF in hex and 11111111 in binary.
Is what I type sent to a server?
No. Every tool in this set converts what you enter inside your browser only, and nothing is sent or stored.
Related tools
To make a hash that cannot be reversed use the hash generator, for message authentication codes the HMAC generator, and to encrypt and decrypt with a key AES encrypt and decrypt. To change the character encoding of a whole file use text encoding converter, and to turn an image file into Base64 use image to Base64.
What you enter is processed only in your browser and never sent to a server.