Text Escape Converter

Use URL encoding when text is placed inside a URL path, query parameter, fragment, or form-style value. Spaces, symbols, and non-ASCII characters are represented with percent escapes so the URL can be parsed safely.

URL encoding is for URLs and uses percent escapes such as %20. HTML entities are for HTML text and attributes, using forms such as < and & so markup characters display as text.

JSON string escaping prepares text for a JSON string value by escaping quotes, backslashes, line breaks, tabs, and control characters. Decode mode can unescape either a full quoted JSON string or raw JSON escape sequences.

Unicode escaping writes characters as escape sequences such as \u00e4 or UTF-16 surrogate pairs for emoji. It is useful when a system accepts only plain ASCII characters but still needs to preserve Unicode text.

ASCII-safe output keeps ordinary ASCII characters readable and escapes non-ASCII characters. It is helpful for logs, configuration snippets, legacy systems, and places where non-ASCII characters may be corrupted.

Quoted-printable is an email-oriented encoding that keeps readable ASCII text mostly intact while escaping bytes outside the safe range. It also supports soft line breaks that are removed when decoded.

Punycode represents internationalized domain names with ASCII characters. A domain such as münchen.de becomes an xn-- style name that DNS systems and older tools can handle.

UTF-8 byte output shows the exact bytes behind a string. It is useful for debugging APIs, encodings, file contents, signatures, hashes, and cases where two strings look similar but have different byte values.

Decoding can fail when the input is incomplete, malformed, or uses escape sequences that do not belong to the selected format. The tool reports invalid input rather than silently producing incorrect text.

No. Encoding changes how the text is represented so it can be safely used in a specific context. Decoding converts that representation back where possible.