Home/URL Encode / Decode
Encoding

URL Encode / Decode

URL encoding and decoding

Input
Plain text
Lines: 0Chars: 0
Output
URL Encoded
Lines: 0Chars: 0

Overview: URL Encode / Decode is a percent-encoding tool for URLs. It escapes any string with %HH hexadecimal notation per RFC 3986, so you can safely pass spaces, non-ASCII characters and special symbols inside URLs, and it decodes them back to plain text. Under the hood it uses the browser native encodeURIComponent and decodeURIComponent for maximum compatibility.

How to use: Step 1 — type or paste the text you want to encode on the left; it may be a full URL, query parameters, a path segment, or you can click "Sample" to load an example. Step 2 — the URL-encoded result appears on the right in real time; non-ASCII characters are turned into UTF-8 byte sequences and percent-escaped (for example a Chinese character becomes something like %E6%95%B0). Step 3 — to go the other way, paste an encoded string on the right and the decoded plain text appears on the left. Step 4 — use the buttons to copy the result or swap the input panel.

Typical scenarios: Back-end developers encode parameters when concatenating query strings so Chinese or special characters do not break parsing; front-end developers handle browser address bars, iframe src or window.open parameters; debugging REST APIs by turning encoded params back into readable form; processing encoded data in OAuth callback URLs or payment callbacks; adjusting query strings when analysing or forging HTTP requests.

Technical notes: The tool uses encodeURIComponent, which escapes reserved characters such as ! * ' ( ) ; : @ & = + $ , / ? # [ ]. Use encodeURI if you want to keep an entire URL structure intact. Encoding is UTF-8 based, so non-ASCII characters become multi-byte %XX sequences. Decoding an illegal sequence throws a URIError, so double-check the input if that happens.

Privacy: Encoding and decoding happen entirely in your browser. Sensitive data such as URLs, tokens or signed parameters is never uploaded, so it is safe to use in production debugging.

Frequently Asked Questions

How do I use URL Encode / Decode?
Step 2 — the URL-encoded result appears on the right in real time; non-ASCII characters are turned into UTF-8 byte sequences and percent-escaped (for example a Chinese character becomes something like %E6%95%B0 ). Step 3 — to go the other way, paste an encoded string on the right and the decoded plain text appears on…
What can URL Encode / Decode do?
Typical scenarios: Back-end developers encode parameters when concatenating query strings so Chinese or special characters do not break parsing; front-end developers handle browser address bars, iframe src or window.open parameters…
Is my data private when I use URL Encode / Decode?
Sensitive data such as URLs, tokens or signed parameters is never uploaded, so it is safe to use in production debugging. Sensitive data such as URLs, tokens or signed parameters is never uploaded, so it is safe to use in production debugging.
What technical details should I know about URL Encode / Decode?
Use encodeURI if you want to keep an entire URL structure intact. Encoding is UTF-8 based, so non-ASCII characters become multi-byte %XX sequences.