Convert map files like a GIS power user.
Turn CSV coordinates, GeoJSON, KML and GPX into clean GeoJSON, CSV, KML or Shapefile ZIP outputs. Built for quick browser-based GIS workflows without making users feel lost.
Turn CSV coordinates, GeoJSON, KML and GPX into clean GeoJSON, CSV, KML or Shapefile ZIP outputs. Built for quick browser-based GIS workflows without making users feel lost.
Start with the converter above. These answers explain supported inputs, privacy and output options.
Yes. Upload the complete Shapefile as a ZIP containing the SHP, SHX and DBF components.
The workflow supports CSV coordinates, GeoJSON, KML, GPX and zipped Shapefiles.
The converter keeps feature properties where the target format supports them.
Map files, coordinates and GIS data
Upload a supported map file, preview what is inside and export a clean GIS-ready result. Shapefile downloads are packaged as a ZIP with the files GIS software expects.
CSV, GeoJSON, JSON, KML or GPX. GeoPackage and Shapefile ZIP input are planned.
No file loaded.
BulkConverter reads the file locally and gives you a quick quality check before exporting.
| Upload a file to see the first features here. |
Export the result directly from your browser. Shapefile output is always downloaded as a ZIP.
Idle.
Shapefile is an older format. BulkConverter creates a ZIP with .shp, .shx, .dbf, .prj and .cpg files. Field names are shortened to 10 characters for compatibility.
GeoPackage conversion is planned for a later, heavier workflow. That version should support layer selection, larger files and better handling for complex GIS datasets.
Yes. Upload a CSV, choose your longitude and latitude columns, select Shapefile ZIP and download a ZIP that includes the expected shapefile components.
Yes. Point, line and polygon GeoJSON datasets can be exported to Shapefile ZIP. Mixed geometry files should be split first.
Yes. KML and GPX can be read and exported to GeoJSON, CSV, KML or Shapefile ZIP where the geometry is compatible.
Not yet in the browser version. GeoPackage is planned for a later workflow because it requires heavier GIS database handling.