URL Encoder / Decoder
A URL Encoder/Decoder converts text to and from percent-encoded form (also called URL encoding), making strings safe to use inside query parameters, fragments, and path segments — all processed locally in your browser.
Output appears here…About URL Encoder / Decoder
Choose component or full-URI mode. Component mode uses encodeURIComponent / decodeURIComponent, which encodes characters like '&', '=', and '/' that have special meaning in URLs — appropriate for individual query values. Full-URI mode uses encodeURI / decodeURI, which preserves URL structure. The tool runs on the Web platform's native URL primitives.
What URL Encoder / Decoder does
- Encode and decode URL components with encodeURIComponent / decodeURIComponent
- Full-URI mode using encodeURI / decodeURI that preserves URL structure
- Toggle between '+' (form-urlencoded) and '%20' encoding for spaces
- Side-by-side panes with live output
- Built on the platform's native URL primitives — no library round-trip
When to reach for URL Encoder / Decoder
- Encoding a search query before stitching it into a URL
- Decoding a tracking parameter to see the actual value
- Spotting double-encoded values that need a second decode pass
- Building a deep link with reserved characters in the query string
How to use URL Encoder / Decoder
- 01
Paste your text
Paste into the encode pane for raw text, or the decode pane for a percent-encoded string.
- 02
Pick the mode
Component mode escapes every reserved character. Full-URI mode preserves URL structure.
- 03
Copy the result
Click Copy on either pane to put the value on your clipboard.
When to use URL Encoder / Decoder vs alternatives
| Alternative | Use URL Encoder / Decoder when… | Use the alternative when… |
|---|---|---|
| encodeURIComponent in a browser console | you want a UI with mode toggle and decode round-trip without opening DevTools. | you are already scripting and want the raw primitive. |
Frequently asked questions
When should I use encodeURI vs encodeURIComponent?
Why does '+' decode to a space sometimes?
Is URL encoding the same as Base64?
Related tools
Related reading
Engineering · 11 min read
Most punycode converters disagree with your browser. We measured it.
Punycode is only the last step of turning a Unicode domain into an xn-- label, and tools that stop there return a different domain than your address bar does. We tested a bare RFC 3492 implementation against the browser's own IDNA on seventeen realistic names: six came back wrong. Then we measured our own against ICU across 1,112,042 code points.
Comparisons · 6 min read
CyberChef alternatives: focused in-browser tools for everyday encoding
CyberChef is a powerful, fully client-side Swiss Army knife — but for a single common task like decoding Base64 or inspecting a JWT, its 300-operation recipe interface is overkill. Here's an honest look at focused, single-purpose alternatives that are just as private and faster for the everyday jobs, plus when CyberChef is still the right tool.