URL Encoder
Percent-encode text or a full URL so it's safe to use in a query string, path segment or form field.
How URL encoding works
URL (percent) encoding replaces characters that aren't allowed or don't have a reserved meaning in a URL with a % followed by their hexadecimal byte value — for example, a space becomes %20 and & becomes %26. It lets you safely pack arbitrary text into a URL without it being misread as part of the URL's structure.
Component vs. Full URL
Component encoding (encodeURIComponent) escapes every character with special meaning in a URL, including / ? # &. Use it for a single value you're about to insert into a query string or path segment.
Full URL encoding (encodeURI) leaves characters that are structurally part of a URL — : / ? # [ ] @ — untouched, and only escapes things like spaces and unicode characters. Use it when you already have a complete URL and want to encode it without breaking it.
Frequently asked questions
Is my data sent to a server?+
No. Encoding happens entirely in your browser. Nothing you paste here is transmitted or stored.
What's the difference between Component and Full URL encoding?+
Component encoding escapes reserved characters like / ? & — use it for a single query parameter or path segment. Full URL encoding preserves a URL's structural characters and only escapes things like spaces — use it on a whole URL.
Why did my encoded text include %20 instead of a plus sign?+
%20 is the standard percent-encoding for a space. The + character is a form-encoding convention (application/x-www-form-urlencoded) used specifically in query strings — both are valid depending on context.
Related tools
URL Decoder
Decode percent-encoded URLs and text back to readable form.
URL Parser
SoonBreak a URL down into protocol, host, path, query and hash.
Query String Parser
SoonTurn a query string into a readable key/value table.