Got a log file or a database export in JSONL format that you need to open in a standard editor? This tool wraps those individual JSON lines back into a single, valid JSON array. It’s the easiest way to make streaming data readable and ready for your next project.
{"id": 1, "name": "Alice", "role": "admin"}
{"id": 2, "name": "Bob", "role": "editor"}
{"id": 3, "name": "Carol", "role": "viewer"}[
{"id": 1, "name": "Alice", "role": "admin"},
{"id": 2, "name": "Bob", "role": "editor"},
{"id": 3, "name": "Carol", "role": "viewer"}
]| Feature | JSONL | JSON | NDJSON | CSV |
|---|---|---|---|---|
| Structure | One object per line | Single root array/object | One object per line | Header row + data rows |
| Streaming | Yes - line by line | No - must parse entire file | Yes - line by line | Yes - line by line |
| Nested Data | Supported per line | Fully supported | Supported per line | Not supported |
| File Extension | .jsonl | .json | .ndjson | .csv |
| Common Use | Logs, ML datasets, BigQuery | APIs, web apps, configs | Log aggregation, Elasticsearch | Spreadsheets, databases |
| Human Readable | Moderate | Good (when formatted) | Moderate | Excellent |
| Append-Friendly | Yes - just add lines | No - must rewrite array | Yes - just add lines | Yes - just add rows |
Provide a .jsonl or .ndjson file with one object per line.
Each line is parsed individually to ensure valid JSON syntax.
Objects are wrapped in array brackets with proper commas.
Get a formatted .json file ready for APIs or web apps.
Converting JSONL to JSON in Python is simple using the built-in json module. Read each line from the JSONL file, parse it with json.loads(), append to a list, and write the list as a JSON array with json.dump(). This approach handles large JSONL files efficiently by processing line by line. Perfect for converting streaming data, log files, or machine learning datasets into standard JSON format for analysis or API consumption.
import json
# Read JSONL and convert to JSON array using list comprehension
with open("data.jsonl", "r") as f:
records = [json.loads(line) for line in f if line.strip()]
# Write as standard JSON array
with open("output.json", "w") as f:
json.dump(records, f, indent=2)
print(f"Converted {len(records)} JSONL lines to JSON array")Converting JSONL to JSON in Node.js uses the fs module and readline for efficient line-by-line processing. Read the JSONL file, parse each line with JSON.parse(), collect into an array, and write as JSON with JSON.stringify(). This streaming approach handles large files without loading everything into memory. Ideal for backend services, data transformation pipelines, or converting API responses from JSONL format to standard JSON arrays.
const fs = require("fs");
const readline = require("readline");
async function jsonlToJson(inputPath, outputPath) {
const records = [];
const rl = readline.createInterface({
input: fs.createReadStream(inputPath),
crlfDelay: Infinity,
});
for await (const line of rl) {
if (line.trim()) {
records.push(JSON.parse(line));
}
}
fs.writeFileSync(outputPath, JSON.stringify(records, null, 2));
console.log(`Converted ${records.length} lines to JSON array`);
}
jsonlToJson("data.jsonl", "output.json");JSONL is better for streaming because you can read one line at a time without loading the whole file into memory. This makes it perfect for processing logs, large datasets, or real-time data feeds where you process records as they arrive.
Standard JSON arrays are better for tools that expect a JSON array input, like most data analysis tools, Pandas, and REST APIs. They need the data wrapped in brackets with commas between objects.
Convert when your downstream tool doesn't support JSONL natively. If you're loading data into a web app, sending it to an API, or importing into a tool that expects standard JSON, you need to convert from JSONL to a JSON array first.
Most conversions happen because the next step in your workflow expects standard JSON format, not line-delimited records.
If one line is malformed (missing bracket, trailing comma, unquoted key), the whole conversion will fail or skip that line. This is the #1 problem users hit when converting JSONL files.
How to find it: open the file in VS Code and look for the red squiggle on the bad line. VS Code's JSON validator will highlight syntax errors immediately.
Or run jq -c . yourfile.jsonl in the terminal. jq will tell you exactly which line number failed and what the error is. This is the fastest way to debug JSONL parsing issues.
Fix the malformed line, save the file, and try converting again. One bad line can break the entire conversion, so validation is critical.
The tool runs in the browser so there's no server upload. Your data stays on your machine, which is great for privacy but means large files depend on your browser's memory.
Very large files (1GB+) may be slow in the browser or cause it to freeze. For those, use the Python one-liner: python3 -c "import json,sys; print(json.dumps([json.loads(l) for l in open('file.jsonl')]))" > output.json
This processes the file line by line without loading everything into memory at once, making it much faster for large datasets.
Hand-picked guides to go deeper
Compare JSON vs XML vs YAML for APIs, config files, and data exchange. Includes syntax examples, performance benchmarks, readability tests, and use case recommendations for developers.
Parse JSON in Python using json.loads() for strings and json.load() for files. Complete guide with code examples, error handling, nested data, and real-world use cases.
Read JSON files in JavaScript using Fetch API, Node.js fs module, and ES6 imports. Complete guide with code examples for browser and server environments, error handling, and large file processing.