URL Encode and Decode
Enjoying this tool?
Part of Code formatters
URL encode and decode: percent-encoding for query strings and paths
URL encoding (percent-encoding) replaces reserved and non-ASCII characters with `%` hex sequences so URLs and query parameters parse correctly. Decoding reverses the process when you inherit an over-encoded link from analytics or a legacy CMS.
Use encode before building query strings manually; use decode when reading logged URLs or debugging redirect chains.
How to use this converter
- Paste the text or full URL fragment to encode or decode.
- Choose Encode for spaces, `&`, `=`, Unicode, and symbols—or Decode to read percent sequences.
- Copy the result into your router, fetch call, or documentation.
Before and after examples
| Original | Converted | Notes |
|---|---|---|
| hello world | hello%20world | Space in query value |
| caf%C3%A9 | café | UTF-8 decode |
Component encoding vs full URI encoding
Encoding a query value (`hello world` → `hello%20world`) differs from encoding an entire URL where some characters (`:`, `/`, `?`) must stay unescaped in specific positions. This tool applies standard encodeURIComponent-style rules to the pasted text—if you encode a full URL, reserved characters in the scheme and path may be encoded too. Encode only the parameter value when building `?q=` links.
Plus signs, spaces, and form data
HTML form submissions historically used `+` for spaces in `application/x-www-form-urlencoded` bodies. URLs in the address bar use `%20`. If decode output shows unexpected `+`, check whether the source was form-encoded rather than URI-encoded.
Slugs, analytics, and SEO
Marketing URLs with UTM parameters should encode campaign names with spaces or special characters. For public slugs, prefer kebab-case lowercase paths instead of percent-encoded phrases—use the kebab-case converter when naming new routes.
Frequently asked questions
Should I encode the entire URL?
Usually encode only parameter values. Encoding `https://` breaks the scheme unless you intend to wrap the whole string.
Why is `%20` different from `+`?
Both can represent spaces in different contexts. URI query strings in browsers typically use `%20`.
Does encoding improve SEO?
Readable lowercase slugs beat encoded phrases. Encode only when characters are not URL-safe.