Question 1

What is string escaping and why is it needed?

Accepted Answer

String escaping converts special characters into escape sequences so they can be safely embedded in code or data formats. For example, a quote inside a JSON string must be written as \" to avoid prematurely ending the string literal. Without escaping, the parser would misinterpret the text.

Question 2

What's the difference between JSON escaping and HTML escaping?

Accepted Answer

JSON escaping handles characters special to JSON strings (quotes, backslashes, control characters like newlines). HTML escaping converts characters that have meaning in HTML markup, such as < → <, > → >, & → &, and " → ". You need the right type of escaping depending on the target context.

Question 3

What is double-escaping and how do I avoid it?

Accepted Answer

Double-escaping happens when you escape a string that is already escaped, turning 
 into \n. This usually occurs when storing escaped strings in a database and escaping again when inserting them into HTML. Escape only once, at the final output boundary for the target format.

Question 4

Why should regex special characters be escaped?

Accepted Answer

Characters like ., *, +, ?, (, ), [, ], {, }, ^, $, |, and \ have special meanings in regular expressions. If your pattern contains a literal dot or parenthesis, you must escape them with a backslash (\. or \() so the regex engine treats them as plain characters rather than metacharacters.

Question 5

Can null bytes appear in strings and do they need escaping?

Accepted Answer

Null bytes (\0 or \u0000) are valid in many programming languages but cause issues in C-style strings (which are null-terminated) and some databases. In JSON, they must be escaped as \u0000. Many web contexts silently truncate strings at null bytes, so escaping them explicitly is safer.

String Escape / Unescape

Frequently Asked Questions

Code Implementation

Comments & Feedback