If this tool helped you, you can buy us a coffee ☕
Process special character escaping and unescaping for HTML, URL, and JS formats. Perfect for web development and data processing tasks.
tools.escape.results.emptyMessage
URL to JSON Parser
Parse URL strings into structured JSON to quickly extract key information like protocols, parameters, and paths.
JSON Formatter
Process JSON data online: format, minify, and validate to boost your development and debugging efficiency.
Code Compare
Professionally compare differences between two texts or code snippets. Highlights additions, deletions, and modifications to assist with code review, document merging, and version control.
Escape Encoder & Decoder
Free online tool for Escape encoding and decoding strings, making URL parameter passing and data processing easier.
URL to JSON Parser
Parse URL strings into structured JSON to quickly extract key information like protocols, parameters, and paths.
JSON Formatter
Process JSON data online: format, minify, and validate to boost your development and debugging efficiency.
Code Compare
Professionally compare differences between two texts or code snippets. Highlights additions, deletions, and modifications to assist with code review, document merging, and version control.
Escape Encoder & Decoder
Free online tool for Escape encoding and decoding strings, making URL parameter passing and data processing easier.
PYC Decompiler
Restore Python bytecode .pyc files into readable source code for easy code auditing and learning. Supports mainstream versions.
When you need to display < in an HTML document without it being parsed as a tag, or pass query parameters containing spaces in a URL, special character escaping ensures accurate data transmission. This tool uses standardized algorithms to convert special characters into escape sequences (such as < or %20), or unescape them back to their original form. It covers three main scenarios: HTML entities, URL encoding, and JavaScript strings.
Why does URL encoding convert spaces to %20?
This is defined by the RFC 3986 standard: spaces in URLs must be encoded as %20, while the plus sign (+) is generally reserved for query parameters.
How do I handle multi-layered nested escape characters? We recommend processing them in the order of your actual application scenario: first unescape the outermost encoding (e.g., HTML entities), then process the inner escaping (e.g., JS strings). Processing them in the wrong order will cause parsing failures.
Please verify the original encoding format before unescaping. Mixing different escape standards (such as treating HTML entities as JS escapes) will result in garbled text. When processing JSON strings containing sensitive information, we recommend operating in an offline environment.
When developing API endpoints, it is highly recommended to use URL encoding for query parameters. For example, the search term "咖啡&茶" should be encoded as q=%E5%92%96%E5%95%A1%26%E8%8C%B6, where the Chinese characters use UTF-8 encoding and the & symbol is converted to %26. Note that browser address bars will automatically decode and display the text, but the actual transmitted data remains the encoded string.
