Paste text, URLs, or parameter strings into the input box and click a button to URL encode or decode. Supports non-ASCII characters and special symbols, perfect for API debugging, redirects, and log analysis.
URL encoding converts special characters into %XX sequences so they can be safely transmitted over the web. Spaces may appear as %20 or +, and non-ASCII text becomes percent-encoded bytes. URL decoding reverses this process. This tool performs both instantly in the browser with no installation.
When working with callback URLs, third‑party login redirects, GET query strings, or short links, you should encode parameters first to prevent & ? = from breaking the structure. If you receive an already encoded string like state=%7B%22from%22%3A%22tools%2Ebzxz%2Enet%22%7D, paste it here and click “URL Decode” to restore readable JSON or text.
Compared with writing scripts or using browser consoles with encodeURIComponent/decodeURIComponent, this tool is more direct: input on the left, output on the right, and a one‑click swap for repeated experiments. It is handy for developers, operators, and site owners who handle parameters daily.
tools.bzxz.net is a multilingual toolkit with timestamp conversion, UUID generation, JSON utilities, and text formatting. The URL encode/decode tool works with these features to form a complete browser‑based toolbox for common data conversions.
URL encoding handles reserved and non-ASCII characters in URLs, such as spaces, Chinese, & and ?. Base64 is a general binary‑to‑text encoding often used for files and images. They are not interchangeable.
When parameters contain spaces, non-ASCII text, #, &, ?, =, or other special characters, you should encode them before appending to a URL to prevent mis-parsing or data loss.
In application/x-www-form-urlencoded, spaces are encoded as +. In strict URL encoding, %20 is preferred. This tool treats + as a space when decoding for compatibility.
It typically means the string is not valid URL encoding, such as an incomplete sequence or illegal %XY fragment. Check for truncation or decode only a valid segment.
Yes, but usually only the parameter values need encoding. Encoding the whole URL can create double‑escaping and unexpected results in browsers or servers.
No. It only represents the same data in a different form. Decoding restores the original content exactly.
No. All encoding and decoding runs locally in your browser. Your input is not sent to the server.
URL encoding assumes UTF‑8 by default. If the original text used another encoding like GBK, decoding in UTF‑8 can produce garbled characters. Use UTF‑8 consistently when generating URLs.
It is useful for API developers, mobile and H5 redirects, third‑party login callbacks, short link debugging, marketing parameter checks, and customer support troubleshooting.
No APIs to remember—just paste and click. Swap input/output and test multiple variants quickly without writing code.
When a URL contains spaces, non-ASCII text, or special characters, browsers and servers use URL encoding. This tool helps you view the encoded form or decode strings like %E4%B8%AD%E6%96%87 back into readable text.
Scan the QR code to open this page on your phone for quick URL encoding and decoding.