What is TOML / NDJSON Converter?
TOML and NDJSON Converter connects configuration and record streams through an explicit rows array of tables. Every TOML rows item becomes one NDJSON line. Reverse conversion parses row objects line by line and wraps them in rows, avoiding guesses about arbitrary TOML settings. Review field types and date semantics before using the result in a pipeline. Common workflows include the following. Generate JSON Lines records. Store NDJSON batches as TOML. Check record counts and boundaries. The page also documents input boundaries, output behavior, and practical cautions so you can review the result before putting it into an application, configuration, test, or production workflow.
When to use it
- Generate JSON Lines records.
- Store NDJSON batches as TOML.
- Check record counts and boundaries.
How to use it
- Use a TOML rows array of tables.
- Keep one complete JSON object per NDJSON line.
- Convert and compare record counts.
- Review string and date normalization.
- Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
- Review the output, status message, and documented limits; copy, download, or continue only after the result matches your expectation.
Runnable examples
The “Example 1” and “Example 2” buttons load the matching inputs. They cover different structures, directions, or boundaries and can be run directly in the workspace.
Example 1
[[rows]]
id = "61"
status = "ready"
[[rows]]
id = "70"
status = "planned"Example 2
{"id":"61","status":"ready"}
{"id":"70","status":"planned"}Input rules
- TOML must contain one rows array.
- Every NDJSON line must be a complete object.
- Damaged lines are rejected.
- Text input is counted before processing and is limited to 1,000,000 characters on this page; file modes apply the separate file limit shown in the workspace.
- TOML to NDJSON requires one rows array.
Output rules
- Each rows item becomes one record.
- Reverse output always uses rows.
- Comments and source layout are not retained.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- Every NDJSON line must be a row object.
Limitations and cautions
- TOML to NDJSON requires one rows array.
- Every NDJSON line must be a row object.
- Comments and original layout are not retained.
How your data is handled
All parsing, conversion, Base64 work, and intermediate data remain in the current browser tab. JSONLane does not upload the input or retain it after refresh or close.