NDJSON to JSON Converter

How to use the ndjson to json converter

1. Paste your NDJSON text into the input area, ensuring each line contains one complete JSON value.
2. Toggle Pretty print output if you want the resulting array indented for readability.
3. The converted JSON array appears immediately below as you type or paste.
4. Copy the result to use in your application, API response, or data pipeline.

What is NDJSON?

NDJSON stands for Newline Delimited JSON. It is a text format where each line is a separate, self-contained JSON value. Unlike a standard JSON file that wraps everything in a single root object or array, NDJSON streams values one per line. This makes it ideal for appending log entries, streaming large datasets, and processing records sequentially without loading an entire file into memory.

A valid NDJSON file might look like this:

{"id":1,"status":"ok"}
{"id":2,"status":"fail"}
{"id":3,"status":"ok"}

Each line parses independently. Empty lines are typically ignored during conversion.

How the conversion works

The ndjson to json conversion follows a straightforward algorithm. First, the input text is split on newline characters (\n or \r\n). Blank lines are discarded. Then, each remaining line is parsed individually using a standard JSON parser. If any line fails to parse, the tool reports the exact line number and error message. Finally, all successfully parsed values are collected into a single JSON array.

For example, given three lines containing 1, "two", and [3], the parser produces the array [1, "two", [3]]. The optional pretty-print step then applies indentation (two spaces per level) to make the output human-readable.

Common use cases

Converting NDJSON to a JSON array is frequently needed when moving data between systems that expect different formats. Here are typical scenarios:

• API responses: Some services stream results as newline-delimited JSON. Wrapping them in an array makes them compatible with clients expecting standard JSON.
• Log analysis: Structured logs from tools like Winston or Bunyan are often written in NDJSON. Converting them to an array allows easy filtering and transformation.
• Data import: Databases and analytics tools sometimes require a single JSON array rather than a stream of objects.

If your source data is in other structured formats, sibling converters like TSV to JSON, TOML to JSON, or INI to JSON handle those transformations before you reach the JSON stage.

Edge cases and pitfalls

Several edge cases can trip up a naive ndjson to json converter:

• Trailing newlines: Files often end with a newline character, producing an empty final line. A robust converter skips empty lines rather than throwing a parse error.
• Mixed value types: NDJSON does not require every line to be an object. Lines can contain strings, numbers, booleans, null, or arrays. The resulting JSON array will hold mixed types, which is perfectly valid JSON but may surprise downstream consumers expecting uniform objects.
• Large files: Because this tool collects all values into a single array in memory, extremely large NDJSON inputs (millions of lines) may cause the browser tab to slow down. For massive datasets, consider command-line tools like jq.
• Invalid JSON on one line: A single malformed line prevents the entire conversion. The error message identifies the offending line number so you can fix it quickly.

NDJSON vs JSON Lines

You may encounter the terms NDJSON and JSON Lines used interchangeably. Both describe the same concept: one JSON value per line, separated by newline characters. The JSON Lines specification (.jsonl extension) formalizes what NDJSON describes. In practice, any tool that reads NDJSON also reads JSON Lines and vice versa. When converting either format to a standard JSON array, the process is identical.

Worked examples