Free · No signup · Browser-based

Convert GeoJSON to CSV.

Paste a GeoJSON FeatureCollection, get one row per feature. Coordinates are split into latitude/longitude columns. Nested properties get flattened with dot notation.

01 · How it works

Three steps, then done.

The other direction from CSV to GeoJSON — useful for getting map data into a spreadsheet or BI tool. For Point features, longitude/latitude/elevation become explicit columns. For other geometries (LineString, Polygon, MultiPoint), the geometry is JSON-stringified into a single 'geometry' column. Properties are flattened with dot notation.

i. drop

Drop or paste

Drag a file, click to choose, or paste data directly into the input pane.

ii. detect

We read the shape

Types are inferred so the output is correctly formatted — not strings everywhere.

iii. use it

Copy, download, or dashboard

Copy the output, download it, or hit 'Build dashboard' to chart what's in the data.

02 · Why ours

Smart CSV conversion by default.

Free CSV converters often produce sloppy output — every value quoted, types lost, errors swallowed. Ours infers types where it can, fails loudly when it can't, and pairs the conversion with a one-click path to a dashboard.

  • 01

    Correct types

    Numbers, booleans and dates are detected as you import, so the CSV (and any dashboard built from it) treats them correctly — not everything as text.

  • 02

    Local-first

    Your file is parsed and converted in your browser — verify in DevTools → Network. Nothing is uploaded, logged, or stored.

  • 03

    Fails loudly

    Malformed input gives a clear, specific error instead of silently wrong output — so you can trust what comes back.

  • 04

    One click to a dashboard

    Every conversion keeps a tabular copy, so you can send the data straight to our visualization tool to chart it.

"Needed a conversion. Ended up with a dashboard. That's the pattern."
— the typical csvtodashboard arc
03 · FAQ

geojson to csv questions.

Which geometry types are handled?
Point features get their coordinates split into latitude, longitude, and optional elevation columns. LineString/Polygon/MultiPoint/etc. have their geometry stringified into a single column — you'd need a tool that understands the wider geometry to use it.
Yes — same dot notation as our JSON to CSV converter (e.g. properties.address.city becomes a column).
Properties are still output; the geometry columns are blank.
Both — a single Feature becomes a one-row CSV; a FeatureCollection becomes one row per feature.