GeoJSON to Shapefile Converter
Required whenever a downstream consumer — enterprise GIS, government portal, engineering firm — mandates Shapefile delivery.
Convert GeoJSON to Shapefile now
Common issues converting GeoJSON to Shapefile
- A Shapefile can only hold one geometry type. If your GeoJSON mixes Points, Lines, and Polygons, split into three FeatureCollections and convert each separately.
- Property names longer than 10 characters are truncated silently by the DBF format. Rename long keys before conversion if the exact names matter downstream.
- Only scalar property types are supported. Nested objects/arrays get serialized to JSON strings inside a text column; consumers must re-parse.
- The output is always zipped — the four companion files must travel together. Don't rename the zip or extract it before delivery, or ArcGIS won't recognize it.
Frequently asked questions
Why does the output come packaged as a ZIP?
A Shapefile is four files (.shp, .shx, .dbf, .prj) that must stay together. Zipping is the standard delivery format and preserves the bundle.
What happens to property names longer than 10 characters?
They're truncated by the DBF spec to 10 characters. Rename long keys in your GeoJSON before conversion if you need to control the truncation.
Can I export mixed geometry types?
No. The format permits exactly one geometry type per Shapefile. Split the FeatureCollection by geometry type and convert each separately.
What CRS does the output use?
WGS 84 (EPSG:4326), pinned in the .prj. Modern versions of ArcGIS won't load a projectionless shapefile, so the .prj is always written.