URL Encode / Decode Text

When and why to URL-encode

Every character outside the "safe" set (letters, digits and a few symbols like - _ . ~) is converted to "%" followed by its byte in hexadecimal, for example, a space becomes "%20" and "á" becomes "%C3%A1" (two UTF-8 bytes). This encoder works in "URL component" mode, the same one used for query string values, so it also escapes "/", "?", "&" and "=".
When decoding, "+" is also treated as a space, a behavior inherited from the "application/x-www-form-urlencoded" format used by HTML forms, useful when pasting query parameters copied from a real URL.

Examples

Encode

Input: nome completo
Expected output: nome%20completo

Space becomes %20.

Decode

Input: jo%C3%A3o
Expected output: joão

UTF-8 handled correctly.

Full tool FAQ

How do I convert text to binary?

Select the Binary format, keep the direction on Text → Code and type your text. Each character becomes an 8-bit group (for example, 'A' becomes 01000001), separated by spaces. For the reverse, paste the binary and switch the direction to Code → Text, it works with space-separated groups or with one continuous run of bits.

How does text become hexadecimal?

Does decoded morse code come back in uppercase or lowercase?

What's the difference between Base64, Base32 and Base58?

What is URL percent-encoding?

What are HTML entities and when should I use them?

Are ROT13 and ROT47 safe for hiding information?

What is the NATO phonetic alphabet?

Why doesn't decoding leetspeak always return the original text?

Does the text I type ever leave my browser?

Frequently asked questions

Why do spaces in a URL become "%20"?

A space isn't an allowed character in URLs. "%20" is the percent-encoded form of a space (byte 0x20 in hex), ensuring the URL doesn't break when interpreted by browsers and servers.

What's the difference between encoding a component and a whole URL?

Encoding a component (what this tool does) escapes ALL special characters, including "/" and "?", correct for an isolated value, like a parameter. Encoding a whole URL would preserve those characters, since they're part of the URL's structure.

Why does "+" become a space when decoding?

It's a convention inherited from HTML forms (application/x-www-form-urlencoded), where "+" represents a space instead of "%20". This decoder handles both formats to cover query strings and form data alike.

Text & Code Translator

Continue in the tool

More pages for this tool