HCODX/JSON to NDJSON
100% browser-based · UTF-8 safe · No upload

JSON to NDJSON

Convert a JSON array into NDJSON — one valid JSON value per line, no enclosing brackets. Ideal for streaming, log lines, BigQuery load, Elasticsearch bulk imports, and tail-friendly pipelines.

JSON input
NDJSON output
Options
Reverse (NDJSON → JSON)
Input size
0 B
Output size
0 B
Output lines
0
Status
Ready
Example

JSON in, NDJSON out

See exactly how JSON maps onto NDJSON — the converter on this page produces output identical to the example below.

JSON input
[
  {"id":1,"name":"Alice"},
  {"id":2,"name":"Bob"},
  {"id":3,"name":"Charlie"}
]
NDJSON output
{"id":1,"name":"Alice"}
{"id":2,"name":"Bob"}
{"id":3,"name":"Charlie"}
Use cases

What you'll use this for

Converting JSON to NDJSON is a daily task in API integration, config management, and data pipelines.

API integration

Stream-friendly format for paginated APIs and log shippers.

Config migration

Move between batch JSON and line-oriented pipelines.

Data import

Native bulk load format for BigQuery, Athena, and Elasticsearch.

CI pipelines

Pipe through jq, awk, or shell tools per line.

Step by step

How to convert JSON to NDJSON

1

Paste your JSON

Drop it into the left editor. The sample is loaded by default — clear it or click the wand to reload.

2

Click Convert

Or leave auto-convert on for live updates. Conversion runs entirely in your browser — no upload.

3

Copy or download

Copy to clipboard or save the output as data.ndjson.

4

Reverse if needed

Jump to the NDJSON to JSON converter for a round-trip check.

FAQ

Frequently asked questions

Yes. NDJSON is just JSON, line by line — types are preserved exactly.

Each array element is serialized verbatim onto its own line with no extra indentation.

Yes. No signup, no limits.

You'll see a clear parse error in the output panel.

Use the NDJSON to JSON converter to rejoin lines into an array.

About

About JSON and NDJSON

NDJSON (newline-delimited JSON), also known as JSON Lines (.jsonl), is the streaming-friendly cousin of JSON: each line is independently parseable. It's the native format for BigQuery loads, Elasticsearch _bulk, structured logs, and ML training shards.

Common pitfalls

  • Input must be an array — each element becomes one line.
  • Embedded newlines inside values are escaped per JSON rules.
  • Don't pretty-print; NDJSON requires single-line objects.
  • UTF-8 with LF (Unix) line endings is the de-facto standard.
Related

Related tools