JSON to TOML
Turn a JSON object into a TOML document with proper tables and arrays of tables.
Convert between JSON arrays and NDJSON, one compact document per line.
The JSON Lines Converter moves between a JSON array and NDJSON, the one-document-per-line format used by log pipelines, BigQuery and Elasticsearch bulk loads. A broken line is reported by its line number.
JSON Lines — also written NDJSON or .jsonl — puts one complete JSON document on each line with no wrapping array and no commas. It is the format log pipelines, BigQuery, Elasticsearch bulk loads and streaming APIs use, because a reader can process a line at a time.
This converter goes both ways. Turning an array into JSON Lines gives you a file that streams; turning JSON Lines into an array gives you something a normal JSON parser will accept. When a line fails to parse the error names the line number, which is the one thing that matters in a file of ten thousand records — a single bad line in the middle is otherwise almost impossible to find.
A single bad record in ten thousand lines is reported by line number, which is otherwise almost impossible to find.
Array to JSON Lines for streaming and appending; JSON Lines back to an array for anything that expects a normal document.
The number of records read is shown, so a truncated paste is obvious before you load the file anywhere.
Each record is written on exactly one line, which is the constraint the whole format depends on.
Downloads use .jsonl or .json to match the direction, so the file arrives named the way the receiving tool expects.
Array to JSON Lines, or JSON Lines back to an array.
A JSON array of objects, or a file with one document per line.
The stat row confirms how many records were read, so a truncated paste is obvious.
Download as .jsonl or .json depending on the direction you converted.
Nothing meaningful — they are three names for the same format. The .jsonl extension is the most common in practice, and .ndjson appears mostly in older tooling.
Because you can append a record without rewriting the file, and a reader can process one line at a time without holding the whole document in memory. That is what makes it the default for logs and bulk loads.
No. Each record must be on exactly one line, which is why the documents are always minified. That constraint is the entire point of the format.
The conversion stops and names the line number and the parse error, so you can go straight to it rather than bisecting the file.
What people who use the JSON Lines Converter think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the JSON Lines Converter. It takes half a minute and no account.
Write the first reviewTurn a JSON object into a TOML document with proper tables and arrays of tables.
See an IP address in binary, hex and decimal, octet by octet.
Generate Java POJOs or records with Jackson annotations from JSON.
Convert HTML back into clean Markdown, keeping lists, tables and code.
Turn a curl command into working fetch, axios, Python, PHP, Go or Ruby.
Generate Dart model classes with fromJson and toJson from a sample payload.
Check any number against the Luhn checksum and see the working.
Generate Nano IDs — shorter than a UUID, and URL-safe by design.