Convert GeoJSON to newline-delimited GeoJSON (NDJSON) locally - for tippecanoe and big data. No upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
Newline-delimited GeoJSON (NDJSON, also called GeoJSONL or GeoJSON Text Sequences) writes one GeoJSON Feature per line instead of wrapping them all in one FeatureCollection. Tools like tippecanoe and ogr2ogr prefer it because a huge dataset can be streamed line by line without loading the whole file into memory.
This tool reads your GeoJSON FeatureCollection and writes each feature as one compact JSON object on its own line. The geometry and properties of every feature are kept exactly; only the surrounding FeatureCollection wrapper is removed. The partner tool NDJSON to GeoJSON puts it back together.
Everything runs entirely locally in the browser - your possibly sensitive location data never leaves your device. Honestly framed: the output is one feature per line, not a single JSON document, so it will not validate as one GeoJSON object on its own - that is exactly what NDJSON is for. An invalid or empty GeoJSON is rejected with a clear message.
| Input formats | GEOJSON, JSON |
|---|---|
| Output format | NDJSON |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Converts a GeoJSON FeatureCollection to newline-delimited GeoJSON (NDJSON / GeoJSONL): one Feature as compact JSON per line. Used by tippecanoe and ogr2ogr for streaming large datasets. Round-trips with NDJSON to GeoJSON. An invalid or empty GeoJSON is rejected with a clear error.
Streaming large geodata: tools like tippecanoe and ogr2ogr read one Feature per line without loading the whole file at once.
Yes, each feature keeps its geometry and properties exactly; only the FeatureCollection wrapper is removed.
Yes, use the partner tool NDJSON to GeoJSON to wrap the lines back into one FeatureCollection.
No, the conversion happens entirely locally in the browser; location data never leaves your device.