Encoding and decoding: Base64, URL, Unicode, HTML and Hex

Text encoding changes how characters or bytes are represented. Use the encoding expected by the receiving protocol instead of applying several encodings at random. The tool supports Unicode, Base64, Base64URL, URL component, URI, form values, HTML, JSON strings and UTF-8 Hex.

Open this tool →

How to use the tool

Choose the encoding mode and select Encode or Decode.
Paste or import text; the example button provides input appropriate for the selected mode.
Run conversion and inspect the result as text. HTML input is not executed.
Copy or download the output. If decoding fails, check the format and the expected text encoding before retrying.

An example to test

Text: hello
Base64: aGVsbG8=

URL component input: a+b c
URL component output: a%2Bb%20c
Form URL output: a%2Bb+c

Base64 and UTF-8

Base64 is encoding, not encryption. Base64URL uses URL-safe characters and omits padding on export. Decoding a JWT segment does not verify its signature. This tool decodes bytes into UTF-8 text and is not a binary-file decoder.

URL values, complete URLs and JSON strings

Use URL component for one parameter value, URI for a complete URL and Form URL for a form value. Form encoding uses + for spaces, while URL component decoding keeps a literal +. JSON encoding returns a quoted string; decoding expects a string literal rather than a JSON object or array.

Frequently asked questions

Why does decoded text contain unexpected characters?

Check that the bytes are UTF-8 and that the source is text rather than a binary file. The tool rejects invalid UTF-8 instead of silently substituting characters.

Can Base64 hide a password?

No. Anyone can decode it. Password protection requires an appropriate security design rather than reversible text encoding.