JSON Multiline String

About the JSON Multiline String

The JSON grammar forbids a raw line break inside a string. An email body, a certificate, a shell script or an SQL statement therefore has to be folded before it can sit in a configuration file or a request body. This converter escapes every newline as \n, escapes the quotes and backslashes around it, and hands back a literal that any parser will accept.

Four shapes cover the common house styles. One string keeps the text in a single value. An array of lines is easier to review in a pull request because each line diffs on its own. An object with a named key produces a ready made field such as {"body": "..."}. Concatenated pieces prints one quoted fragment per line for languages where the source is easier to read that way.

The line ending selector matters more than it looks. A Windows program that writes CRLF produces \r\n pairs, and a checksum or a test comparison against LF text will fail on that invisible difference. Trimming each line removes the trailing spaces that survive a copy from a terminal.

Switch the direction to unfold a stored value back into readable lines before editing it. For escaping other characters rather than newlines, see JSON Escape, and for whole documents rather than plain text see JSON to String.

How to use

1. Paste the multi-line text on the left, or press Sample to load a short letter.
2. Choose a shape: one string, an array of lines, an object with a key, or concatenated pieces.
3. Set the line ending to CRLF if the text must keep Windows endings.
4. Switch Direction to unfold an existing JSON string back into plain lines.