Online URL encoder and decoder with percent-encoding support for Chinese characters and special symbols
URL encoding (also known as percent-encoding) is a mechanism that converts non-ASCII characters, special characters, and reserved characters in URLs into %XX format. Since URLs can only contain ASCII characters, Chinese characters, spaces, &, ?, and other special characters must be encoded to be safely transmitted in URLs.
SEO optimization: handle non-English URLs and query parameters. API debugging: encode/decode request parameters. Frontend development: handle special characters in URLs. Web scraping: parse and construct URLs. Cross-border e-commerce: handle multilingual product links.
Select "Encode" or "Decode" mode, enter your text in the left input box, and the result will appear in real-time on the right. Click "Copy Result" to copy to clipboard. Click "Swap" to move the output to the input box for reverse operations.
URL encoding (percent-encoding) makes special characters safe for URL transmission, resulting in %XX format. Base64 converts binary data to printable ASCII characters, resulting in alphanumeric + / = format. They serve completely different purposes.
%20 is the standard URL encoding for spaces (RFC 3986). The + sign is the space representation in the application/x-www-form-urlencoded format, commonly used in query strings from form submissions. Both formats are used in different contexts.
encodeURI does not encode characters with special meaning in URLs (like : / ? # [ ] @), suitable for encoding complete URLs. encodeURIComponent encodes all special characters, suitable for encoding parameter values within URLs. This tool uses encodeURIComponent.
Google can correctly recognize and index non-English URLs, though they may appear as %XX encoded form in the browser address bar. For non-English websites, using native language URLs is SEO-friendly, but it's recommended to keep URLs concise and keyword-rich.
If decoding fails, it's usually because the input encoding format is incorrect. Check: 1) Are there incomplete %XX sequences? 2) Are there non-encoded characters mixed in? 3) Are the characters after % valid hexadecimal digits (0-9, A-F)?