Which columns become latitude and longitude?

When converting GeoJSON to CSV, every Point feature's coordinates fill two fixed columns: latitude (the second coordinate value) and longitude (the first). Converting the other way, the tool auto-detects columns named lat, latitude, y, lon, lng, longitude, or x and uses them as the point coordinates.

How are non-point geometries handled?

Lines, polygons, multipolygons, and geometry collections cannot be reduced to a single latitude/longitude pair, so their exact shape is preserved as a compact GeoJSON string in a geometry column. The latitude and longitude cells stay empty for those rows so no coordinate data is lost.

What happens to my GeoJSON properties in the CSV?

Every property key found across the features becomes its own column, in first-seen order, and each feature's values are written into those columns. Missing properties are left as empty cells, so features with different property sets still line up correctly.

Which CSV column names are detected as coordinates?

The converter recognizes common latitude names (lat, latitude, y) and longitude names (lon, lng, longitude, x), case-insensitively. Every remaining column is kept as a feature property, so an id or name column carries straight through to the GeoJSON.

Is my data uploaded when I convert it?

No. The GeoJSON to CSV and CSV to GeoJSON conversions run entirely in your browser, so your coordinates and properties are processed locally and never leave your device.

GeoJSON to CSV Converter

Convert GeoJSON to CSV and CSV back to GeoJSON in your browser. Your coordinates stay on your device.

Your GeoJSON and CSV are converted locally in your browser and never uploaded, so location data in your features stays on your device.

Need CSV from JSON instead? Try JSON to CSV.

About GeoJSON to CSV

This GeoJSON to CSV converter flattens a GeoJSON FeatureCollection into a spreadsheet-ready table and rebuilds GeoJSON from a CSV of coordinates. Going GeoJSON to CSV, every Point feature becomes one row: its coordinates fill dedicated latitude and longitude columns, and each feature property becomes its own column in a stable order. Non-point geometries such as lines and polygons keep their exact shape in a compact geometry column so nothing is lost. Switch direction and a CSV with latitude and longitude columns is turned back into a FeatureCollection, with the remaining columns preserved as feature properties. It is handy for opening map data in Excel or Google Sheets, importing survey exports, or prepping coordinates for a mapping library. The conversion runs entirely in your browser, so the data you paste is processed locally and never leaves your device.

Features

Converts a GeoJSON FeatureCollection to CSV with dedicated latitude and longitude columns
Flattens every feature property into its own column using a stable, first-seen order
Preserves lines, polygons, and other non-point geometries in a compact geometry column
Rebuilds a GeoJSON FeatureCollection from any CSV that has latitude and longitude columns
Auto-detects coordinate columns named lat, latitude, y, lon, lng, longitude, or x
Keeps every non-coordinate CSV column as a feature property
Applies RFC 4180 quoting so values with commas, quotes, or newlines stay intact
Copy the result or download it as a .csv or .geojson file with one click

How to use the GeoJSON to CSV

Pick a direction: GeoJSON → CSV or CSV → GeoJSON.
Paste your data into the input box, or use Choose file to load a .geojson, .json, or .csv file.
Read the converted output in the panel on the right.
Click Copy to grab the result, or download it as data.csv or data.geojson.

Example

Input

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": { "name": "Eiffel Tower", "city": "Paris" },
      "geometry": { "type": "Point", "coordinates": [2.2945, 48.8584] }
    }
  ]
}

Output

latitude,longitude,name,city
48.8584,2.2945,Eiffel Tower,Paris

Each Point feature becomes a row; coordinates fill latitude and longitude, properties become columns.

Common errors & troubleshooting

CSV → GeoJSON reports "No latitude/longitude columns found". — Rename your coordinate columns to something recognizable, such as latitude and longitude (lat, y, lon, lng, and x also work), so the converter can locate them.
The GeoJSON → CSV output has empty latitude and longitude cells. — Those rows are non-point geometries; their shape is kept in the geometry column instead. Only Point features fill the latitude and longitude columns.
The converter shows "Invalid JSON" for GeoJSON → CSV. — Check that the input is valid GeoJSON — a FeatureCollection, Feature, or Geometry object with matching braces and quoted keys.
A CSV value that contains a comma spills into the next column. — Wrap that value in double quotes in the source CSV; on export the converter quotes such values automatically.

Frequently asked questions

Which columns become latitude and longitude?: When converting GeoJSON to CSV, every Point feature's coordinates fill two fixed columns: latitude (the second coordinate value) and longitude (the first). Converting the other way, the tool auto-detects columns named lat, latitude, y, lon, lng, longitude, or x and uses them as the point coordinates.
How are non-point geometries handled?: Lines, polygons, multipolygons, and geometry collections cannot be reduced to a single latitude/longitude pair, so their exact shape is preserved as a compact GeoJSON string in a geometry column. The latitude and longitude cells stay empty for those rows so no coordinate data is lost.
What happens to my GeoJSON properties in the CSV?: Every property key found across the features becomes its own column, in first-seen order, and each feature's values are written into those columns. Missing properties are left as empty cells, so features with different property sets still line up correctly.
Which CSV column names are detected as coordinates?: The converter recognizes common latitude names (lat, latitude, y) and longitude names (lon, lng, longitude, x), case-insensitively. Every remaining column is kept as a feature property, so an id or name column carries straight through to the GeoJSON.
Is my data uploaded when I convert it?: No. The GeoJSON to CSV and CSV to GeoJSON conversions run entirely in your browser, so your coordinates and properties are processed locally and never leave your device.

Related tools

JSON to CSV — Convert an array of flat JSON objects to CSV.
GPX to GeoJSON — Convert GPX to GeoJSON and back — GPS tracks, routes and waypoints to GeoJSON features, or GeoJSON back to a GPX file.
KML to GeoJSON — Convert KML ⇄ GeoJSON — turn Google Earth KML into GeoJSON for web maps, or GeoJSON back into KML.
WKT to GeoJSON — Convert WKT (Well-Known Text) to GeoJSON and back, in your browser.
JSON Formatter — Beautify, minify and validate JSON with error locations.
Coordinate Map Viewer — Plot a latitude/longitude on an OpenStreetMap map, or click the map to read coordinates back out.