Live Online ConverterChannel: kmlshapefile

KML to Shapefile Converter

Convert visual markup maps into standard database shapes.

Move markup layers out of visual scopes into database environments. This tool will convert KML datasets into standardized ESRI Shapefiles bundled within a ZIP archive containing all necessary mapping and data files.

Drag file here to convert, or select file

Supported file extension: .kml • Max 50MB

Channel: Direct Stream ModeGDAL Driver Operational

Specification Rules

  • Export routes drawn in Google Earth into municipal planning systems
  • Convert raw spatial markers into GIS features
  • Import field survey tracks from KML sources into CAD environments
  • Attribute structures must be flattened to match the 10-character limit of dBASE files
  • Complex nested XML folder structures are simplified with each conversion
  • Multigeometry features must fit into unified coordinate structures

GDAL Direct Equivalent Terminal Command

sh — gdalready
$ogr2ogr -f "ESRI Shapefile" output_folder input.kml

When to use this conversion

Convert when KML data needs to enter a traditional desktop GIS pipeline (ArcGIS, QGIS) or a legacy tool that only reads Shapefile. Useful when a client delivered a Google Earth export and your downstream workflow predates GeoPackage.

Technical Details

GDAL parses the KML, drops styling, and writes the geometry plus name/description as a Shapefile bundle. The .dbf is created with 10-character truncated field names; KML's description balloon HTML is stripped to plain text. The CRS is fixed to WGS 84 because KML carries no other CRS option.
Output file size

Shapefile bundle is typically 20–40% the size of the source KML. Binary .shp/.dbf is much more compact than KML XML; the difference is largest for files with many small features.

Common Errors & Fixes

  • Field names truncated: KML's long property names are cut to 10 chars in dBASE. Fix: rename properties in the KML first, or accept the truncation.
  • Description HTML lost: rich content becomes plain text. Fix: prefer GeoPackage as the target if descriptions matter.
  • Mixed geometry types: a single KML can have points, lines, and polygons; a Shapefile cannot. Fix: split into separate Shapefiles per geometry type.
  • Encoding garbled: non-ASCII names lose accents because the .dbf has no .cpg. Fix: add a .cpg file containing "UTF-8" after conversion.

Alternative Tools

  • QGIS: open the .kml, Export → Save Features As → ESRI Shapefile
  • ogr2ogr CLI: ogr2ogr -f "ESRI Shapefile" output_dir input.kml
  • togeojson + shp-write (npm) for JavaScript pipelines
  • mapshaper for conversion with attribute name cleanup

Frequently Asked Questions

Will the output contain all parts of a Shapefile?

Yes. The tool compiles and archives .shp, .shx, .dbf, and .prj coordinate documents into a single download package.

How are properties from visual descriptions handled?

Visual text descriptions are parsed and written as single columns in flat database attribute tables.

What coordinate system is used for exports?

The export maps coordinates to standard WGS 84 (EPSG:4326), but we can adjust target projections using coordinate flags.

Related Transformations Map