URL encoder & decoder
Paste a full URL to see every part (protocol, host, path, query, hash), or paste any text to percent-encode or decode with encodeURIComponent / decodeURIComponent and the lighter encodeURI / decodeURI. Unicode and reserved characters (spaces, &, #, etc.) are handled in your browser only — nothing is uploaded.
Parse URL expects an absolute URL (e.g. https://…). For a single query value or path piece, use Encode component / Decode component.
Result
URL components
Query parameters (decoded keys & values)
| Name | Value |
|---|
Result ready. CloudyBot can open live pages, follow redirects, and capture the same host, path, and query fields on a schedule — so you are not manually rebuilding encoded links every day.
Try CloudyBot FreeFree plan · No credit card · 60-second setup
How percent-encoding works
URIs only allow a limited ASCII set unescaped. Everything else — spaces, emoji, accents, < — is written as % followed by two hex digits per UTF-8 byte. encodeURIComponent is the strictest common helper: it encodes ? # & = + and more, which is what you want for one value in a query string. encodeURI leaves delimiters like ? and # alone so a mostly-human-readable link stays parseable after encoding.
decodeURIComponent reverses that process and throws on invalid sequences (for example a lone % or invalid UTF-8). decodeURI is gentler on full strings. This tool surfaces the browser’s error message in red when decoding fails.
Parse URL uses the URL constructor: it needs an absolute URL with a scheme (usually https://). The query table lists every name/value pair your browser exposes through URLSearchParams, including duplicate keys.
Common use cases
- Build a safe query string — percent-encode a user-typed search term or address before appending it to
?q=. - Decode pasted tracking links — unwrap layers of encoding to read the real destination path and parameters.
- Debug OAuth and SSO — inspect
redirect_uri,state, andscopevalues without sending tokens to a third party. - Compare encodeURI vs encodeURIComponent — see which preserves
&between multiple query pairs. - Document API examples — turn Unicode examples into copy-pasteable ASCII-only URLs for curl or Postman.
- Normalize messy logs — decode path segments copied from reverse proxies or CDN access logs.
You just encoded or parsed a URL. CloudyBot can revisit that page for you.
Example: “Every hour, open our status dashboard, read the same query parameters you just parsed, and alert me if region is not us-east.” CloudyBot runs in the cloud with browser sessions, memory, and optional schedules.
Free plan · No credit card · 60-second setup
FAQ
encodeURI vs encodeURIComponent?
Use encodeURIComponent for one piece you are inserting into a query or path. Use encodeURI when you need to lightly encode an almost-correct full URL string without destroying ? and & structure.
Is data sent to CloudyBot?
No. All encoding, decoding, and URL parsing happen in JavaScript in your tab.
Why does decodeURIComponent throw on some input?
Percent sequences must be valid UTF-8 when decoded, and lone % characters are invalid. This page shows the browser error in red; try Decode URI or fix the string.
Does this tool fetch remote URLs?
No. It only parses or encodes the text you paste. Nothing is sent to CloudyBot servers for these actions.
What is CloudyBot?
CloudyBot is a hosted AI agent with a real cloud browser, file workspace, and schedules — with published plan caps. This encoder stays local; the product automates visiting URLs and extracting structured data.
Related tools
Try CloudyBot on the free plan
30 AI Tasks / month · 2 browser sessions (10 min) · 50 MB storage · 7-day chat history
Start free — no credit card