Percent-encode text for URLs, query strings and form data.
Escape characters that would otherwise break a URL. Choose component encoding for parameter values, full-URI encoding to keep a whole address usable, or form encoding.
Everything you enter stays in this browser tab. Nothing is sent to our servers, logged or stored.
This is one of the thingsEncoding Tooldoes — open it for everything else it supports.
Loading tool…
What Encoding Tool supports
Base64
Base64 encode
Base64 decode
URL
URL encode
URL decode
HTML
HTML entity encode
HTML entity decode
About URL Encoder
URLs allow only a limited set of characters, and several of those carry structural meaning. A question mark starts the query string, an ampersand separates parameters, a hash begins a fragment. When those characters appear inside a value rather than as structure, they have to be escaped or the URL is parsed wrongly.
Which mode you need depends on what you are encoding, and getting it wrong is the classic mistake: encoding a complete URL with component encoding destroys it, because the slashes and colons that give it structure get escaped along with everything else.
How to URL-encode text
1
Enter your text
The value, URL or query string you need to encode.
2
Choose the mode
Component for a parameter value, full URI for a whole address, form for classic form data.
3
Copy the result
Encoding happens as you type.
Frequently asked questions
What is the difference between component and full-URI encoding?
Component encoding escapes every reserved character including the slashes and colons that structure a URL — correct for a single parameter value, destructive for a whole address. Full-URI encoding leaves those structural characters intact.
Why is a space sometimes + and sometimes %20?
Both are valid in different contexts. The form-urlencoded format used by classic HTML forms encodes a space as +, while standard percent-encoding uses %20. In a URL path, %20 is the only correct option.
How are emoji and accented characters handled?
They are converted to UTF-8 bytes first, then each byte is percent-escaped. That is why a single emoji expands into several escape sequences, and it is the standard interoperable behaviour.
Does encoding protect my data?
No. Percent-encoding is a transport convention, entirely reversible and visible to anyone who sees the URL. It provides no confidentiality whatsoever.