Encode and decode URLs with component and full-address modes, including Unicode.
Escapes every reserved character. Use for a single value such as a query parameter.
This tool runs directly in your browser. The content you enter is processed locally and is not sent to TechFixGen servers. No account or signup is required.
URL encoding — also called percent encoding — rewrites text so it can travel safely inside a URL. Characters that are not allowed in a URL, or that have special meaning such as ?, &, and =, are replaced by a % followed by two hexadecimal digits that identify the UTF-8 byte.
For example, a space becomes %20, and the letter A stays as A because it is already safe.
Encoding converts readable text into its percent-encoded form, usually before it is placed in a URL. Decoding reverses the process, turning %20 back into a space so you can read the original value. This tool is bidirectional: choose a mode, paste your text, and the result appears instantly.
Browsers expose two related functions, and this tool exposes both:
encodeURIComponent / decodeURIComponent. It escapes every reserved character, which is what you want for a single query-parameter value.encodeURI / decodeURI. It leaves the delimiters : / ? # & = untouched so a complete address still works.A common mistake is encoding a whole URL with component mode, which destroys the structure by escaping its slashes and query separators.
hello world
hello%20world
A space becomes %20 (or + in form bodies).
name=Ada & city=London
name%3DAda%20%26%20city%3DLondon
& and = are reserved, so component mode escapes them.
price=10€
price%3D10%E2%82%AC
€ is a multi-byte UTF-8 character: %E2%82%AC.
search?q=a/b
search%3Fq%3Da%2Fb
? and / are escaped in component mode, kept in full-URL mode.
Spaces are not valid in a URL, so they are encoded as %20. In HTML form submissions a space may instead appear as +, which is a form-encoding convention rather than standard percent encoding — this tool uses %20.
Each percent escape is exactly three characters: % plus two hexadecimal digits. The digits are the byte value, so byte 0x20 (32) is a space and becomes %20. Text that uses multiple bytes — accented letters, other scripts, and emoji — produces several escapes in a row.
Percent encoding works on UTF-8 bytes. A character such as é is two bytes and encodes to %C3%A9, while an emoji such as 🚀 is four bytes and encodes to %F0%9F%9A%80. Decoding those escapes reconstructs the original character.
Encoding and decoding run locally in your browser. The text you enter is not uploaded to TechFixGen servers and is not included in analytics events. No account or signup is required. Working with Base64 instead? See the Base64 Encoder & Decoder.
%20 is a percent-encoded space. The digits 20 are the hexadecimal value of the space byte (32 in decimal). Decoding %20 turns it back into a space.
Raw spaces are not allowed in a URL. Encoding a space as %20 keeps the address valid and unambiguous. HTML forms sometimes use + instead, which is a separate form-encoding convention.
Usually not. Use Full URL mode (encodeURI) when the string is a complete address so its : / ? # & = delimiters survive. Use Component mode (encodeURIComponent) for a single value, such as one query-parameter value.
Percent encoding represents a byte as a percent sign followed by two hexadecimal digits. It is how URLs carry characters that are otherwise reserved or not permitted, and it operates on UTF-8 bytes.
Yes. If the input contains an incomplete or invalid percent escape, such as a lone %, %2, or a byte sequence that is not valid UTF-8, decoding cannot succeed. The tool reports a clear error and, when it can identify the position, points to the offending character.
No. Encoding and decoding happen entirely in your browser. Your input and output are not uploaded to TechFixGen servers and are not included in analytics events.