What is CSV / NDJSON Converter?
CSV and NDJSON Converter handles bulk logs, event imports, and line-oriented processing. Each CSV row becomes one compact JSON record, while reverse conversion parses every non-blank line and rebuilds a table with precise errors for damaged records. Values are not guessed as numbers, dates, or booleans, protecting postal codes, long identifiers, and leading zeros until the destination schema applies its own types. Common workflows include the following. Generate JSON Lines test data. Export event logs to CSV. Locate a damaged batch line. 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 test data.
- Export event logs to CSV.
- Locate a damaged batch line.
How to use it
- Choose the CSV delimiter.
- Prepare one header row and data rows.
- Keep each NDJSON record on one line.
- Convert and compare record counts.
- 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
id,event,ok
63,develop,true
70,release,falseExample 2
{"id":"63","event":"development","ok":true}
{"id":"70","event":"release","ok":false}Input rules
- CSV requires unique headers.
- Each non-blank NDJSON line must be a complete object.
- A record cannot span lines.
- 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.
- Each NDJSON line must contain one complete object.
Output rules
- Each CSV row becomes one record.
- Blank NDJSON lines are ignored.
- Imported CSV values remain strings.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- Blank NDJSON lines are ignored.
Limitations and cautions
- Each NDJSON line must contain one complete object.
- Blank NDJSON lines are ignored.
- CSV values remain strings after import.
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.