Shapefile to KML Converter
Export Shapefile archives as KML features.
Use this online tool to convert Shapefile properties to KML format quickly and securely. No files are saved on our servers.
Drag file here to convert, or select file
Supported file extension: .zip • Max 50MB
Specification Rules
- Import enterprise utility layers into Google Earth
- Share planning boundaries with customers using popular mapping tools
- Visualize cadastral datasets without requiring desktop GIS platforms
- Complex layer configurations will collapse into simplified styles
- Large regional datasets can cause rendering lag in web browsers
- Attributes map to nested table fields rather than flat key-value columns
GDAL Direct Equivalent Terminal Command
When to use this conversion
Convert when a Shapefile needs to display in Google Earth, Google My Maps, or a consumer mapping tool that doesn't read Shapefile. KML's inline styling also makes it useful for one-shot client deliverables where the symbology should travel with the file.
Technical Details
KML is typically 3–6× the size of the source Shapefile bundle. XML overhead, attribute table replication in HTML descriptions, and coordinate text formatting all inflate the output. KMZ compresses back to roughly Shapefile size.
Common Errors & Fixes
- CRS not WGS 84: KML requires lat/lon. Fix: ensure the source has a .prj or pass -s_srs EPSG:<code> -t_srs EPSG:4326 explicitly.
- Styling missing: KML output has default yellow pushpins. Fix: post-process with a templating step that injects <Style> blocks, or use the LIBKML driver with -dsco DOCUMENT_ID.
- Special characters break HTML descriptions: ampersands and angle brackets in attribute values aren't escaped. Fix: use the LIBKML driver, which handles escaping.
- Multiple geometry types collapsed into MultiGeometry: rarely what you want. Fix: explode collections with -explodecollections.
Alternative Tools
- QGIS: drag the .shp in, Export → Save Features As → KML with CRS = EPSG:4326
- ogr2ogr CLI: ogr2ogr -f KML output.kml input.shp
- ogr2ogr with LIBKML driver: ogr2ogr -f LIBKML for richer styling support
- mapshaper.org for browser-based conversion with optional simplification
Frequently Asked Questions
Can I use styling settings?
Yes. Future updates will preserve attribute tables and standard boundaries while offering basic color customization options.
Are multiple files supported inside the ZIP?
Yes, standard ESRI files (.shp, .dbf, .shx, .prj) must be bundled into a single ZIP archive to construct complete maps.
Will coordinate projections be handled automatically?
Yes. The backend will read the coordinate boundaries from projection files (.prj) and project them to the standard spherical coordinates required by KML.