URL Encode Converter
Percent-encode text for safe use in URLs.
Text
Encoded
About the URL Encode converter
URLs may only contain a limited set of characters. Everything else — spaces, ampersands, accents, emoji — has to be percent-encoded, written as a `%` followed by the hexadecimal value of each UTF-8 byte.
Which characters need escaping depends on where in the URL the text is going, so this tool offers the three encodings that actually differ.
Component, URI or form?
Component encoding escapes everything that is not unreserved, including `:`, `/`, `?`, `&` and `=`. Use it for a single query parameter value or a path segment — this is the right default and the one people usually want.
Full-URI encoding leaves the structural characters alone, so an entire address stays usable. Use it when you have a complete URL containing a space or a non-ASCII character.
Form encoding matches `application/x-www-form-urlencoded`, where a space becomes `+` rather than `%20`. Use it only when building a form body by hand.
Double encoding
Encoding an already-encoded string turns `%20` into `%2520`, and the result looks fine until something downstream decodes it once and gets the literal text `%20`. If your input already contains percent signs followed by hex pairs, decode first.
Frequently asked questions
Why is my ampersand still there?
You are probably in full-URI mode, where & is structural and left alone. Switch to component encoding to escape it.
How are emoji encoded?
As their UTF-8 bytes, so one emoji typically becomes four percent escapes. That is correct and every modern server decodes it.