Exporting to Google Earth

Export packages your whole project as a KMZ — every asset as true-scale 3D geometry, standing on the terrain at its exact coordinates, facing its set heading. Exporting requires a Pro or Team plan.

Two flavors, two destinations

Google Earth Pro: The main export: a KMZ with full 3D models. Open it in the free Google Earth Pro desktop app (File → Open, or just double-click the file). This is the one to send to stakeholders — smooth to orbit, looks right from every angle.
Google Earth (web): earth.google.com can't render KMZ 3D models, so this variant rebuilds the same geometry as polygons it can draw. The file is named …-earthweb.kmz— use it when the recipient won't install anything.

What's in the file

→Real meter dimensions — a 120 m hub height measures 120 m in Earth's ruler.
→Models sit on the terrain surface and follow it — no floating or buried bases.
→Heading and dish azimuths carry over exactly as set.
→Per-asset color tints are baked into the models.
→Assets are grouped by type in the Places panel, one placemark per asset, named by its label.
→Wind turbines use the high-detail model — shaped blades, nacelle, spinner.

Big sites

Past about 80 assets, the export automatically splits into geographic tiles that Google Earth streams as you fly — a 300-turbine build-out stays smooth instead of choking the viewer. Nothing to configure; it's still one KMZ file.

Export history

Each project keeps a log of exports — when, which variant, how many assets. It's a record, not a file archive: to get a file matching the current state of the project, just export again.

Keep the .kmzas-is — don't unzip it. And every export is cache-proof: if you move a turbine and re-export, Google Earth shows the new position, never a stale cached model.

Sharing without a file

For a quick look that needs no Google Earth at all, a project's share link opens the interactive 3D site view in any browser, read-only. See Getting started.