URL Encoder + Parser
Percent-encode or decode strings, and inspect every part of a URL.
About the URL Encoder / Decoder + Parser
This tool does two jobs on one page. The top panel percent-encodes or decodes any string, so characters like spaces, ampersands, and slashes become safe to drop into a URL and back again. The bottom panel takes a full URL and breaks it into its parts, saving you the guesswork of hand-editing a query string or hunting a long link for one parameter.
Encoding uses the browser's encodeURIComponent, so a space becomes %20 and an ampersand becomes %26. Decoding reverses that; a broken percent sequence returns an invalid-encoding warning instead of failing silently. The parser runs the URL through the browser's own URL constructor, then lists protocol, origin, username, password, host, hostname, port, pathname, search, and hash, and splits every query parameter into its key and value.
Encoding, decoding, and query parsing all run in the page, so no account is required. Everything runs in your browser using built-in JavaScript, so the strings and URLs you paste never leave your machine and nothing is sent to a server. That matters when a URL carries a session token, an internal hostname, or a password. Paste, encode, copy the result with a single button, and move on to the next one.
How to use the URL Encoder / Decoder + Parser
- 1Type or paste text into the String box at the top of the page.
- 2Click Encode to percent-encode it, or Decode to turn percent codes back into readable characters.
- 3Read the Result box, then click Copy to send the output to your clipboard.
- 4Click Clear to empty both the input and result and start over.
- 5Paste a full URL into the URL Parser field lower down.
- 6Read the breakdown rows and the Query Parameters list as you type.
What you can use it for
Fix a broken query string
A tracking link stopped working after a raw ampersand landed in a parameter value. Encode that value, put it back into the URL, and the next parameter stops being cut off. Use the parser to confirm each key and value lands where you expect.
Read a redirect chain
An OAuth or login URL often carries a redirect_uri that is itself an encoded URL. Decode the string to read the nested destination, then paste the whole URL into the parser to see the parameters the provider passes along.
Audit a URL for leaks
Before pasting a link into a ticket or chat, run it through the parser. The username and password rows make it obvious if credentials sit in the authority part, and the query list shows every parameter you might share by accident.
Percent encoding and component escaping
Percent encoding replaces a character with a percent sign and the two-digit hexadecimal value of its bytes. A space is byte 0x20, so it becomes %20; non-ASCII characters are first turned into their UTF-8 bytes and each byte is encoded, which is why an accented letter can expand into several percent codes. That is how arbitrary text survives inside a URL.
The Encode button uses component encoding, which is stricter than encoding a whole URL. It escapes reserved characters like the slash, ampersand, and equals sign, because inside a single value those would be read as structure and split the value in the wrong place. So encode each name and value on its own, then join them with the raw & and = that give the query string its shape.
Frequently asked questions
Does anything I paste get uploaded?
No. Encoding, decoding, and parsing all run in your browser with built-in JavaScript functions. No string or URL is sent to a server, and the page makes no network request to do its work. The only thing that leaves the page is what you send to your clipboard with the Copy button.
What is the difference between Encode and Decode?
Encode turns unsafe characters into percent codes, so a space becomes %20 and a slash becomes %2F, making the text safe to place in a URL. Decode does the reverse. Use Encode when building a link, Decode when reading one.
Why did decoding show an invalid encoding warning?
Decoding only works on well-formed percent sequences. A percent sign must be followed by two hexadecimal digits, like %20. If the input has a lone % or a code like %ZZ, the browser cannot decode it and the tool shows an invalid percent encoding warning instead of garbled output.
Why does the parser say a URL is not valid?
The parser uses the browser's URL constructor, which needs a scheme. A bare host like example.com/page fails, but https://example.com/page parses. If you see the not-a-valid-URL message, add http:// or https:// first.
Does Encode escape every character in a URL?
No, and that is by design. It encodes a single component, not a whole URL, so characters that are legal inside a value get escaped while a few others are left alone. Encode individual pieces like one parameter value, then assemble them into the full URL.