NDJSON to CSV
Universal Format Converter
Convert between CSV, TSV, JSON, and Excel. Supports multiple files, primary data, and batch operations.
Select a data source to begin conversion
No data loaded
Upload files or use primary data to start converting
About NDJSON to CSV
Convert newline-delimited JSON (NDJSON / JSON Lines) log and pipeline exports into CSV rows, one JSON object per line turned into one row.
NDJSON is the format most log pipelines, Kafka consumers, and Elasticsearch bulk exports use — one complete JSON object per line, instead of one big JSON array. That makes it easy to stream and append to, but not something a spreadsheet can open directly.
This converter reads each line as its own JSON object and flattens the set into CSV rows, so a pipeline export becomes something you can sort, filter, and pivot immediately.
It also serializes CSV data back into NDJSON, one compact JSON object per line, which is useful when you need to feed edited or filtered data back into a log pipeline or bulk-import API that expects the line-delimited format.
Because parsing is just JSON.parse per line, it handles files with hundreds of thousands of records without choking, entirely in your browser.
Category: Conversion & ExportCommon Use Cases
- Turning a Kafka topic dump into a spreadsheet
- Reviewing Elasticsearch bulk export data
- Converting log pipeline output for analysis
Key Features
- Parses each line as an independent JSON object without needing a wrapping array
- Handles files with hundreds of thousands of records via per-line JSON.parse
- Serializes CSV back into line-delimited JSON for pipeline or bulk-import re-ingestion
The NDJSON to CSV tool is compatible with: Kafka Consumers, Elasticsearch Bulk Export, Log Pipelines.
Convert a log or Kafka NDJSON dump here first, then use CSV to JSON if you need a different JSON shape, or Multi-Format Converter for a broader export format.
Frequently Asked Questions
A regular JSON file has one big array wrapping all records; NDJSON has one independent JSON object per line with no wrapping array or commas between records — that makes it streamable and appendable.
Each line is parsed as its own JSON object and used as one row — nested objects and arrays inside a line are kept as-is in that cell rather than being flattened into separate columns.
Built for data engineers and analysts who need to eyeball or filter a streaming log or Kafka export without spinning up a pipeline.
Read the related guide →