URL Decoder
Decode %20 and other percent escapes back into normal characters.
Percent-encode text so it can travel safely inside a URL.
URLs may only contain a limited set of characters. Anything else, including spaces, ampersands, question marks and every non-English letter, has to be written as a percent sign followed by two hexadecimal digits. URL Encoder does that conversion for you and shows the result ready to paste.
Two modes are offered because the right answer depends on where the text is going. Component mode escapes everything that is not safe inside a single query value, including ampersands, equals signs and slashes. This is what you want when encoding one parameter. Full URL mode leaves the structural characters of a URL alone so that an entire address stays usable while its spaces and accented characters are escaped.
Picking the wrong mode is the usual cause of broken links. Encoding a complete URL in component mode turns every slash into %2F and produces an address that no longer works; encoding a single value in full-URL mode leaves ampersands intact and lets a value split into two parameters.
The url encoder is used by writers, developers, students, marketers and anyone else who needs the job done once without installing software. Common cases include:
Use component mode whenever you are encoding one value that will sit inside a parameter, such as a search term or a redirect target. Use full URL mode only when you want to tidy a complete address while keeping its slashes, question mark and ampersands working.
Percent-twenty is the standard encoding for a space in a URL path or query. The plus sign comes from HTML form submission, where it has historically meant a space. Both appear in the wild, which is why the plus option is offered.
No. Letters, digits, hyphen, underscore, full stop and tilde are always safe in a URL and are never escaped by either mode.
They are converted to UTF-8 bytes first and each byte is written as a percent escape. That is why one accented letter often becomes two percent sequences.
No. Encoding only ensures the characters survive transport. It provides no protection and no secrecy; a value in a URL can be read by anyone who sees the address.
Encode each value separately in component mode, then join them with ampersands and equals signs yourself. Encoding the whole string at once would escape the separators and break it.
If the url encoder is not quite what you need, these other free tools solve closely related problems.
Decode %20 and other percent escapes back into normal characters.
Split a URL into every component, including a table of query parameters.
Encode any text, including emoji and accents, to a Base64 string.
Convert a headline into a lowercase, hyphenated URL slug ready for publishing.
Escape angle brackets and quotes to HTML entities, or decode them back.