Free online KMZ to PLY converter

A mapping or surveying program may deliver a 3D building or terrain model as a KMZ archive, while a scanner, mesh editor, or 3D-printing workflow may require PLY. Converting it extracts the model mesh, but does not preserve the complete geographic scene.

What the KMZ format is

KMZ is a ZIP-compressed geographic archive used by Google Earth, GIS applications, and mapping or surveying software. It normally contains a KML file plus referenced assets such as Collada .dae geometry, image textures, icons, placemarks, paths, polygons, camera views, and geographic metadata.

A KMZ may contain a textured building or terrain model, but it may also contain only geographic features and no 3D surface. A KML <Model> element usually identifies the embedded geometry through an <href> reference to a .dae file. Some archives use external references or other model formats, so the required geometry may not be present inside the archive.

What the PLY format is

PLY, also called Polygon File Format or Stanford Triangle Format, stores polygon or triangle meshes as vertices and face indices. It supports ASCII and binary encoding and can store optional vertex normals, vertex colors, and application-dependent properties such as texture coordinates.

PLY is read by MeshLab, Blender, CloudCompare, 3D-scanning and photogrammetry software, and many 3D-printing tools. Binary PLY is usually smaller and faster to load than ASCII PLY, while ASCII is easier to inspect manually. PLY does not retain KML placemarks, geographic reference systems, altitude modes, camera views, or the original KMZ scene hierarchy.

How to convert KMZ to PLY

1. Extract the archive. Make a backup, then rename model.kmz to model.zip and extract it with an archive utility. On systems with the unzip command, use unzip model.kmz -d model_kmz.
2. Find the model reference. Open doc.kml in a text editor and inspect the <Model> element and its <href> value. Follow that relative path to the referenced .dae file. If the KML has no model reference or the referenced file is unavailable, it cannot produce a mesh without another GIS or modeling workflow.
3. Keep assets together. Preserve the extracted folder structure and keep the DAE file beside its referenced texture images. Missing textures do not normally prevent geometry import, but they remove the model's visual appearance.
4. Import the geometry. In MeshLab, use File → Import Mesh and select the DAE file. In a Blender version that includes the Collada importer, use File → Import → Collada (.dae). Blender versions and installations differ, so use MeshLab or an available Collada importer when that menu is absent.
5. Clean the scene. Remove cameras, lights, empty objects, and unrelated meshes. Check that the required objects have the expected scale, orientation, materials, normals, and texture paths.
6. Export PLY. In MeshLab, use File → Export Mesh As and choose PLY. In Blender, use File → Export → Stanford (.ply), enable Selection Only when appropriate, and choose whether to write vertex normals and vertex colors. Select binary or ASCII output according to the receiving software.
7. Verify the result. Reopen the exported PLY in MeshLab, Blender, or another PLY viewer and check the mesh, scale, orientation, normals, and colors.

For a supported archive, the free converter on 101convert.com can perform the conversion without installing software. Inspect the output afterward because automatic conversion may not preserve textures, object hierarchy, geographic placement, or other KML data.

Quality and compatibility limitations

• Geographic placement can be lost. KML commonly stores latitude, longitude, altitude, orientation, and scale separately from the DAE model. Exporting the DAE alone may produce a model at local coordinates, while applying geographic coordinates directly can place vertices very far from the origin and cause precision problems. Recenter or rescale the mesh in Blender or MeshLab when required.
• Textures are not guaranteed. Keep relative texture paths during extraction and verify them after import. PLY applications vary in their support for texture coordinates and external texture images; vertex colors are generally more portable, but converting an image texture to vertex colors can increase file size and reduce color detail.
• Scene information is discarded. PLY represents mesh data, not KML placemarks, paths, geographic coordinate systems, camera views, animation, or the complete arrangement of multiple scene objects. Keep the original KMZ when those details are needed.
• Geometry may require repair. Check for missing faces, reversed normals, duplicate vertices, non-manifold edges, holes, and excessive polygon counts before 3D printing or further modeling.
• Referenced content may be unavailable. A KMZ can point to files outside the archive or to network resources. Download or package those resources before conversion; otherwise the result may contain only part of the intended model.