← All tools

URL Encode / Decode

About URL encoding utilities
URLs reserve certain characters for structure (for example ?, &, #, and spaces). When you pass arbitrary text inside query parameters or path segments, you must percent-encode it so servers and browsers interpret your intent correctly. This page helps you encode or decode those sequences and inspect full URLs.
The Parse URL action uses the WHATWG URL parser built into modern browsers, so you get the same decomposition you would expect in JavaScript fetch logs—ideal when debugging OAuth callbacks or misbehaving redirects.
When developers reach for this tool
  • Encoding user-supplied keywords before appending them to analytics or search endpoints.
  • Decoding a copied curl command’s query string to understand each parameter.
  • Breaking down production URLs to compare hostnames, paths, and hash fragments.
How to use this page
  1. Paste the raw string you need to transform into the editor.
  2. Choose Encode for encodeURIComponent semantics (UTF-8 percent encoding).
  3. Choose Decode when you already have percent-encoded text.
  4. Use Parse URL only when the input is a full absolute URL (including scheme).
  5. Swap input/output when you want to chain decode → inspect → re-encode manually.
Privacy
All transformations execute locally. Your URLs may describe sensitive environments—clear the textarea afterward on shared laptops.
Frequently asked questions
Does encodeURIComponent match RFC 3986?
It follows the ECMAScript standard used by browsers, which is what most web stacks implement for component encoding.
Why does parsing fail?
The parser expects a valid absolute URL (for example https://example.com/path). Relative paths need a base URL in other APIs.
Can I encode an entire URL?
Usually you encode components, not the whole string, or you risk encoding the delimiters that give the URL structure.
Does this send my URL to a server?
No. Parsing and encoding happen entirely in your browser tab.