URL Encoder
Encode/decode URL components or full URLs, plus a query-string parser
Encodes everything, including / ? & = — use this for a single value (query parameter, path segment).
| Parameter | Value |
|---|
Two URL encoders, two different jobs
Component or whole URL
Encode a single query parameter value with strict percent-encoding, or switch modes to keep the colons, slashes, question marks and ampersands of a full URL intact.
Query strings, parsed
Paste any link with a query string and its parameters appear in a table — names, decoded values and plus signs turned back into spaces — refreshed as you edit.
Both halves of the job
The same box encodes a value before it goes into a form and decodes a tracking link to see what it actually sends, with the result copied straight off the output pane.
What Is a URL Encoder?
A URL may only contain a limited set of characters. Spaces, quotes, non-ASCII letters and symbols such as & and ? must be percent-encoded before they travel in a URL, or the link breaks or sends the wrong request. Encoding by hand is fiddly, and getting the scope wrong — encoding a full URL when you meant one component, or vice versa — is a classic bug. This tool encodes and decodes both ways, and parses any query string into a readable table, so you can see exactly what a tracking link or form submission is carrying. The same tool therefore covers both halves of the workflow: preparing a value for a link, and decoding a link someone sent you.
What it encodes and decodes
- 🔗 Component mode: percent-encode a query value or path segment
- 🌐 Full-URL mode: encode while keeping : / ? & = structural characters intact
- 🔄 Decode either mode back to readable text
- 📋 Query-string parser: paste a URL, see its parameters as a table
- ⚡ Handles the plus-as-space convention in query values
Where encoding trips people up
- Building links that carry user-entered search terms safely
- Debugging why a copied link 404s or drops its parameters
- Decoding tracking URLs to read the UTM values
- Preparing values for an API call or redirect
The conversion happens entirely in your browser — URLs and parameters are never uploaded. Note that full-URL encoding keeps URL structure intact by design, which is correct for an entire link but wrong for a single parameter value; component mode exists for that case.
encodeURIComponent versus encodeURI
- Component encoding escapes reserved characters (?, &, =, /) — right for query values.
- Full-URL encoding preserves them so a link stays a link — right for a whole address.
- Spaces become %20 either way; + means space only inside form-encoded bodies — legacy of application/x-www-form-urlencoded.
Frequently asked questions
What's the difference between Component and Full URL mode?⌄
Component mode (encodeURIComponent) escapes every special character, including / ? & = — correct for a single query value. Full URL mode (encodeURI) leaves URL-structural characters like : / ? & # alone, so it's for encoding an entire URL without breaking it.
Why does the query-string parser show + as a space?⌄
In the application/x-www-form-urlencoded convention used by query strings and form submissions, + represents a space (as an alternative to %20) — the parser follows that convention.
Is my text uploaded anywhere?⌄
Percent-encoding is computed in your browser with JavaScript, so even URLs containing tokens or internal hostnames never leave your machine.