GeoJSON to Shapefile Converter
Convert web JSON spatial objects into localized shape components.
Transfer coordinates from web environments back to standard offline databases. This upcoming converter parses flat JSON coordinate arrays and packages them into a ZIP archive containing all required ESRI components.
Drag file here to convert, or select file
Supported file extension: .geojson, .json • Max 50MB
Specification Rules
- Convert crowdsourced web mappings into formats compatible with professional GIS suites
- Save geometries generated in JavaScript environments directly to offline systems
- Translate spatial properties back to local CAD setups
- Attributes field key names must be truncated to 10 characters
- Does not support nested JSON objects within attributes
- Large files are subject to browser session upload limits
GDAL Direct Equivalent Terminal Command
When to use this conversion
Convert when your downstream consumer requires Shapefile — a public-sector procurement, a legacy ArcGIS 10.x installation, or an external partner stuck with an old workflow. Avoid this conversion for new projects: GeoPackage is a strictly better target.
Technical Details
Shapefile bundle is typically 25–40% the size of the source GeoJSON. Binary geometry plus terse dBASE attribute storage drops the JSON text overhead.
Common Errors & Fixes
- Field names truncated and collide: "population_2020" and "population_2025" both become "populatn_2". Fix: rename to short unique names before export.
- Nested JSON properties stringified: arrays and objects become text. Fix: flatten the JSON structure before conversion.
- Mixed geometries fail: a FeatureCollection with both points and polygons cannot become a single Shapefile. Fix: split per geometry type with multiple ogr2ogr runs.
- Output is a folder, not a file: Shapefile needs all four sidecars. Fix: ZIP them together and confirm files sit at the archive root.
Alternative Tools
- QGIS: open the .geojson, Export → Save Features As → ESRI Shapefile
- ogr2ogr CLI: ogr2ogr -f "ESRI Shapefile" output_dir input.geojson
- shp-write (npm) for in-browser conversion
- mapshaper for cleanup before export, especially attribute renaming
Frequently Asked Questions
Why are attribute column names altered?
Shapefile uses the legacy dBASE format for attribute tables, which limits database field column headers to 10 characters.
How does the tool handle missing projections?
By default, the converter writes standard WGS 84 system data unless explicit projection files are supplied.
Are multiple coordinate definitions supported?
Yes, standard spatial geometries like lines and polygons are fully mapped during the conversion.