CSV to GeoJSON

updated 28 April 2026

Before you start

You need a CSV (comma, tab, semicolon, or pipe-separated — the parser sniffs the delimiter from the header row) with one of:

• A pair of latitude / longitude columns. I look for lat, latitude, y, lat_dd for the Y axis and lng, lon, long, longitude, x, lon_dd for the X axis. Names are matched case-insensitively.
• Or a WKT column (Well-Known Text) holding the geometry. I check headers wkt, geometry, geom, the_geom, shape. The parser handles POINT, LINESTRING, POLYGON, and the multi-variants.

If your headers don't match the auto-detect list (e.g. you exported from a system that uses POINT_X/POINT_Y), type the exact header name into the override boxes above the panes and the converter will use those.

Everything happens in your browser. I don't see your file. There's no hard size limit — the CSV is parsed in a single pass — but tens of millions of rows will eventually exhaust the tab's memory.

How to use it

1. Paste your CSV into the left pane, or drop a .csv / .tsv file.
2. If your column names are unusual, type them into lng col, lat col, or WKT col. Otherwise leave them empty for auto-detect.
3. Click Convert.
4. Review the right pane. The status bar reports how many features were built and how many rows were skipped (e.g. blank coordinates).
5. Click Copy or Download .geojson. The result is also stashed in your session, so you can hop straight to the Viewer.

Options explained

lng / lat overrides

Use these when your CSV uses headers I don't recognize (e.g. POINT_X, centroid_lon, or a localized name). Type the header verbatim. The match is case-insensitive but otherwise exact — a leading or trailing space in the header still works because I trim both sides.

WKT override

Set this when your geometry column has a non-standard name. WKT takes precedence over lat/lng on a per-row basis — if a row has a valid WKT value, I use that; if it's blank or unparseable, I fall back to lat/lng for that row.

Example

Input (CSV with mixed Point + Polygon data via WKT):

name,population,wkt
Lake,0,"POLYGON((-122.5 37.7,-122.4 37.7,-122.4 37.8,-122.5 37.8,-122.5 37.7))"
Coffee Shop,1,"POINT(-122.4 37.7)"

Output (GeoJSON):

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": { "name": "Lake", "population": "0" },
      "geometry": {
        "type": "Polygon",
        "coordinates": [[[-122.5,37.7],[-122.4,37.7],[-122.4,37.8],[-122.5,37.8],[-122.5,37.7]]]
      }
    },
    {
      "type": "Feature",
      "properties": { "name": "Coffee Shop", "population": "1" },
      "geometry": { "type": "Point", "coordinates": [-122.4, 37.7] }
    }
  ]
}

Notice that the spatial column (wkt) is consumed by the geometry and removed from properties, while everything else carries through verbatim.

Tips & common pitfalls

• Coordinate order is the #1 footgun. CSV exports vary wildly — some use lat, lng, some use lng, lat. I match by column name, not position, so as long as your header is honest, the output is correct. If your points show up off Madagascar instead of in Texas, you probably mislabeled a column.
• Numbers in quotes are fine. A cell like "-122.4" parses cleanly. Locale-formatted numbers like -122,4 (European decimals) do not — convert those to dot-decimals first.
• Null-ish values are tolerated. Cells equal to NULL, N/A, NA, None, or \N are treated as missing. Rows with no usable geometry are skipped (counted in the status bar) instead of producing broken features.
• WKT with Z/M ordinates. If you have POINT Z(1 2 3) or POINT M, the Z/M flag is recognized but only X and Y are kept. Add an elevation property column if you need to preserve altitude.
• Property values stay as strings. CSV has no real type system, so I leave numbers and booleans as strings. If your downstream tool needs typed properties, transform them after the conversion.

Troubleshooting

Related tools

• GeoJSON to CSVThe reverse — flatten a FeatureCollection back to a spreadsheet.
• GeoJSON ViewerRender the converted CSV on a map in one click.
• GeoJSON ValidatorCheck the result against RFC 7946 before shipping it downstream.
• GeoJSON to KMLPush the converted points into Google Earth.

See also: if you need to do something adjacent on this site, try GeoJSON to CSV to flatten a feature collection back into a CSV table, GeoJSON Viewer to map your converted data, or GeoJSON Validator to lint the result.

Frequently asked questions