Convert a Shapefile ZIP to KMZ
Drop a ZIP archive containing Shapefile sidecars, select the dataset when the archive contains more than one, choose the property used for placemark names, and download a KMZ with doc.kml. The browser inspects the archive before decoding it and keeps the source files local.
Shapefiles are multi-file datasets. Files are matched by basename, so parcels.shp, parcels.dbf, parcels.prj, and parcels.cpg are treated as one layer. A ZIP containing roads.* and parcels.* presents two separate layer choices instead of silently mixing their records.
Expected archive
parcels.zip
├── parcels.shp required geometry
├── parcels.dbf optional attributes
├── parcels.shx optional index
├── parcels.prj coordinate reference system
└── parcels.cpg attribute text encoding
If the projection file is absent, conversion pauses until you explicitly confirm that the coordinates are already WGS 84 longitude/latitude. Unknown projections are blocked rather than guessed.
Worked example
Suppose parcels.zip contains separate parcels and roads datasets. The
parcels dataset has one point at longitude 12.55, latitude 55.68. Its DBF row
has parcel_id=parcel-7 and name=North field, while parcels.prj declares
WGS 84. Select parcels as the dataset and name as the placemark-name field.
The downloaded KMZ contains one root file, doc.kml, with a concrete placemark
equivalent to:
<Placemark>
<name>North field</name>
<ExtendedData>
<Data name="parcel_id"><value>parcel-7</value></Data>
</ExtendedData>
<Point><coordinates>12.55,55.68</coordinates></Point>
</Placemark>
The accompanying report identifies parcels as the selected layer, records the
WGS 84 CRS normalization, and lists the DBF-to-ExtendedData field mapping.
Input-specific considerations
Archive contents determine the per-run result. Missing DBF data does not block geometry conversion, but it leaves the output without source attributes. DBF records marked as deleted are omitted, blank values are normalized, and precision-sensitive numbers may remain text. The canonical preservation contract above describes format-level behavior; the downloadable report lists the selected layer, field mappings, skipped records, coordinate dimensions, and reprojection observed for this archive.
Archive safety and limits
These are the effective central browser-worker and bounded-archive limits:
| Runtime limit | Exact value |
|---|---|
Compressed input (maxInputBytes) | 26214400 bytes (25 MiB) |
Expanded archive (maxExpandedArchiveBytes) | 104857600 bytes (100 MiB) |
Archive entries (maxArchiveEntries) | 128 |
Expansion ratio (maxArchiveCompressionRatio) | 200:1 |
Features (maxFeatures) | 25000 |
Coordinate positions (maxCoordinatePositions) | 2000000 |
DBF/property fields (maxPropertyFields) | 2048 |
Serialized properties (maxPropertyBytes) | 16777216 bytes (16 MiB) |
Geometry/property nesting (maxNestingDepth) | 64 levels |
Hard timeout (timeoutMs) | 60000 ms (60 seconds) |
Nested and encrypted archives are rejected, as are unsafe paths and archives
without a .shp dataset.
Use WKT to KML for a single text geometry or GeoJSON to CSV for an attribute-table handoff. If the source imagery needs inspection first, open the GeoTIFF Inspector. For workflow context, read GIS export software guidance.
FAQ
Does the Shapefile leave my browser?
No. Archive inspection, reprojection, KML serialization, and KMZ packaging run locally in a browser worker.
Must the ZIP contain a DBF file?
No. Geometry can be converted without it, but attributes and placemark-name choices will be unavailable and the loss is reported.
What happens when the ZIP contains several Shapefiles?
They are grouped by matching basename. You must choose the layer to convert; the tool does not silently merge unrelated datasets.
Why can KMZ look different from the source GIS layer?
Shapefile does not carry the complete styling configuration from a GIS project. KMZ receives the geometry and supported attributes, not external symbols, labels, or project-specific render rules.