Runs locally in your browser. Nothing you enter is uploaded to our servers.
Tips for text encodings
Base64 and Hex encode bytes — UTF-8 text is assumed when converting to readable text.
URL decoding treats + as a space (form-style), same as many query parsers.
Unicode mode supports \uXXXX, \xNN, and \u{…} code points.
If decode fails, check that the selected encoding matches the input format.
Several text encodings in one place
Processing stays in your browser — your input is not uploaded to our servers.
A codec panel switches between encodings you meet in APIs and logs — Base64, URL, hex — without hopping across three tabs.
Always know which encoding the producer used. Guessing hex versus Base64 is how tokens get corrupted.
Encode or decode text
Pick the encoding
Match the format in the spec or the `Content-Transfer-Encoding` you actually have.
Paste the source
Keep the original alphabet. Do not prettify hex with extra spaces unless the tool strips them.
Copy the result
Round-trip once to confirm you chose the right variant.
Text codec FAQ
Which encoding should I use?
Whatever the other side already speaks. This page does not invent a wire format for you.
Is Unicode handled?
Text is treated as UTF-8 bytes before binary encodings. That matches most modern APIs.
Does any variant leave the browser?
No. Codecs run locally.