FileBrixNo upload · Private
Processed locally — your file never leaves your device

Shapefile to GeoJSON Converter

Convert a zipped Esri Shapefile to GeoJSON in your browser, reprojecting it to WGS84 automatically — nothing is uploaded.

Drop a GeoJSON, TopoJSON, KML, KMZ, GPX, zipped Shapefile or CSV file hereor click to choose a file from your deviceNothing is uploaded — the file is detected and processed entirely on your device.

How it works

  1. Select or drop a .zip containing your shapefile (.shp, .dbf, .shx and ideally .prj).
  2. Your browser unpacks the archive and reads the geometry and attribute table locally.
  3. If a .prj is present, coordinates are reprojected to WGS84 so the result is valid GeoJSON.
  4. Download the resulting .geojson file, or switch to the View tab to see it on a map first.

Frequently asked questions

Why do I need to upload a ZIP instead of the .shp file?
A shapefile isn't a single file. Geometry lives in the .shp, attributes in the .dbf, and the coordinate system in the .prj. A .shp on its own has no attribute data and no way to know where on Earth it belongs, so the whole set has to travel together — which is why shapefiles are almost always distributed as a ZIP.
Is my shapefile uploaded anywhere?
No. The archive is unpacked and converted entirely in your browser. Nothing is sent to a server at any point.
What happens to the coordinate system?
If the ZIP contains a .prj file, the coordinates are reprojected to WGS84 (longitude/latitude), which is what GeoJSON requires. National grids such as the Czech S-JTSK/Krovak, British National Grid and UTM zones are all handled. Without a .prj, coordinates are passed through unchanged, since guessing a projection would silently move your data.
Are attributes from the .dbf kept?
Yes. Every attribute column becomes a property on the matching GeoJSON feature.
Can I convert GeoJSON back to a Shapefile?
Not currently. Writing a shapefile means producing four separate files with fixed-width columns and a 10-character limit on field names, which would silently truncate longer property names. Rather than ship a lossy export, this tool is read-only for now.