GeoJSON to Shapefile Converter
Convert GeoJSON from web maps, APIs or Python into ESRI shapefiles for QGIS and ArcGIS. Free, private and with the projection you need.
Accepted: .geojson, .json. Up to 20.0 MB, converted on your device.
Your file never leaves your device. Nothing is stored on any server.
GeoJSON is what web maps, government open-data portals, Overpass Turbo and Python scripts produce, while many colleagues and desktop tools still expect shapefiles. Drop a .geojson or .json file here to get a proper shapefile set with a .prj, a UTF-8 .dbf and field names shortened to the 10-character limit with a mapping file.
How to convert GeoJSON to Shapefile
Drop a .geojson or .json file containing a FeatureCollection, a single Feature or a bare geometry. The map preview and layer counts confirm what was read.
Select the output coordinate system: WGS84 as in the GeoJSON, Web Mercator, or the recommended UTM zone for measuring in metres.
Click Convert and download a ZIP with one shapefile per geometry type and a field_mapping.csv listing any shortened field names.
What is a GeoJSON file?
GeoJSON is a JSON-based format for geographic features, defined in RFC 7946. It is the native format of web mapping libraries such as Leaflet and MapLibre and is supported by QGIS, ArcGIS, PostGIS and most modern tools. Coordinates are always longitude/latitude in WGS84.
What is a Shapefile?
The ESRI Shapefile is the most widely supported vector format in GIS. A "shapefile" is really a set of files with the same base name: .shp holds the geometry, .shx the index, .dbf the attribute table, .prj the coordinate system and .cpg the text encoding. Each shapefile stores a single geometry type, which is why a mixed KML becomes several shapefiles.
Why use this converter
Mixed geometry and folders handled
Mixed geometries are handled automatically. Points, lines and polygons are separated into their own layers, and you can split by folder as well.
Properties become fields
Every property becomes a .dbf column with its type inferred (text, integer, decimal, date). Nested objects are stored as JSON text so nothing is dropped, and long names are shortened with a mapping file.
Correct coordinate system
Choose the coordinate system for the output: WGS84, Web Mercator or the correct UTM zone for your area, with a proper .prj file so QGIS and ArcGIS read it correctly.
Nothing is uploaded
Everything runs in your browser. Your files are never uploaded, so confidential survey, cadastral or forestry data stays on your computer.
Frequently asked questions
Are GeoJSON properties kept as shapefile attributes?
Yes. Each property becomes a column in the .dbf; numbers, booleans, dates and text are typed accordingly and nested objects or arrays are written as JSON strings. Because DBF field names are limited to 10 characters, longer names are truncated and made unique, and the original names are listed in field_mapping.csv in the download.
Which coordinate system will the shapefile be in?
GeoJSON is defined as WGS84 longitude/latitude, so the default output is EPSG:4326 with a matching .prj. You can choose Web Mercator (EPSG:3857) or the UTM zone the tool recommends for your data if you need coordinates in metres. Files that declare an old-style crs member in another projection are flagged with a warning.
My GeoJSON mixes points, lines and polygons. How many shapefiles do I get?
One per geometry type: _points, _lines and _polygons, with empty ones skipped. GeometryCollections are split across those layers with the same attributes, and Multi* geometries become multi-part shapes.
Is the GeoJSON to SHP converter free, and is my data uploaded?
It is free and the file is never uploaded. Parsing and writing the shapefile happen in your browser, so the tool also works offline once the page has loaded.
Does the shapefile open in QGIS and ArcGIS?
Yes. You get standard .shp, .shx, .dbf, .prj and .cpg files that open in QGIS, ArcGIS Pro, ArcMap, AutoCAD Map, Global Mapper and any other software that reads ESRI shapefiles.
What about features with null geometry or 3D coordinates?
Features without geometry are skipped and counted in the notes, because a shapefile record must have a shape. Z coordinates are dropped by default; tick "Keep Z values" to write PointZ, PolyLineZ or PolygonZ shapes.