Shapefile to GeoJSON Converter failed or looks wrong? Troubleshooting guide
Troubleshoot extensions, file structure, dependencies, encoding, memory, and output error in Shapefile to GeoJSON Converter while preserving the source.
Preserve the source first
Do not rename and overwrite the original, and do not treat a browser preview as the only acceptance record. Use a small copy and record size, producer, version, browser, and exact error.
The easy-to-miss fact for this format
For an administrative-boundary ZIP with region.shp, region.shx, region.dbf, and region.prj, first confirm matching names. After conversion, sample labels, feature count, and geographic bounds.
Recommended troubleshooting order
- Test the page example or a smaller known-good file to confirm the tool runs.
- Check extension, signature, companion files, remote URL, and CORS; exclude a downloaded HTML error page.
- Supply the input again according to the workflow:
- Choose a ZIP containing matching .shp, .dbf, .shx, and optional .prj.
- Review detected layer, feature count, geometry type, and field encoding.
- Preview bounds and sample properties to catch coordinate errors.
- Download UTF-8 GeoJSON and retain the original ZIP for traceability.
- Close memory-heavy tabs and retry in current Chrome or Edge.
- If it still fails, re-export from the producing application and validate in the receiving system.
Common questions and answers
Why use a ZIP?
SHP geometry and DBF attributes are separate; a ZIP keeps the required companions together.
Why are coordinates off the map?
The PRJ may be missing or wrong; verify the source CRS in GIS software.
Is the data uploaded?
Processing runs in this browser tab; the file is not uploaded to FreeTool to perform the task.
Limits that must not be bypassed
- Missing or wrong PRJ prevents reliable WGS84 conversion
- Unspecified DBF encoding can corrupt non-Latin text
- No geodatabase, spatial-index, or topology repair
Privacy handling
Local input is not uploaded to FreeTool for processing; remote IIIF/DZI URLs are requested by the browser from their source. Troubleshooting images, OCR text, model summaries, and converted files may contain sensitive or copyrighted content. De-identify and confirm rights before sharing.