URL Encoder / Decoder
Percent-encode or decode text and break a URL into editable query parameters.
URL parser
About this tool
Two jobs in one page. The encoder turns text into its percent-encoded form and back: component mode escapes everything (right for a single query value), full-URL mode keeps the structure characters so a whole address stays clickable. The parser breaks a URL into scheme, host, port, path and fragment, and lays the query string out as a decoded table you can edit. Change a value, delete a row or add one, and the rebuilt URL updates with correct encoding as you type.
Handy when a link arrives wrapped in three layers of tracking parameters, or when a value containing & or = needs to go into a query string without breaking it. Everything runs in your browser with the standard URL API; the address you paste is never fetched or sent anywhere, which matters because real URLs often carry tokens and session ids.
Frequently asked questions
- What is the difference between encoding a component and a full URL?
- Component encoding escapes every reserved character (so "a&b" becomes "a%26b") and is what you want for a single query value. Full-URL encoding keeps the structural characters like :, /, ? and & intact so the URL still works.
- Is the URL I paste sent anywhere or previewed?
- No. Parsing happens in your browser with the standard URL API. Nothing is fetched, previewed or logged, which matters because real URLs often carry session tokens.
- Why do spaces show up as %20 or + in URLs?
- Percent encoding uses %20 for a space. The older form-submission format uses + inside query strings. The parser here understands both, and re-encodes edited values with %20.