URL Encode / Decode
Encode text into a percent-encoded URL string, or decode one back to plain text. Everything runs in your browser, so your input never leaves your machine.
encodeURIComponent and decodeURIComponent (and encodeURI/decodeURI in full URL mode). Nothing is uploaded or logged.About the URL Encode / Decode
The URL Encode / Decode tool converts text and URLs to and from percent-encoding. Encode turns characters that are unsafe in a URL (spaces, accented letters, &, ?, and others) into %XX escape sequences; Decode reverses that back to readable text. It is built for developers, WordPress and API integrators, and anyone debugging query strings, redirect parameters, or links. Everything runs in your browser using the native encodeURIComponent, decodeURIComponent, encodeURI, and decodeURI functions, so your input stays private and is never uploaded.
How it works
- Pick Encode or Decode with the mode toggle.
- Type or paste your text into the input box; the result updates on the right as you type.
- If you are working with a whole URL and want to keep structural characters like :/?#& intact, turn on Full URL mode (encodeURI / decodeURI).
- Click Copy to grab the output, or Clear to start over.
Features
- Encode and decode in one panel with a single mode toggle.
- Component mode (encodeURIComponent / decodeURIComponent) for query values and path segments.
- Full URL mode (encodeURI / decodeURI) that preserves URL structural characters.
- Inline error message when a string has malformed percent-encoding that cannot be decoded.
- Live character counts and one-click copy.
Frequently asked questions
Is my text sent to a server?
No. Encoding and decoding run entirely in your browser using its built-in URL functions. Nothing is uploaded or logged.
When should I use Full URL mode instead of the default?
Use the default (component) mode for a single value, such as a query parameter or a path segment, because it encodes characters like &, ?, /, and = as well. Use Full URL mode when you have an entire URL and want to keep those structural characters readable while still escaping spaces and other unsafe characters.
Why does decoding show an error?
Decoding fails when the input has an invalid percent sequence, for example a % that is not followed by two hexadecimal digits, or bytes that are not valid UTF-8. Fix or remove the broken sequence and try again.
How are spaces handled?
Both encode modes turn a space into %20. Note that the older + sign for spaces (used in form submissions) is not produced or decoded here; this tool follows the percent-encoding rules of the native URL functions.
Does it work offline?
Once the page has loaded, the tool runs locally in your browser, so it keeps working without an active connection.