Back

Export Google Maps Lists to GeoJSON and KML for Map Content

Content creators spend hours curating place lists in Google Maps. Takeout Tools turns those lists into publishable formats, GeoJSON for custom maps, CSV for editorial, KML for shareable guides.

For content creators and map publishers

The curation problem

Building a great place list takes time. Finding the right restaurants for a neighbourhood guide, vetting hotels for a travel piece, collecting the stops for a walking tour, that research lives in Google Maps because Google Maps is the fastest place to collect and verify location information.

The problem is publishing it. Google Maps doesn't let you export a list as an embeddable map, a downloadable file, or a structured dataset your audience can use. The curation work you did is locked behind a platform you don't control.

What publishing actually needs

Depending on what you're building, location data needs to go to different places:

  • Custom web maps: Mapbox, Leaflet, and Felt all work natively with GeoJSON. If you want an interactive map embedded on your site or newsletter, GeoJSON is the input they expect.
  • Google My Maps: If your audience is comfortable with Google products, KML imports directly into My Maps and renders your places with the labels and colours you set.
  • Editorial and data use: CSV is the right format for content workflows: add columns for description, category, and editorial notes, then feed into Flourish or Datawrapper for visualisation.
  • Downloadable packs: Audience members who want your list on their GPS device need GPX. A downloadable GPX file is a product in itself.

The Takeout Tools workflow

Google Takeout gives you your saved places as a CSV, names and categories only, no coordinates. That's not enough to build a map, embed a layer, or produce a downloadable file.

Takeout Tools geocodes each place in your export, adding the coordinates that make the data usable. From there you choose the format that fits your publishing workflow.

Which format fits which output

GeoJSON

The right format for any web map workflow. Mapbox, Leaflet, Felt, Kepler.gl, and Datawrapper all accept GeoJSON directly. If you're building a custom interactive map, start here. Convert from KML to GeoJSON or GPX to GeoJSON if you're coming from another source.

KML

The right format for Google My Maps and Google Earth. KML preserves your list structure and lets you apply custom icons and labels. Good for creating a shareable, styled guide that non-technical audiences can open and navigate. Convert GeoJSON to KML if you need it for a specific tool.

CSV

The right format for editorial and design workflows. Import into Airtable or Google Sheets, add editorial notes, categories, and editorial status columns, then hand off to a designer or feed into Flourish and Datawrapper for visualisation. CSV is also the most flexible format for republishing location data as a structured dataset alongside a written piece.

GPX

The right format for a downloadable audience product. Package your guide as a GPX file and let your readers load it into OsmAnd, Gaia GPS, or a Garmin device for use in the field. Convert from KML to GPX or GeoJSON to GPX if you already have a file in another format.

Keeping your place list up to date

Published maps go stale. Restaurants close, venues move, prices change. The most sustainable workflow is to treat your Google Maps list as the source of truth and re-export via Takeout Tools whenever you update it. Export to GeoJSON, replace the file your web map reads from, and the published map stays current without rebuilding it from scratch.

Offering a downloadable file as a product

A well-curated GPX or KML file has standalone value for your audience, something they can load into their own navigation app and use in the field. Consider publishing a downloadable file alongside your written guide. A "download the GPX" link gives your audience something tangible and makes your content more useful than a guide that only works inside Google Maps.

Working with multilingual place names

If you curate places across different countries, you may encounter place names in multiple scripts or languages. Takeout Tools normalises CSV headers across 11 languages and handles Unicode place names correctly. The geocoder works from the address data Google has on file, so even places saved with a local-language name will resolve correctly as long as Google Maps has an address associated with them. This matters for travel-focused content creators in particular, a guide to Tokyo or Istanbul needs accurate coordinates regardless of how place names are stored in the export.

Convert between formats

Already have a geo file and need it in a different format? Use the free online converters:

Frequently asked questions

Google Maps Saved Places to GeoJSON and KML for Content Creators and Map Publishers | Takeout Tools