GeoJSON to CSV

updated 25 April 2026

Before you start

You need a GeoJSON FeatureCollection or a list of individual Feature objects. You can either paste the raw JSON text into the input pane or drop a .geojson (or .json) file directly onto the page.

The tool works by "flattening" your spatial data. It scans every feature to find every possible key in the properties object. These keys become your CSV columns. If one feature has a "population" property and another doesn't, the latter will simply have an empty cell in that column.

Everything happens locally in your browser. I don't see your data, and nothing is sent to a server. While there isn't a hard file size limit, very large collections (500 MB+) might make your browser sweat as it tries to build the final CSV string in memory.

How to use it

1. Paste your GeoJSON into the left pane, or drop a file anywhere on the input area.
2. Click Convert to start the flattening process.
3. Check the status bar to see how many features were successfully processed into rows.
4. Use Copy CSV to grab the text, or Download .csv to save the file for use in Excel or Google Sheets.
5. If you need to start over, the Clear button wipes both panes and the internal session cache.

Example

Input (GeoJSON Feature):

{
  "type": "Feature",
  "geometry": { "type": "Point", "coordinates": [-122.4, 37.7] },
  "properties": { "name": "Coffee Shop", "rating": 4.5 }
}

Output (CSV):

name,rating,lng,lat,wkt
Coffee Shop,4.5,-122.4,37.7,"POINT(-122.4 37.7)"

Notice how the geometry is split into simple lng/lat columns for points, while also providing a full wkt string for spatial databases.

Tips & common pitfalls

• WKT is your friend. The wkt (Well-Known Text) column is a standard format. You can import this CSV directly into QGIS, PostGIS, or DuckDB's spatial extension, and they will recognize the geometries instantly.
• Point-specific columns. The lng and lat columns only populate for Point geometries. For Polygons or LineStrings, these cells will be empty, as those shapes don't have a single coordinate pair.
• Nested properties are tricky. If your properties contain nested objects (e.g., "owner": {"name": "Bob"}), this tool will stringify them into a single cell. You might need to flatten your JSON structure before converting if you want "owner.name" as its own column.
• Coordinate order. Per the GeoJSON spec (RFC 7946), coordinates are always [longitude, latitude]. The CSV output respects this, naming the columns lng and lat to avoid confusion.

Troubleshooting

Related tools

• CSV to GeoJSONThe reverse direction — turn a lat/lng or WKT CSV back into a FeatureCollection.
• GeoJSON ViewerMap your data instantly to see if the geometry is correct.
• GeoJSON ValidatorCatch syntax errors or spec violations before converting.
• GeoJSON to KMLConvert to KML if you're heading toward Google Earth.

See also: if you need to do something adjacent on this site, try CSV to GeoJSON to convert a CSV with lat/lng or WKT columns back into GeoJSON, GeoJSON to KML to convert GeoJSON to KML for Google Earth, or GPX to GeoJSON to turn GPX tracks into GeoJSON.

Frequently asked questions