Collect JSONL values into a JSON array
Converting JSONL collects the value on each nonempty line into an array. Every line must contain one complete JSON value, so its input structure differs from a conventional JSON object formatted across several lines.

How to use this tool
- Choose files in JSONL, NDJSON, TXT format. Maximum files per batch: 1.
- Review Indentation, then start processing.
- Download the JSON result and check its content and quality.
Choose the right settings
Choose two-space, four-space or zero indentation for the output. Zero creates compact JSON, but the result is still an array rather than a JSONL file that preserves one record per line.
- Supported input
- JSONL, NDJSON, TXT
- Output
- JSON
- Available settings
- Indentation
Before you start
Establish the meaning of the input
Before converting or arranging data, identify what a row or value represents and keep a source copy. In tabular files, review headers, separators and text encoding; in structured files, inspect the required object or array shape. Identifiers, dates and amounts should not be interpreted solely from how a spreadsheet happens to display them.
Where the tool offers matching columns, type rules or output fields, choose them according to the destination’s requirements. Test a sample with a blank, a repeated value and a value containing punctuation. For labels, charts or personalized documents, check which column supplies each displayed value and whether the source units and wording are correct.
Define a few checks before processing: an identifier that must retain its spelling, a value with a known interpretation and an expected relationship between records. If the tool offers type conversion or matching rules, distinguish a source value from the program’s display of it. Test ambiguous dates or differently written keys before accepting a broad rule. Keep the chosen rules and destination requirements with the result; this makes a discrepancy traceable to input, interpretation or the requested transformation.
Verify values, structure and exceptions
Reopen or import the result using the destination’s settings. Compare headers, record counts and several values with the source, allowing for the operation you requested. A summary, split or duplicate-removal task can legitimately change the count; verify why it changed rather than expecting every transformation to keep identical rows.
Inspect any exception or validation report before continuing. If columns shift, characters are garbled or a key is not found, check delimiters, encoding and exact header spelling first. Encoding data does not encrypt it, and formatting a value does not confirm its meaning. For printed codes or labels, test the actual output before making the full set.
Example input and output
two valid JSON lines → two-element JSON arrayExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Compare the input's nonempty-line count with the resulting array length. Sample the first, middle and last items to review both the values and their order.
If the result is different from what you expected
Objects spanning multiple lines or several JSON values on one line are unsupported. Correct a failing line to contain one complete JSON value before processing it again.
Limits to keep in mind
- Every non-empty line must contain one complete JSON value. A malformed line stops conversion instead of being silently discarded.
Continue with a related tool
This guide explains the public browser tool. Keep a copy of the original and inspect the result before sharing it.