How JSON String Escape & Unescape can help
Use this converter when plain text must fit safely inside a JSON string, or when JSON escape sequences need to become readable text again. It handles quotation marks, backslashes, tabs, line breaks, carriage returns, and other characters defined by JSON string syntax.
Text containing a real line break and quotation marks becomes a single escaped sequence such as line 1 "line 2". In the reverse direction, the two characters backslash+n become an actual line break. The result is string content only, without adding surrounding quotation marks.
How the conversion works
Escape mode uses the browser’s JSON string rules, then removes only the outer pair of quotes added during serialization. Unescape mode places the supplied sequence inside a temporary JSON string and accepts it only when the complete sequence parses successfully as one string value.
Select Escape when your starting value is ordinary readable text. Select Unescape when the starting value already contains JSON sequences such as \n, \t, \", \\, or \u0041. Literal line breaks are not valid inside unescape input because valid JSON represents them with escape sequences.
How to use the JSON String Escape & Unescape
Paste or type a small representative example, choose the available output mode, and run the tool. Read the visible result before copying or downloading it. Reset returns the controls to the example state and clears the current output, which is useful before starting a different task.
Copy the result only after checking the preview, or download the escaped or unescaped text file. For a full JSON document, use JSON Formatter or JSON Validator instead. Keeping these tasks separate prevents string-level escaping from being mistaken for document-level validation.
What to check in the result
After escaping, look for each expected backslash and make sure you have not added a second escape layer required only by another language or shell. After unescaping, compare line breaks and whitespace carefully, because tabs and spaces can look similar while remaining different characters.
If the result is empty or surprising, start by checking the first visible error, the selected mode, and whether the source uses the syntax this page accepts. Try a smaller known example before returning to important input; this separates a format problem from a misunderstanding about the expected output.
Privacy and important limits
Your input and result remain in the current browser tab. They are not sent to NexaCurrent, added to the page address, saved to an account, or reused after you reset or leave the page. Avoid pasting passwords, private keys, access tokens, or personal records into any convenience tool when a smaller non-sensitive example can answer the same question.
This tool handles the contents of one JSON string. It does not format a complete JSON object, repair malformed JSON documents, interpret JavaScript template literals, or apply the additional quoting rules of SQL, HTML, regular expressions, command shells, or programming-language source files.