Data & Requests · LOCAL TOOL
NDJSON Line Diagnostics
Review newline-delimited JSON one physical line at a time. Separate valid values, invalid source lines, and skipped blank lines, then recover only the successfully parsed records.
No API call
Your input
LOCALResult
Run the tool to see a result.
Your result will appear here. Input is not saved.
WHY THIS TOOL EXISTS
A focused job, not a black box.
Unlike formatting one JSON document, this report preserves which individual lines failed and leaves their original text available for repair. A broken record does not hide the rest of an export.
How to use it
- Paste an export with one complete JSON value on each line.
- Run the check and compare valid and invalid line numbers.
- Review the recoveredNdjson field before copying valid data into a new file.
TRY A WORKING EXAMPLE
Start with known input.
Load this sample into the workspace, run the tool, and compare the result shown below.
Show sample input
{
"source": "{\"id\":1,\"ready\":true}\n{\"id\":2,}\n\n{\"id\":3,\"ready\":false}"
}Expected sample result from the local tool
2 valid · 1 invalid line(s).
{
"valid": [
{
"line": 1,
"value": {
"id": 1,
"ready": true
}
},
{
"line": 4,
"value": {
"id": 3,
"ready": false
}
}
],
"invalid": [
{
"line": 2,
"source": "{\"id\":2,}",
"error": "Expected double-quoted property name in JSON at position 8 (line 1 column 9)"
}
],
"blankLines": [
3
],
"recoveredNdjson": "{\"id\":1,\"ready\":true}\n{\"id\":3,\"ready\":false}"
}LIMITS AND INTERPRETATION
What the result cannot tell you.
Up to 200000 characters. Multiline JSON values are not NDJSON and are checked as separate lines. Recovery excludes invalid lines and does not repair them automatically.
Inputs are processed in this page and are not written to local storage.