SHP to GeoJSON Converter
Processing entirely on your device — large files may take a moment.
SHP is the ESRI shapefile — the decades-old GIS standard that still carries most government and research map data (usually zipped with .dbf/.prj siblings). Convert SHP/KML/GPX into GeoJSON to feed Leaflet, Mapbox or any web map.
Because the whole conversion happens on your device, it is instant, unlimited and genuinely private — no accounts, no watermarks, no files on anyone's server. Multiple files are converted in one go.
How SHP compares to GeoJSON
| SHP | GeoJSON | |
|---|---|---|
| Structure | Geometry + DBF attribute table | FeatureCollection JSON |
| Types / schema | Points, polylines, polygons | Point / LineString / Polygon |
| Compatibility | ArcGIS, QGIS, OSM exports | Leaflet, Mapbox, QGIS, PostGIS |
| Best for | Government & research map data | Web maps and data pipelines |
How to convert SHP to GeoJSON
- 1
Select your files
Drag & drop your SHP files onto the area above, or click to browse. You can add multiple files at once for batch conversion.
- 2
Convert instantly
Click "Convert to GeoJSON". The conversion runs entirely inside your browser using WebAssembly — no upload, no queue, no waiting.
- 3
Download results
Download each converted GeoJSON file individually, or grab everything at once as a ZIP archive.
About the SHP format
The ESRI shapefile is the cockroach of GIS formats — designed in 1998, immune to extinction. Governments, research institutes andOpenStreetMap exports still ship as .shp, almost always zipped together with .dbf (attributes), .shx (index) and .prj (projection) siblings.
The browser can read the whole bundle: unzip it, parse the geometry records and the DBF attributes, and you get a clean GeoJSON or a flat CSV — no QGIS install required for a quick look.
+ Strengths
- ✓The lingua franca of public GIS data
- ✓Attributes and geometry in one bundle
- ✓Reads in every serious GIS tool
! Limitations
- −Multi-file bundle, awkward to move
- −2GB size limit and field-name limits
- −No web map support without conversion
About the GeoJSON format
GeoJSON is the map format the web agreed on: a FeatureCollection of points, lines and polygons, each carrying arbitrary properties, in plain JSON. Leaflet, Mapbox, D3, QGIS and PostGIS all consume it directly, which is why almost every GIS workflow ends with “export as GeoJSON”.
Converting the older formats into GeoJSON (SHP, KML, GPX) is the bridge from institutional and device data into anything a browser can draw.
+ Strengths
- ✓Consumed by every web mapping library
- ✓Plain JSON — easy to filter and edit
- ✓Properties travel with the geometry
! Limitations
- −Verbose for huge datasets
- −No built-in styling or symbology
Why convert SHP to GeoJSON?
Think of it as moving your file to the container that fits the job. Multi-file bundle, awkward to move GeoJSON works differently: Consumed by every web mapping library If any of that sounds like your task, run the conversion — it takes seconds and nothing leaves your device.
Frequently asked questions
Is this SHP to GeoJSON converter really free?
Yes — completely free, with no sign-up, no watermark and no daily conversion limits. The site is supported by advertising.
Are my files uploaded to a server?
No. The conversion runs entirely inside your browser using WebAssembly, so your files never leave your device — that is what makes it instant and private.
Does it work on Windows, Mac, iPhone and Android?
Yes. Anything with a modern browser works: Windows, macOS, Linux, Android and iOS. No software installation is required.
Is there a file size limit for SHP to GeoJSON?
The only limit is your device's memory, since nothing is uploaded. Files up to a few hundred megabytes work fine on a modern desktop browser; very large files simply take a little longer.
How large can my SHP file be?
Since everything runs locally in your browser, the real limit is your device memory rather than an upload cap. Files up to a few hundred megabytes are usually fine on a modern computer; extremely large ones simply take longer.
Is my data safe here?
Yes. The conversion is plain JavaScript running in your tab: the data is parsed and re-serialized in memory, never sent anywhere, and disappears when you close the page.