JSONL Converter and Validator
Convert JSON, JSON Lines, NDJSON, and CSV without uploading your data. Validation reports the exact line that needs attention.
Convert JSON, JSON Lines, NDJSON, and CSV without uploading your data. Validation reports the exact line that needs attention.
JSON Lines stores one valid JSON value on each line. The format is also called JSONL, NDJSON, or newline-delimited JSON. Unlike a single large JSON array, records can be read and processed one at a time, which makes the format useful for logs, data pipelines, model-training datasets, database exports, and command-line workflows.
This converter handles three common jobs: converting a JSON array to JSONL, combining JSONL records into a formatted JSON array, and converting a CSV table into one JSON object per line. Empty JSONL lines are ignored, while malformed non-empty lines are reported with their line number.
Input:
[
{ "id": 1, "name": "Ada" },
{ "id": 2, "name": "Linus" }
]
Output:
{"id":1,"name":"Ada"}
{"id":2,"name":"Linus"}
Each output line is independently valid JSON. Do not add a comma between the lines or wrap the complete file in square brackets.
The validator parses each line separately, so one bad record does not hide the location of the problem. Correct the reported line and validate again before importing the file elsewhere.
The first CSV row is treated as the field-name header. Quoted commas, embedded line breaks, and escaped quotation marks are handled by a standards-aware CSV parser. CSV values remain strings because CSV does not carry reliable type information; convert specific fields to numbers or booleans later when your destination schema requires it.
Conversion happens locally in your browser. The text and files you select are not uploaded to MiniUtil. Very large files still depend on available browser memory, so command-line streaming tools may be more appropriate for multi-gigabyte datasets.
Use the JSON Formatter to inspect a JSON document, CSV Viewer to review table structure, or CSV to JSON converter when the destination expects a regular JSON array.