Free online KMZ to GLB converter

Many web viewers, game engines, and AR tools accept GLB but do not open Google Earth's KMZ packages. Conversion is useful when you need to edit the embedded model in Blender or share one self-contained file containing the geometry and textures.

What the KMZ format is

KMZ is a ZIP-compressed container for a KML geographic document and its referenced resources. Google Earth Pro, mapping and GIS applications, surveying software, and some 3D applications create KMZ files.

A KMZ used for 3D modeling commonly contains doc.kml, one or more COLLADA .dae models, and image textures. KML records the model's geographic placement, orientation, scale, name, visibility, and links to those resources. A KMZ can instead contain only placemarks, lines, polygons, overlays, descriptions, or network links; those contents do not automatically form a 3D mesh.

What the GLB format is

GLB is the binary container form of glTF 2.0. It can store meshes, materials, textures, node hierarchies, cameras, and animations in one file for WebGL viewers, game engines, AR applications, digital-twin systems, and 3D asset libraries.

Unlike a separate .gltf file with external buffers and images, GLB normally embeds its buffer data and textures, making the asset easier to copy and publish. GLB does not inherently preserve KML placemarks, Earth coordinates, terrain behavior, tours, layer controls, or other Google Earth document features.

How to convert KMZ to GLB

Using Blender

1. Back up the original KMZ. Extract it as a ZIP archive: on macOS or Linux, run unzip model.kmz -d model_kmz; on Windows, open the file with File Explorer or an archive utility and extract its contents.
2. Inspect doc.kml in a text editor. Find the <Model> element and its <Link> or <href> value, then locate the referenced .dae file and texture files. If the archive contains no COLLADA model, Blender cannot reconstruct the original 3D object from placemarks or KML geographic shapes alone.
3. Keep the extracted directory structure unchanged. Relative paths in the DAE and KML files may depend on the original locations of the model and images.
4. Open Blender and choose File → Import → COLLADA (.dae). Select the extracted .dae file rather than the KMZ. Check the viewport for missing textures, incorrect orientation, and unexpected scale.
5. Move the model near Blender's world origin if it was imported at very large geographic coordinates. Remove unwanted cameras or helper objects, correct materials, and apply any required rotation or scale.
6. Choose File → Export → glTF 2.0, set the output format to GLB, and export the required objects or the complete scene. With GLB selected, the glTF exporter packages the buffer data and available image textures into the binary file.
7. Reopen model.glb in Blender or the target GLB viewer. Check the mesh, normals, scale, transparency, texture appearance, and animation before sharing the file.

Using the built-in converter

You can convert the file on 101convert.com for free without installing software: select the KMZ input, choose GLB as the output, submit the file, and download the generated binary. This is suitable for standard KMZ packages containing an embedded COLLADA model, but it provides less control than Blender over coordinate cleanup, material correction, object selection, and optimization.

Quality and compatibility limits

• Geographic placement may be lost: KML stores longitude, latitude, altitude mode, heading, tilt, and roll at the document or model-placement level. A GLB export generally preserves local object transforms, not the full Earth-coordinate meaning. Record the original KML placement separately or use a geospatial system with an explicit GLB placement convention.
• Large coordinates can reduce precision: Models positioned at real-world coordinates may jitter, become difficult to edit, or disappear because of floating-point limits. Recenter the mesh near the origin and retain its original geographic position as metadata.
• Materials may change: COLLADA effects, texture transforms, transparency, specular settings, and double-sided behavior do not map perfectly to glTF's physically based material system. Repair materials in Blender when the converted result looks different.
• Textures require valid references: Missing images usually result from broken relative paths, unsupported image formats, or files omitted from the archive. Keep the texture files beside the DAE during import and verify that they are embedded in the exported GLB.
• KML features may be omitted: Network links, terrain references, screen overlays, placemark icons, KML lines, Google Earth tours, and vendor-specific extensions are not ordinary mesh data and may not appear in GLB.
• Optimize for the target viewer: Remove unnecessary objects, reduce excessive polygon counts, resize oversized textures, and apply transforms when the destination has memory, draw-call, or file-size limits.