What encoding is used?

Standard percent-encoding (encodeURIComponent / decodeURIComponent) as used in URLs and query strings.

Why does decode fail?

Invalid percent-encoded sequences (e.g. %ZZ) or truncated input can cause decode errors.

Runs in browser

Encode and decode URL percent encoding instantly in the browser.

Encode text for use in URLs or decode URL-encoded strings. Handles special characters and spaces. All processing runs in your browser.

Auto-detect encoded textEncode query params separately (URLs)

Text to encode

Encoded

https%3A%2F%2Ftooldock.org%2Ftools%3Fsearch%3Djson%20formatter%26category%3Ddata%26sort%3Dpopular

🔒 Runs in your browser · No uploads · Your data never leaves your device

Choose mode
Switch between Encode (text → percent-encoded) and Decode (percent-encoded → text).
Enter input
Type or paste your text or encoded string.
Copy result
Use the Copy button to copy the encoded or decoded output.

Encoding query parameters — Encode special characters in query string values before appending them to URLs in API requests or scripts.
Decoding URL-encoded form data — Decode application/x-www-form-urlencoded POST bodies to read the original values.
Fixing broken URLs — Decode percent-encoded URLs from logs or error messages to identify the original request path or parameters.

What encoding is used?: Standard percent-encoding (encodeURIComponent / decodeURIComponent) as used in URLs and query strings.
Why does decode fail?: Invalid percent-encoded sequences (e.g. %ZZ) or truncated input can cause decode errors.

Percent encoding: URL encoding that replaces unsafe characters with a % followed by their hex code (e.g. space → %20).
Query string: The part of a URL after ? that contains key=value pairs, where special characters must be percent-encoded.

You might find these useful too.