Save a JSON array as one JSONL value per line
Convert a JSON array to JSONL when the receiving system expects one value per line. Each item in the selected array becomes a line; nested arrays are not automatically expanded into additional records.

How to use this tool
- Choose files in JSON format. Maximum files per batch: 1.
- Review Array path (empty for root array), then start processing.
- Download the JSONL result and check its content and quality.
Choose the right settings
Leave the array path empty for a top-level array. For one inside an object, enter a dotted path such as data.items and confirm that the value at that location is an array.
- Supported input
- JSON
- Output
- JSONL
- Available settings
- Array path (empty for root array)
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
[{"record":1},{"record":2}] → one JSON record per lineExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Compare nonempty output lines with the selected array's item count. Check that every line is valid JSON and inspect line breaks inside strings to ensure they remain part of their values.
If the result is different from what you expected
A missing path or a final value that is not an array cannot be processed. Very deep or large structures can reach safety limits, so prepare only the array required for the task.
Limits to keep in mind
- The selected value must be an array. Each output line is a complete JSON value.
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.