Shapefile to GeoJSON Converter

The default hand-off between GIS teams who ship Shapefile and web-mapping or data teams who need GeoJSON.

Common issues converting Shapefile to GeoJSON

A Shapefile is at least three files (.shp, .shx, .dbf). Upload a zip of the whole bundle, not the .shp alone. Don't zip a containing folder — the zip should contain the components at the top level.
Attribute names in the DBF are capped at 10 characters. Those truncated names (e.g. 'PostalCode' → 'PostalCod') become your property keys. Renaming happens pre-shipping, not here.
Without a .prj file the source CRS is unknown. We assume WGS 84, which will be wrong if the file is in UTM, State Plane, or another projected system. Always include the .prj.
Shapefiles cap file size at 2 GB per component. If your .shp is larger, split it on a stable attribute (region, year) before zipping.

Frequently asked questions

Why do I need to upload a ZIP?

A Shapefile is a set of files that must travel together: .shp (geometry), .shx (index), .dbf (attributes), and ideally .prj (projection). The .shp alone is useless to any reader.

Is my file's projection handled automatically?

If a .prj is included, yes — we read its WKT, identify the CRS, and reproject to WGS 84 as required by GeoJSON. Without a .prj we fall back to assuming WGS 84, which may be incorrect.

My file has character encoding issues — what went wrong?

Legacy DBF files are often encoded in CP1252 or similar rather than UTF-8. If you see mojibake in your output strings, re-export with UTF-8 attribute encoding from your GIS tool.

What's the max shapefile size supported?

The format itself tops out at 2 GB per component. Client-side conversion in the browser works well up to ~100 MB; above that consider the API or splitting by region.