GeoJSON to CSV Converter
Writes a GeoJSON file as CSV table with geometry columns, using GDAL's ogr2ogr.
Upload a .geojson or .json file. You get a CSV with all properties and the geometry: X/Y for a point layer, a WKT column for lines, polygons or mixed geometries.
Drag a file here to convert, or select file
Accepted: .geojson, .json · max. 50 MB
What the converter does
- Point layers get the columns X and Y (and Z if the points have heights) in front of the attributes; lines, polygons and mixed layers get a column WKT with the geometry as Well-Known Text.
- CSV cannot store a coordinate system. The coordinates stay as they are and the report names their coordinate system (e.g. EPSG:4326 or EPSG:25832).
- Lists and objects become JSON text, e.g. [ "bahn", "fern" ].
- The report below the upload shows layers and features read and written, skipped layers with the reason, GDAL's warnings and the exact commands.
GDAL command the worker runs
For a point layer. For lines, polygons and mixed layers the worker uses -lco GEOMETRY=AS_WKT -lco GEOMETRY_NAME=WKT.
Tested with
| Test file | Result |
|---|---|
| 4 points with 10 properties | CSV with X, Y and all properties; tags as [ "bahn", "fern" ] |
| Mixed file: 2 points, 1 line, 1 polygon | CSV with a WKT column for all 4 rows |
Tested on 24 Sep 2026 with the worker code of this site and GDAL 3.10.3 (conda-forge build on Windows). The worker image runs the Debian build of the same GDAL version; the live worker was not part of these tests.
Limits
- Upload limit: 50 MB per file.
- CSV stores no coordinate system.
- Each GDAL step may run for up to 240 seconds; a longer run is stopped with an error message.
Frequently Asked Questions
What happens to my file?
Your browser uploads it directly to the GDAL worker on Fly.io (region Frankfurt). The worker converts it in a temporary folder and deletes the folder after sending the result, or immediately if the conversion fails. Files are not stored permanently.