Convert GeoJSON to CSV when the people who need the data live in spreadsheets rather than web maps. The FeatureCollection is flattened locally in-browser, with no API, no upload and no account.
Drop a file here, or click to browse
KML, KMZ, SHP (.zip), GeoJSON, GPKG, GML, GPX, DXF, CSV, Excel, and more
No GeoJSON file to hand? Download a sample GeoJSON file (100 points) and drop it above to see the conversion.
Every format stores different things, so a conversion is never perfectly loss-free. Here is exactly what carries over when you convert GeoJSON to CSV, and what to watch for.
| What | GeoJSON → CSV | |
|---|---|---|
| Geometry | Changes | Point features become X and Y columns; lines and polygons are written to a WKT geometry column, so no shape is lost in the table. |
| Attributes | Kept | Every column and full field name moves from GeoJSON into CSV untouched. |
| Styling & labels | Kept | Neither GeoJSON nor CSV stores visual styling, so there is nothing to lose, the geometry and data carry straight over. |
| Coordinate system | Changes | CSV stores raw coordinates without a CRS tag, so note the coordinate system separately for whoever opens the file. |
| Elevation (Z) | Changes | Z values, if present, appear as an extra column rather than 3D geometry. |
| File structure | Kept | A single, self-contained .csv file you can move around on its own. |
GeoJSON is the language of web maps. It packs geometry and attributes into one JSON structure, which is great for Leaflet or Mapbox but awkward in a spreadsheet. So people convert GeoJSON to CSV when they want to leave the map and work with the raw table. For example, you might pull features from a web API, then open them in Excel or Google Sheets to sort, filter, or chart the attributes. Analysts also convert to CSV to feed point data into pandas scripts. CSV strips the nesting and gives you flat rows that any tool, GIS or not, can read.
GeoJSON is already defined in WGS84 longitude/latitude (EPSG:4326), so no guessing is needed on the way in.
CSV stores raw coordinates without a CRS tag, so make a note of the coordinate system for whoever opens the file next. A quick CRS check before you download saves the classic "my GeoJSON data is in the wrong place" surprise; the guide on coordinate systems and EPSG codes goes deeper.
Check how each feature's geometry lands in the CSV. GeoJSON can hold points, lines, and polygons, but a flat CSV row wants simple coordinate columns. Points map cleanly to latitude and longitude. Lines and polygons cannot fit two numbers, so their geometry is usually written as WKT text instead. Also confirm your GeoJSON coordinates are in WGS84, since CSV stores bare numbers with no coordinate system attached.
GeoJSON files typically come out of Leaflet, Mapbox GL, OpenLayers, QGIS, GDAL. Once you convert to CSV, the file opens in Microsoft Excel, Google Sheets, LibreOffice Calc, and any script or database import. The CSV output follows the standard specification exactly, so those programs read it without any special import settings.
GeoJSON is where web maps and APIs keep their vector data, with each feature holding a geometry plus a bag of properties. CSV is the flat table you open in a spreadsheet to sort, filter and chart those same records. Converting one to the other pulls features out of the mapping stack and into analysis. In practice you export a FeatureCollection, then read the attributes as plain columns. That means non-mapping colleagues can work the data without touching any GIS tool.
Yes. Each key inside a feature's properties object becomes a CSV column, and every feature becomes one row. The geometry is added as coordinate columns or WKT alongside those attribute columns.
A polygon cannot fit into simple latitude and longitude cells, so its geometry is written as WKT text in a single column. Points, by contrast, become plain lat and lon values that Excel or pandas can read directly.
Point features map cleanly to latitude and longitude columns, one row per feature. Lines and polygons cannot fit two number columns, so their coordinates are written into a single geometry field as WKT. That keeps the shape intact for tools like QGIS or pandas that can parse it back.
CSV is strictly flat, so a nested object or array inside a feature's properties cannot become its own column. Those values are serialized into a single cell as text rather than dropped. For example, a properties block with an address object becomes one string you can split later in Excel.
A CSV file opens in Excel, Google Sheets, LibreOffice and any database. Because the output follows the standard specification, any tool that supports CSV will read it without special settings.
No conversion is perfectly loss-free because each format stores different things, but nothing important is lost: point coordinates become X/Y columns and any lines or polygons are saved as WKT text, so the geometry survives in the table.
