Home / Map App How-Tos

How to Import a KML File Into Google Maps: My Maps Layers, Placemarks, and the Limits That Shape the Job

Close-up of a hand pinning a small flag into a paper map

Photo: Lara Jameson / Pexels

Someone has sent you a KML file, or you have exported one from Google Earth, and now it sits in your downloads folder doing nothing, because Google Maps has no Open button for it. That gap surprises people, but it has a clean explanation and a clean workaround. KML is the file format Google Earth was built on, a container for named placemarks, drawn lines and polygons, styles, and descriptions. The consumer Google Maps app does not import files at all. Google My Maps, the free map-building tool attached to your Google account, does, and a map built there opens inside Google Maps on your phone as a layer you can navigate with. This guide runs that route carefully, explains what the format carries and what the import keeps, and states the documented limits before they surprise you mid-project.

Interactive tool

Bring Your Pins Home: The KML Import Checklist

Check off each step as you finish it. Your progress stays on this page.

0 of 7 complete

0% done

KML Is Not GPX: Know Which File You Hold

Before importing anything, be sure the file is really yours to import this way. Two formats dominate personal map files, and they come from different worlds. GPX is the GPS exchange format: tracks, routes, and waypoints recorded by watches, handhelds, and cycling computers. If your file came off a device that recorded a journey, it is probably GPX, and our GPX import guide is the right walkthrough, even though the destination, My Maps, is the same. KML is the Google Earth format: authored rather than recorded, built of placemarks someone placed deliberately, often with names, icons, colors, and written descriptions attached. Its compressed sibling wears the KMZ extension and imports the same way. The distinction decides your expectations. A GPX import is about replaying movement. A KML import is about publishing a small, styled atlas someone designed, and the import tools are built to preserve exactly that: the names, the styles, and the words.

The Route In: Google My Maps, Step by Step

Open Google My Maps in a desktop browser and sign in with the Google account you use on your phone. Choose Create a new map. In the layer panel on the left, use the Import link under the layer, then upload your KML or KMZ file, by dragging it in or browsing to it. My Maps reads the file and draws its contents as features on that layer: placemarks become pins with their names, lines and polygons arrive with their styles, and clicking any feature shows the description its author wrote. Give the map a proper title and description of your own at the top of the panel, because that title is how you will find it later on your phone. Then tidy the result: rename the imported layer to say what it holds, hide layers you do not need, and check a handful of features against the source to confirm the import read the file the way its author intended. The whole job takes minutes. What it produces is not a file in Google Maps but a map in your account, which is better: it syncs, it shares by link, and it updates everywhere when you edit it once.

Close-up of a hand pinning a small flag into a paper map
Close-up of a hand pinning a small flag into a paper map

What Survives the Import

The import is faithful to the things KML is for. Placemark names arrive intact, which matters more than it sounds: a well-authored KML is a gazetteer, and the names are the content. Styles largely survive, the icon choices, line colors, and polygon fills that let an author separate trailheads from campsites at a glance. Descriptions survive, including the practical notes authors bury in them, the gate code, the water source, the warning about the last two miles. Folder structure from the source file maps naturally onto My Maps layers if you import folder by folder, which is the working method for big projects: split the KML by theme in Earth or your GIS first, then import each piece as its own layer, so the finished map can show and hide themes the way the author organized them. Our guide to adding multiple pins in Google Maps covers the neighboring territory: when a handful of pins belongs in a list instead, and when a project deserves this full My Maps treatment.

The Documented Limits That Shape the Job

My Maps import has hard edges, and Google's own documentation states them, so plan around the numbers rather than discovering them. An imported file can be up to 5 MB in its uncompressed KML or KMZ form, and a layer can hold up to 2,000 rows of features. Both limits shape real projects. A KML exported from a GIS with every vertex of a detailed boundary can pass 5 MB while describing a single polygon, and a placemark collection built over years can pass 2,000 features in one file. The remedies are craft, not force: simplify geometry before export, since a boundary rarely needs survey-grade vertex density to be useful on a phone map, and split large collections into themed files imported as separate layers, which the layer system is designed to hold. If your data genuinely exceeds what My Maps accepts, that is the signal that the project has outgrown a consumer tool, and the file belongs in Google Earth or a real GIS instead, with My Maps reserved for the field-ready extract.

What Gets Left Behind

Earth authors use parts of KML that My Maps does not carry, and a good import plan names them in advance. Guided tours, the recorded fly-throughs, do not import as experiences; the places they visited survive as features, the journey between them does not. 3D models placed in Earth stay behind, as do some of the more exotic styling and time-based features that Earth renders and My Maps simplifies or drops. Network links, which pull live data from a server into Earth, have no equivalent in a static import. None of this is a defect in the import; it is the difference between a presentation format and a field format. The working habit is to open the imported map beside the source file in Earth and diff them with your eyes, feature by feature for the layers that matter, so the losses are choices you noticed rather than surprises you meet outdoors. If the file's real value is its coordinates rather than its presentation, our guide to getting coordinates from a KML file covers extracting the numbers themselves.

Where KML Files Come From, and Making Your Own

Knowing the sources helps you judge what an import can hold. The classic origin is Google Earth, where a folder of placemarks built over months of research can be saved as KML or KMZ in one right-click, carrying its names, icons, and notes with it. GIS programs are the second source: QGIS and ArcGIS both export layers to KML, which is how survey boundaries, habitat polygons, and site plans end up traveling to phones, though these exports are the ones most likely to hit the size limit and benefit from simplification first. The third source is other people: outfitters, event organizers, researchers, and forum members publish KML files of trail networks, rally routes, and study sites, and importing a stranger's file deserves the same inspection as opening a stranger's document, checking what the features are and where they came from before the layer joins your maps. You can also author in reverse: draw the project in My Maps first, export it as KML from the map menu, and keep that export as your archival copy. That round trip, My Maps out to KML and KML back into My Maps, is the closest thing the consumer tools have to a backup system, and it is worth doing before any big edit to a map you cannot afford to lose.

Using the Imported Map on Your Phone

The payoff for the desktop work is mobile. Open Google Maps on your phone, go to the Saved tab, and find your maps at the bottom of the lists area, under Maps. Open the imported map and it draws as a layer over the live map: your placemarks with their names, your lines, your polygons, all searchable by tapping, all present while you navigate the ordinary map underneath. The layer works as reference rather than as a routing engine: Google Maps will not route along your imported line, but it will show you standing on it, which is what most field use actually needs. Share the map from My Maps by link when collaborators need it, with view or edit permission chosen deliberately, and remember that edits in My Maps flow to every phone that opens the map. Keep the original KML file archived outside Google entirely. The import is a copy with limits and losses, and the authoring file is the one thing the whole chain cannot recreate if it disappears. For the pins and lists that live outside projects like this, our saved places guide keeps the everyday system tidy.

Sharing the Finished Map Without Losing It

A My Maps map is an account object, and sharing it well is a small discipline of its own. From the My Maps editor, the Share button offers the same choice as a Google Doc: specific people, or anyone with the link, as viewers or as editors. Choose deliberately. View access is right for publishing a trail day, an event layout, or a research area to the world. Edit access is a key to the whole map, and a collaborator's tidy-up can delete the layer your trip depends on, so grant it to named people only, and keep that archival KML export from the previous section before any shared editing session. Remember also that the map's visibility and your account's privacy are linked: a publicly shared map shows its title and its owner's name, which is exactly right for a community project and worth a thought for a personal one. When the project ends, you can unshare, export the final KML as the record, and delete the working map, leaving the file as the single source of truth again. Import, build, share, archive: the full circle keeps a format from 2004 feeling surprisingly modern.

Related Guides

Readers working through this topic usually need its closest companions too. These map app guides cover the neighboring ground:

Frequently Asked Questions

Can Google Maps open a KML file directly?

No. The Google Maps app and website do not import files. The route is Google My Maps: create a map, import the KML or KMZ into a layer there, and then open that map inside Google Maps on your phone through the Saved tab.

What are the size and feature limits for importing KML into My Maps?

Google's documentation states an imported file can be up to 5 MB in uncompressed KML or KMZ form, and a layer can hold up to 2,000 rows. Split large collections into themed layers and simplify heavy geometry before export to stay inside both limits.

What is the difference between KML and GPX for Google Maps?

KML is Google Earth's authored format: named placemarks with styles and descriptions. GPX is the GPS exchange format from watches and handhelds: recorded tracks, routes, and waypoints. Both import through My Maps, but they come from different work and carry different content.

What parts of a KML file do not survive the import?

Earth extras such as guided tours and 3D models do not carry into My Maps, and some advanced styling, time features, and network links are simplified or dropped. Placemark names, core styles, and descriptions, the substance of most files, import faithfully.

Can I navigate along a line I imported from KML?

Not as a route. The imported map draws as a reference layer over Google Maps, so you can see your position against your lines and placemarks, but Google Maps will not generate turn-by-turn directions along an imported path.

Photo credits: Lara Jameson (Pexels); Vlada Karpovich (Pexels). Photos are served from this site; follow the credit to the library page for the original.