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?
URLs accept only a narrow alphabet, so spaces, quotes, ampersands, question marks and non-ASCII letters must be percent-encoded before travel, or links break or misroute. The classic mistake is scope: encoding a whole URL when one value needed it mangles structural colons and slashes, while encoding too little leaves a raw space that snaps the link. This tool handles both scopes — component mode for single values, full-URL mode preserving structure — in both directions, plus a live query inspector splitting any pasted URL at its question mark and hash into a decoded parameter table, honoring the plus-means-space form convention in values.
Component scope versus full-URL scope
- 🔗 Component mode encodes everything unsafe, built for one value or segment
- 🌐 Full-URL mode keeps structural characters intact across the whole link
- 🔄 Matching decode in either mode restores the readable original
- 📋 Live parameter table with decoded keys and values plus an empty state
- ⚡ Explicit encode and decode buttons with clear and copy
Link bugs it helps you catch
- Embedding user-typed terms safely inside generated links
- Auditing tracking URLs to see which parameters a campaign carries
- Tracing why a copied link 404s or drops half its query string
Heed the lesson the tool teaches: full-URL mode suits an entire link but corrupts a lone value, so match the mode to your selection before encoding. All conversion runs in your browser with no network calls — private URLs, tokens and session links are never uploaded or logged.
Last updated · 2026-09-01
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.