How To Create A KMZ File In Google Earth: Step-by-Step GIS Guide

To create a KMZ file in Google Earth, organize your spatial data, placemarks, and paths inside a single parent folder in the Temporary Places panel, right-click the folder, and select the Save Place As option. Choosing the KMZ format from the file type dropdown automatically compresses your KML vector data and associated image assets into a single zip-archived file based on the WGS 84 coordinate system. This ensures that your geospatial files remain lightweight, highly portable, and instantly compatible with modern GIS platforms.

Pre-Authoring Checklist and Spatial Data Setup

Before creating custom geographic files, it is vital to understand the structural difference between KML (Keyhole Markup Language) and KMZ (Keyhole Markup Language Zipped). A standard KML file is a plain-text XML document containing geographic coordinates, styling instructions, and folder structures. While highly readable, standard KML files cannot natively store binary data like custom icons, digital terrain models, ground overlays, or screen images.

A KMZ file resolves this limitation by acting as a compressed zip archive. It packages the primary KML document (internally renamed to doc.kml) alongside a subdirectory of localized assets, such as PNG custom icons, JPEG ground overlays, or 3D Collada models.

To ensure successful map compilation and to prevent broken link indicators, you must prepare your physical system workspace and software configurations prior to generating your spatial boundaries.

Essential Tools and Environment Requirements

• Primary Mapping Software: Google Earth Pro for Desktop (Version 7.3 or later is highly recommended over the web-based version to access advanced layer organization, manual directory configurations, and precise coordinate entry tools).
• Coordinate Reference System Standard: World Geodetic System 1984 (WGS 84), which is the native geographic coordinate system for Google Earth. Ensure your external data inputs are projected in decimal degrees (Latitude/Longitude) before manual entry.
• Asset Workspace Directory: Create a dedicated, localized project folder on your local hard drive (e.g., C:/GIS_Projects/Project_Alpha/). Place all custom map icons, logos, and raster overlay graphics into this single directory before importing them into Google Earth.
• Project Budget & Timeline: Free/Open-Source (utilizing Google Earth Pro's native tools). Creating a single structured KMZ file typically requires 15 to 45 minutes, depending on the volume of vector layers and embedded attributes.

Step-by-Step Geospatial Authoring and KMZ Export

Follow this systematic workflow to construct, style, organize, and compile your spatial data layers into a highly functional, shareable KMZ package.

Step 1: Initialize the Parent Folder Directory

To package multiple placemarks, lines, or boundary areas into a single KMZ file, you must first establish a unified container inside the Google Earth directory tree. Without a parent folder, your export will be restricted to isolated geographic features.

1. Launch Google Earth Pro on your desktop computer.
2. Locate the Places panel on the left-hand sidebar.
3. Right-click on the Temporary Places folder to open the context menu.
4. Hover over the Add menu item and select Folder from the flyout list.
5. In the New Folder configuration dialog box, type a clear, descriptive name for your project (e.g., Regional Asset Inventory).
6. Use the Description text area to write metadata, project boundaries, or author information, then click OK. The new folder will now appear in your Places sidebar.

Step 2: Plot Points, Lines, and Polygons

With your container folder active, you can begin drawing geographic vector data. Google Earth supports three primary vector geometries: Placemarks (points), Paths (lines), and Polygons (areas).

1. Select your newly created parent folder in the Places panel. This ensures that any vector features you draw are automatically nested inside this directory.
2. To add a point of interest, click the yellow Add Placemark pin icon on the top utility toolbar. Drag the blinking yellow crosshairs on the map viewer to your exact coordinate location. In the properties panel, enter your desired title and coordinates.
3. To add a linear feature, such as a pipeline, road, or flight path, click the Add Path icon on the top toolbar. Left-click along the map to drop successive vertices. Hold down the left mouse button to draw continuous freehand lines.
4. To define a boundary or land area, click the Add Polygon icon. Click the map surface to establish corner vertices; the application will automatically fill the space between these points to form a closed shape.

Warning: Always keep the properties dialog window open while placing or editing your vector points. Closing this window locks the geometries. To re-enable editing, you must right-click the feature in the sidebar and choose Properties.

Step 3: Configure Symbology and Apply Custom Styles

Unstyled vector layers default to standard yellow pins or basic white lines, which can obscure critical maps. Customize the styling parameters of your vectors to make your geospatial data clear and legible.

1. Right-click your vector feature in the Places panel and select Properties (on Windows) or Get Info (on macOS).
2. Click the Style, Color tab inside the properties window.
3. For paths and polygon outlines, adjust the Width property to a minimum of 2.0 or 3.0 pixels to ensure visibility against high-contrast satellite backgrounds. Adjust the Color box to apply high-visibility colors like neon green, cyan, or bright orange.
4. For polygons, use the Area dropdown menu to select Outlined (which displays only the boundary line) or Filled + Outlined (which shades the interior). Set the opacity slider to roughly 30% to 50% so users can see the underlying terrain features.
5. To change point icons, click the pushpin icon button in the upper-right corner of the properties window. Choose a preset icon, or click Add Custom Icon to load an image from your local asset directory.

Step 4: Embed Metadata and Relative-Path Media

A strong KMZ file should provide information to users when they click on individual elements. You can add context by embedding rich HTML descriptions, tables, and ground photos inside each feature’s information bubble.

1. Open the Properties dialog for any selected placemark or polygon.
2. In the Description tab, input clear metadata. Google Earth supports basic HTML formatting inside this space, allowing you to write styled paragraphs, bold headers, and bulleted lists.
3. To embed an image, click the Add Web Image or Add Local Image button.
4. When adding local images, use a relative path structure instead of an absolute path pointing to your computer's drive. If your image file is in your project workspace folder alongside your working KML, write only the image filename (e.g., site_photo_01.jpg) rather than referencing your system drive. This relative link ensures the image successfully packages into the final KMZ archive.

Pro-Tip: Wrap your description content in standard HTML table tags to build structured pop-up boxes. This keeps your attribute names and metric values perfectly aligned in columns, making the map much easier to read.

Step 5: Export and Compress the Folder Structure

Once your geographic vectors, custom styling, and relative asset paths are configured, compile your spatial project into the compressed KMZ format.

1. In the Places panel, locate the parent folder you created in Step 1. Confirm that all your individual vector points, paths, and polygons are fully nested inside this folder.
2. Right-click on this parent folder to trigger the context menu.
3. Select Save Place As... from the options list.
4. In the file saving dialog window, navigate to your dedicated local project folder.
5. Click the Save as type dropdown menu and change the selection from KML (.kml) to KMZ (.kmz).
6. Click Save. Google Earth will instantly zip your vector data, custom styles, and local image assets into a single, highly compressed KMZ file.

KML vs. KMZ Technical Specifications and Formatting Metrics

The choice between exporting raw KML data or compiled KMZ structures depends heavily on the complexity of your spatial assets and your target platform's specifications. Use the table below to compare their core properties and formatting metrics.

Troubleshooting KMZ Compilation Errors and Red X Graphics

Even experienced GIS technicians can run into display issues or missing information when exporting spatial packages. Review these real-world failure scenarios and their solutions to fix common KMZ errors.

Failure 1: Custom Icons and Ground Overlays Display as Red "X" Boxes

• Root Cause: This issue occurs because of broken absolute file paths. If your local file references are set to absolute system paths (such as C:\Users\Surveyor\Desktop\Project_Files\icon.png), the KMZ file will look for that exact location. When shared with a user on a different computer, Google Earth cannot find that folder path and displays a Red X icon instead.
• Actionable Fix: Convert all absolute asset paths to relative paths. Place your custom icons or ground overlay images in the same folder as your working KML file before exporting. When assigning the image, refer only to the direct filename (e.g., icon.png or images/icon.png). When you export to a KMZ, Google Earth will correctly bundle these assets into the compressed folder, making them display properly on any computer.

Failure 2: Distorted Polygon Topography and Flat Geometries

• Root Cause: This occurs when the vector feature's altitude property is set to absolute elevation values without considering the surrounding terrain. This can cause polygons and paths to slice through 3D mountains, dip below the Earth's surface, or float high in the air.
• Actionable Fix: Right-click the problematic polygon or path in your Places panel and select Properties. Navigate directly to the Altitude tab. Change the altitude dropdown menu setting from Absolute to Clamped to ground. This forces your vector shapes to conform to the curves and elevation of the 3D terrain.

Failure 3: Extremely Slow Render Times or Google Earth Application Crashes

• Root Cause: Packing uncompressed high-resolution images or vector lines with too many points into a single KMZ can cause performance issues. Google Earth Pro struggles to process files when a KMZ exceeds 50 megabytes or includes complex geometries.
• Actionable Fix: Open your local asset folder and use an image editor to compress all embedded ground photos and custom logos. Downsample your image resolutions to 72 or 150 DPI and save them as compressed JPG or PNG files. If your vector paths contain too many vertices, run them through a simplification tool in an external GIS application before importing them back into Google Earth Pro.

Frequently Asked Questions

What is the difference between a KML and a KMZ file?

A KML file is an uncompressed, plain-text XML file used to store spatial vector points, paths, and polygons. A KMZ file is a zipped archive that contains the primary KML file along with its local assets, such as custom map icons, logos, and ground photos. Use KMZ files when sharing detailed maps that include custom imagery, and KML files when you need to edit coordinate values in a text editor.

Can I open a KMZ file in Google Maps?

Yes, Google Maps supports importing KMZ files through the My Maps feature. To upload one, go to Google My Maps, create a new map, add a new layer, and click the Import button. Select your local KMZ file to import your custom vector shapes, points, and paths onto the standard Google Maps interface.

How do I convert a KMZ file back to a KML file?

Because a KMZ is simply a compressed zip folder, you can extract its contents manually. Change the file extension of your KMZ file from .kmz to .zip (for example, renaming project.kmz to project.zip). Use any archive extraction tool to unzip the folder. Inside, you will find your primary KML document, which is always named doc.kml, along with a folder containing any embedded image assets.

Why are my custom icons missing when I share my KMZ file?

This issue occurs when your custom icons are saved to your local computer but are not packaged inside your KMZ archive. To make sure your custom icons are included, place them in the same directory as your project files before adding them to Google Earth. Then, make sure to export the parent folder containing your layers as a KMZ file, which packages the images, rather than a raw KML file.

Is there a size limit for KMZ files in Google Earth?

Google Earth Pro does not have a strict file size limit for KMZ imports. However, files larger than 50 megabytes can slow down performance or cause the application to crash. For the best performance on both desktop and mobile devices, keep your KMZ files under 10 megabytes by compressing your image overlays and simplifying highly detailed vector lines.

Elevate Your Enterprise Geospatial Workflows

Building accurate, reliable maps is key to successful asset tracking, environmental analysis, and site planning. Reach out to our professional GIS consulting team today to streamline your spatial data workflows, configure your enterprise systems, and upgrade your mapping pipelines.