NDJSON and XML: what actually changes
NDJSON is one JSON object per line, so a huge file can be streamed rather than parsed whole. XML is verbose, schema-validated markup still standard in enterprise and publishing.
Records are read out of the NDJSON with their structure intact and written as XML, so this is a real parse rather than a text substitution — quoting, escaping and character encoding are all handled for you. The XML you get back keeps attributes, namespaces and validation against a schema, and gives up brevity. The thing to check before you rely on the output is typing: dates, leading zeros and very large integers are where formats disagree.
How it goes3 steps
-
Add your NDJSON files
Drop them onto the box above or click Select File. Add as many .ndjson files as you like — the whole batch converts in one go, and duplicates are ignored.
-
Confirm XML as the output
XML is already selected as the target format on this page. Check the delimiter and encoding options if your data is unusual.
-
Download your XML
Hit Convert and grab the finished XML files individually or as a single ZIP. Everything is deleted from the server once you have them.
Format facts
What each side of this conversion is good at, so you know what you are trading away.
Source
.ndjson
NDJSON
One JSON object per line, so a huge file can be streamed rather than parsed whole.
- Compression
- Lossless
- Transparency
- Not supported
- Keeps
- Record structure while staying line-addressable
- Gives up
- The enclosing array — each line stands alone
Result
.xml
XML
Verbose, schema-validated markup still standard in enterprise and publishing.
- Compression
- Lossless
- Transparency
- Not supported
- Keeps
- Attributes, namespaces and validation against a schema
- Gives up
- Brevity
Send NDJSON somewhere else
Every other format a NDJSON file can leave as.
From .ndjson
6 targets