All tools
Format conversionLocal browser worker

GeoJSON to CSV Converter

Convert GeoJSON features and properties to a spreadsheet-safe CSV locally, with WKT geometry, stable columns, and a field mapping report.

Loading tool

Preparing this tool in your browser.

Preparing the local tool…

Format preservation contract

This is the converter's static format contract. The result report adds input-specific warnings, field mappings, transformations, and losses for each run.

Data areaStatusBehavior
GeometryTransformedEach non-null feature geometry is serialized to geometry_wkt; null geometry becomes blank cells, and input bbox members are reported and omitted.
AttributesConditionalPrimitive properties remain cells and nested values become stable JSON strings; foreign members not mapped by this converter are reported and omitted.
Coordinate reference systemNot supportedCSV does not embed CRS metadata; coordinates remain WGS84 longitude/latitude.
DimensionsPreservedWKT retains observed coordinate ordinates.
LayersPreservedThe normalized GeoJSON root becomes one table.
StylesNot supportedThe source format does not provide a portable style contract for this conversion.
AttachmentsNot supportedExternal attachments are outside this browser conversion.
PackagingPreservedOutput is a standalone UTF-8 CSV file.

Convert GeoJSON features to CSV

Paste or drop GeoJSON and download one CSV row per feature. Geometry is retained in a geometry_wkt column, while feature identifiers, geometry types, and properties become stable tabular columns. The conversion runs locally and includes a report for renamed fields, serialized values, null geometry, and other losses.

The reader accepts a GeoJSON Geometry, Feature, or FeatureCollection and normalizes it to one layer. RFC 7946 longitude/latitude coordinates pass through without reprojection. Legacy non-WGS84 CRS declarations are rejected rather than being written into a misleading CSV.

Worked example

Input:

{
  "type": "Feature",
  "id": "parcel-7",
  "properties": { "name": "North field", "score": 0.92 },
  "geometry": { "type": "Point", "coordinates": [12.55, 55.68] }
}

Output columns:

feature_id,geometry_type,geometry_wkt,name,score
parcel-7,Point,POINT (12.55 55.68),North field,0.92

Input-specific considerations

The canonical preservation contract above describes the format-level behavior. For a specific input, feature IDs are written to feature_id with a deterministic fallback, while geometry_type and geometry_wkt make the output schema explicit. Null geometry stays in its row with blank geometry cells and a reported warning.

Property columns are collected across the full layer and sorted deterministically. A source property that collides with a reserved converter column is renamed to property_<name> with a numbered suffix when needed. Suspicious spreadsheet-formula strings are escaped by default, while actual negative numbers remain numeric. Input bbox values and foreign members whose semantics are not mapped by this converter are omitted and listed in the downloadable report.

Limits and privacy

These values are the effective central browser-worker limits for this page:

Runtime limitExact value
Input size (maxInputBytes)26214400 bytes (25 MiB)
Features (maxFeatures)25000
Coordinate positions (maxCoordinatePositions)2000000
Property fields (maxPropertyFields)2048
Serialized properties (maxPropertyBytes)16777216 bytes (16 MiB)
Geometry/property nesting (maxNestingDepth)64 levels
Hard timeout (timeoutMs)60000 ms (60 seconds)

Files, property values, coordinates, and filenames are never uploaded or included in analytics.

Run the GeoJSON Validator first when coordinate order or geometry validity is uncertain. Use WKT to KML for a Google Earth handoff or Shapefile to KMZ for a multi-file GIS source. See GIS-ready export workflow guidance for downstream considerations.

FAQ

Does this create longitude and latitude columns?

The default preserves every supported geometry type in one WKT column. Point coordinates remain available inside the WKT without pretending that lines or polygons have one authoritative longitude and latitude.

What happens to nested properties?

Objects and arrays are JSON-encoded into their CSV cells. The conversion report identifies those fields so the transformation is not silent.

Is the CSV safe to open in spreadsheet software?

Strings beginning with spreadsheet formula prefixes are escaped by default. Actual numeric values, including negative numbers, remain numeric.

Does this upload the GeoJSON?

No. Reading, schema inference, WKT serialization, and CSV generation happen in a browser worker on your device.

Related tools