What is JSONL or NDJSON, and how is it different from a JSON file?

JSONL (also called NDJSON, newline-delimited JSON) puts one complete JSON value on each line, with no commas between lines and no wrapping brackets. A line like {"id":1} then a line like {"id":2} is two records. A normal JSON file holds a single value, usually an array such as [{"id":1},{"id":2}]. JSONL streams record by record so a reader never loads the whole file; a JSON array is one object you parse all at once.

How do I turn JSONL into a JSON array?

Paste your JSONL on the left with the direction set to JSONL to JSON array. The tool parses each non-empty line, gathers the values in order, and prints one array. Input of {"id":1} on the first line and {"id":2} on the second becomes [{"id":1},{"id":2}], pretty-printed at your chosen indent. Pick compact for the smallest output, or 2 or 4 spaces when a human will read it.

How do I turn a JSON array back into JSONL?

Switch the direction to JSON array to JSONL and paste an array like [{"a":1},{"a":2}]. Each element is written on its own line in compact form: {"a":1} then {"a":2}, with no indentation and no trailing comma. That is the exact layout a streaming reader, a BigQuery or Snowflake load job, or an LLM training file wants. If the top level is not an array, the tool says so instead of guessing.

One line of my JSONL is broken. How do I find it?

The converter parses line by line and stops at the first failure with the line number and the parser message, for example "line 4: Unexpected token } in JSON". JSONL hides errors badly because the whole file looks like text, so a single missing comma or smart quote on one line is hard to spot by eye. The line number drops you straight onto the offending row in your editor.

Where do people actually use JSONL versus a JSON array?

JSONL rules anywhere data streams or grows without bound: application logs, Kafka and event pipelines, big-data exports from Spark or BigQuery, and OpenAI-style fine-tuning files where each line is one training example. A JSON array is what most REST APIs return and what JavaScript code, config files, and array.map expect. You convert from one to the other when a tool on the far side speaks the other dialect.

Load a streaming log dump into a tool that wants an array

Your service writes one JSON event per line to a .jsonl file, and you want to drop the day's events into a notebook, a charting widget, or a quick JSON.parse in the console. Those expect a single array, not a stream. Paste the JSONL, convert to a JSON array, copy, and you have one parseable value with every event in order, ready for array.map and filter without a streaming reader in the loop.

Build an OpenAI-style fine-tuning file from an array of examples

You collected training examples as a JSON array while prototyping, but the fine-tuning upload wants JSONL with one example object per line. Switch the direction to JSON array to JSONL, paste the array, and each example lands on its own compact line in the exact shape the trainer reads. Download the .jsonl and upload it without hand-editing brackets and commas out of a thousand-line file.

Find the one corrupt record in a 10,000-line export

A BigQuery or Spark export of NDJSON fails to load and the loader only says "invalid JSON" with no location. Paste it here: the converter parses line by line and reports the first bad line by number with the parser message. You jump to that exact row, fix the stray comma or unescaped quote, and re-run the load instead of bisecting by hand.

Reshape an API response into a streamable feed

An API hands you a big JSON array, but the downstream consumer, a Kafka producer or a tail-friendly log sink, wants newline-delimited records it can read one at a time. Convert the array to JSONL so each element becomes its own line, then pipe or append the result without re-serializing the whole payload as one giant object every time.

JSONL to JSON Converter — NDJSON and JSON Array Both Ways

Turn newline-delimited JSON into a JSON array and back, with bad-line numbers and pick-your-indent — browser only

Runs locally
Category Format Converter
Best for Turning pasted content or local files into a handoff-friendly format.

DirectionIndent

JSONL / NDJSON input

Output

What this tool does

A free two-way converter between JSONL/NDJSON and a JSON array, built for the moment you have one JSON object per line and need a real array, or the reverse. Going JSONL to JSON array, the tool parses every non-empty line, collects the values into a single array, and pretty-prints it at 2 spaces, 4 spaces, or compact. Blank lines are skipped, and if line 7 has a missing comma or a trailing brace it tells you exactly that: "line 7" plus the parser message, so you fix the source instead of hunting through a wall of text. Going the other way, paste a JSON array and it writes one compact object per line, which is the format log pipelines, BigQuery loads, and LLM fine-tuning sets expect. This is not a JSONL beautifier that keeps the line layout. It changes the shape between the two formats. Copy the result in one click or download it as .json or .jsonl. Everything runs in your browser tab, so no record, prompt, or dataset is ever uploaded.

Tool details

Input: Text + Numbers + Structured content; The page exposes text boxes, numeric controls, file pickers, or structured inputs depending on the tool.
Output: Live result + Copy + Download; The result area focuses on usable output, with copy, download, or preview actions when supported.
Privacy: Browser-side processing; The main tool logic does not call an external API, so inputs normally stay in the current tab.
Save / share: Shareable URL state; Key settings are encoded in the URL so another person can reopen the same setup.
Performance budget: Initial JS <= 9 KB; No WASM budget is declared, keeping the tool quick to open on mobile.
Best fit: Format Converter · Developer; Category and role tags drive related tools, internal links, and quick fit checks.

How to use

1. Input

Paste or drop your content into the tool panel.
2. Process

Click the button. All processing is local in your browser.
3. Copy / Download

Copy the result or download to disk in one click.

How JSONL to JSON Converter fits into your work

Use it when the main problem is getting content from one practical format into another.

Conversion jobs

Turning pasted content or local files into a handoff-friendly format.
Previewing a conversion before you use it in a larger workflow.
Cleaning small format mismatches without opening a full editor.

Conversion checks

Try a small sample first when the source format is messy.
Check character encoding, separators, and line endings after conversion.
Keep the source until the converted output has been reviewed.

Good next steps

These links move the current task into a more complete workflow.

Real-world use cases

Load a streaming log dump into a tool that wants an array
Your service writes one JSON event per line to a .jsonl file, and you want to drop the day's events into a notebook, a charting widget, or a quick JSON.parse in the console. Those expect a single array, not a stream. Paste the JSONL, convert to a JSON array, copy, and you have one parseable value with every event in order, ready for array.map and filter without a streaming reader in the loop.
Build an OpenAI-style fine-tuning file from an array of examples
You collected training examples as a JSON array while prototyping, but the fine-tuning upload wants JSONL with one example object per line. Switch the direction to JSON array to JSONL, paste the array, and each example lands on its own compact line in the exact shape the trainer reads. Download the .jsonl and upload it without hand-editing brackets and commas out of a thousand-line file.
Find the one corrupt record in a 10,000-line export
A BigQuery or Spark export of NDJSON fails to load and the loader only says "invalid JSON" with no location. Paste it here: the converter parses line by line and reports the first bad line by number with the parser message. You jump to that exact row, fix the stray comma or unescaped quote, and re-run the load instead of bisecting by hand.
Reshape an API response into a streamable feed
An API hands you a big JSON array, but the downstream consumer, a Kafka producer or a tail-friendly log sink, wants newline-delimited records it can read one at a time. Convert the array to JSONL so each element becomes its own line, then pipe or append the result without re-serializing the whole payload as one giant object every time.

Common pitfalls

Expecting this to keep your line layout. A JSONL beautifier re-indents each line in place and keeps the file as JSONL. This converter changes the shape, so JSONL becomes one array and an array becomes one object per line. If you only want prettier JSONL, use the json-lines-formatter instead.
Pasting a JSON array while the direction is set to JSONL to JSON array. The array's outer brackets and inter-element commas are not valid on a single JSONL line, so the first line fails to parse. Flip the direction to JSON array to JSONL first, or strip the brackets if the data really is meant to be per-line.
Forgetting that JSONL has no commas between records. People hand-build JSONL by copying array elements and leave the trailing commas in. A line ending in a comma is invalid JSON on its own, so the parser flags it. Each line must stand alone as a complete value with nothing after it.

Privacy

Both directions, the line-by-line parse and the array reshape, are plain JavaScript that runs entirely in your browser tab. No JSONL, JSON array, log line, or training example is ever sent to a server, and nothing is logged. The one thing to watch: this tool deliberately does not write your input into the share URL, because logs and datasets are often large or sensitive. To share a result, use the copy or download button and send the file directly rather than passing a link.

FAQ

Tool combos

Folks in your role tend to reach for these alongside this tool.

Developer

Browse all tools for this role

JSONL to JSON Converter — NDJSON and JSON Array Both Ways

What this tool does

Tool details

How to use

1. Input

2. Process

3. Copy / Download

How JSONL to JSON Converter fits into your work

Conversion jobs

Conversion checks

Good next steps

Real-world use cases

Load a streaming log dump into a tool that wants an array

Build an OpenAI-style fine-tuning file from an array of examples

Find the one corrupt record in a 10,000-line export

Reshape an API response into a streamable feed

Common pitfalls

Privacy

FAQ

JSON Lines Formatter

JSON Formatter & Validator

JSON to CSV Converter

CSV ⇄ JSON Converter

Angle Converter

Base64 Encoder & Decoder

Base64 to File Converter

BBCode to HTML Converter

Chinese Numeric Converter

Chinese Pinyin Converter

Chinese Zodiac Sign Checker (Sheng Xiao)

Cooking Measurement Converter