Why URLs need encoding
URLs can only safely contain a limited set of characters — spaces, ampersands, question marks and other symbols have special meaning in a URL or break it outright, so they need to be "percent-encoded" (like %20 for a space) before being placed in a query string or path. This tool uses JavaScript's encodeURIComponent and decodeURIComponent, which correctly handle Unicode text as well as plain ASCII — useful when building links, debugging query parameters, or working with redirect URLs that have been encoded once (or sometimes twice) already.
About this tool
This tool encodes text into URL-safe format (percent-encoding) or decodes an already-encoded URL back into readable text — useful for building query strings, debugging a broken link, or understanding what a long encoded URL actually says.
How to use it
- Type or paste your text or URL into the input box.
- Choose "Encode" to make it URL-safe, or "Decode" to convert it back to readable text.
- Click "Copy" to copy the result.
Frequently asked questions
What characters get encoded?
Characters that aren't safe in a URL — like spaces, &, ?, # and non-ASCII characters — get converted to their percent-encoded equivalent (a space becomes %20, for example).
What happens if I decode text that isn't actually encoded?
Plain text with no percent-encoded sequences decodes to itself unchanged, so it's safe to try decoding something if you're not sure whether it's encoded.
Is my data uploaded anywhere?
No — encoding and decoding happen entirely in your browser; your text is never sent to a server.