Convert GeoJSON to CSV
Free, private and fast: everything runs in your browser and your GeoJSON file is never uploaded.
GeoJSON to CSV: why convert
GeoJSON is great for maps and code, but to sort, filter or share the attributes as a table, a spreadsheet is easier. This converter writes a CSV with one row per feature and one column per property. Points get two plain coordinate columns, X for longitude and Y for latitude, which every spreadsheet can read; lines, polygons and mixed files get a WKT column instead, which QGIS, PostGIS and most GIS tools can turn back into geometry. You choose between a standard CSV and two Excel styles, one of them with semicolons and decimal commas for Excel in countries that use a decimal comma. Nested properties are kept as JSON text and dates in ISO form. Everything happens in your browser with GDAL.
How to convert GeoJSON to CSV
- Drop your .geojson or .json file in the box, or click to choose it.
- Choose the CSV style, and optionally an output coordinate system.
- Click Convert to CSV and open the file in your spreadsheet or GIS.
What changes when you convert
X and Y, or WKT
When every feature in the file is a point, the coordinates go into the first two columns, X and Y. In WGS84, X is the longitude and Y the latitude. Points with real heights also get a Z column. As soon as the file contains a line or a polygon, all geometries are written as WKT text in a first column called WKT, for example LINESTRING (12.5683 55.6761,12.5794 55.6795), because a pair of columns cannot describe a line. A GeometryCollection is written as WKT too.
Opening the CSV in Excel
Excel opens a CSV without a byte order mark in an old encoding and shows ø as ø. Both Excel styles add the mark, so letters display correctly. In countries where the decimal mark is a comma, Excel expects semicolons between columns and reads 12.59 as text or even as a date; the "Excel in Europe" style writes semicolons and decimal commas for that case. Use the standard style for GIS programs, databases and scripts.
Leading zeros in Excel
The CSV keeps text such as the postcode 0800 exactly, but Excel converts it to the number 800 when it opens the file directly. To keep the zero, import the file in Excel with Data, From Text/CSV and set that column to text.
Nested properties and dates
A CSV cell holds plain text, so nested objects and arrays are written as JSON text, true and false become 1 and 0, and dates are written as 2024-05-01 or 2024-05-01T10:00:00Z. Property names are kept in full.
Very long geometries
WKT for a detailed coastline or country border can run to hundreds of thousands of characters. Excel cuts every cell at 32,767 characters, so such geometries are damaged if the file is saved again from Excel. GIS programs read the full value.
About the formats
GeoJSON
GeoJSON is a plain-text JSON format for geographic features, standardized as RFC 7946 in 2016. It is the native format of web maps such as Leaflet, MapLibre and Mapbox, and of many APIs.
- Coordinates are WGS84 longitude, latitude (in that order).
- Points, lines and polygons can be mixed in one file.
- Properties can be any JSON value, with no limit on field name length.
CSV
CSV (comma-separated values) is a plain-text table that opens in Excel, Google Sheets and every database. It has no geometry type of its own: locations are stored either as two coordinate columns, such as latitude and longitude, or as a column of WKT text.
- Points fit in two columns (X and Y, or longitude and latitude); lines and polygons need a WKT column.
- The coordinate system is not stored in the file, so note it separately.
- There is no standard for the separator: Excel uses a comma or a semicolon depending on the language settings.
- Every value is text; whether 0800 is a number or a postcode is up to the program reading it.
Frequently asked questions
Is my GeoJSON uploaded?
No. The CSV is written by your browser on your own device, and nothing is sent anywhere.
Can I get the coordinates in another system?
Yes. Enter an EPSG code as the output coordinate system, for example EPSG:25832 for UTM zone 32N, and X and Y are written in metres. The CSV does not record the system, so the message after converting names it for you to note down.
Can I turn the CSV back into GeoJSON?
Yes, with the CSV to GeoJSON converter, which reads the X and Y columns or the WKT column.
Can I open it in Google Sheets?
Yes. In Google Sheets choose File, Import, upload the CSV and let it detect the separator. The standard style works best there.