JSON Lines to array

What the conversion does

Combine one JSON value per line into a JSON array. Parse each line independently and write one readable array.

Worked example

Start with the input shown on this page: {"name":"Hello","message":"Welcome"} {"name":"Welcome"}. The tool produces: [ { "name": "Hello", "message": "Welcome" }, { "name": "Welcome" } ]. Try the example first so you can compare the two representations. Then replace it with your own material. The result is plain text that you can copy into an editor, a test fixture or a request only after checking that its destination expects the same form.

Format rules and limits

JSON Lines stores one complete JSON value on each line, making records easy to stream or inspect. Each line is parsed independently; a blank line in the middle is rejected because it is not a JSON value. A final line ending is allowed. The reverse tool accepts a JSON array and writes one compact JSON value for each member. Line breaks inside a JSON string remain escaped as backslash-n, so they do not split a record. Top-level values may be objects, arrays, numbers, strings, booleans or null, although a receiving service may demand objects only. The resulting array is one JSON document; the line form is several JSON documents and should not be submitted to an endpoint that expects a single JSON value. Check encoding as UTF-8 and any downstream record size limit before using large exports.

Check the result

Keep the original beside the transformed text while you inspect it. Compare a small known case first, especially one containing punctuation, a non-ASCII character, a repeated value or an empty field relevant to your data. A readable output is not proof that the receiving program accepts the same schema or conventions. If you exchange data between applications, run the receiving parser and review a few records after import. Keep important source files under version control so changes are reversible. Processing takes place in your browser; this page does not send the pasted input to a conversion server. Browser memory and the clipboard still need ordinary care on shared devices.

The source and result have different roles even when they look similar. The method above defines the accepted subset rather than every extension of the named format. For a strict receiving system, try a small known case before changing many records. If validation fails, return to the original input and the first reported error; editing only the generated result can hide the cause.

Validate the generated JSON Lines by parsing each nonempty line separately; validate a generated array by parsing it once as a complete JSON document. Keep line breaks inside strings escaped so they do not become accidental record boundaries. If a downstream service requires objects on every line, check that requirement explicitly because the format itself also permits scalar values. A final newline is acceptable for many line-based readers.