URL Encoder & Decoder
Percent-encode and decode URLs and query parameters.
Opens the editor with the text on the left and its percent-encoded form on the right. Everything runs locally.
URL encoding — also called percent-encoding — replaces characters that are unsafe in a URL with a % followed by their hex code. Spaces become %20, & becomes %26, and so on. It is what keeps a query parameter from breaking the URL it lives in, and it is essential whenever JSON or free text is passed through a link.
When you need it
- Query parameters. A value with spaces,
&or=must be encoded or it will corrupt the query string. - JSON in a URL. Passing a small JSON blob as a parameter requires encoding the braces, quotes and commas.
- Redirect and callback URLs. A URL passed inside another URL has to be encoded so its own parameters do not leak out.
Encode and decode, both directions
Paste readable text to encode it, or paste an encoded string to decode it back. The sample above contains spaces, an ampersand and a comma — encode it to see how each becomes a safe percent-sequence, then decode it to get the original back. Both operations are exact inverses.
Component vs. full URL
This tool encodes a value the way encodeURIComponent() does — it escapes the reserved characters (&, =, ?, /) because you are usually encoding a single parameter value, not an entire URL. Decoding is the matching decodeURIComponent().
Runs in your browser
Encoding and decoding are local. Nothing is uploaded, so URLs and parameters containing tokens are safe to work with here.
Frequently asked questions
How do I URL-encode a string?
Paste the text into the editor and run URL encode. Every unsafe character is replaced with its percent-code, giving you a value safe to drop into a query string.
What is the difference between encoding a component and a whole URL?
Encoding a component (this tool) escapes reserved characters like & and = because you are encoding a single value. Encoding a full URL leaves those structural characters intact.
Is my data uploaded?
No. Encoding and decoding run entirely in your browser — nothing is sent to a server.
Related tools
Prefer to start from scratch? Open the JSON editor and paste your own data — everything runs locally in your browser.