Free online KML to GDB converter

ArcGIS Pro and other Esri workflows require an Esri file geodatabase for editing, querying, and geoprocessing data received from Google Earth or mapping systems. The .gdb extension is also used by some Garmin software, so the required destination must be identified before conversion.

What KML is

KML (Keyhole Markup Language) is an XML-based geographic format used by Google Earth, Google Earth Pro, web maps, GPS exports, surveying systems, real-estate maps, and shared location data. It can contain points, lines, polygons, names, descriptions, HTML pop-ups, styles, icons, folders, camera views, ground overlays, and some 3D content.

KMZ is the compressed ZIP-based form of KML and may contain images or other referenced resources. KML coordinates normally use geographic WGS 84, EPSG:4326, with longitude, latitude, and optional altitude in that order.

What GDB is

In GIS software, GDB normally means an Esri file geodatabase. It is a directory whose name ends in .gdb, not one standalone file. A file geodatabase can contain feature classes, tables, spatial indexes, domains, subtypes, and coordinate-system information.

Compared with KML, it provides a structured storage model for GIS editing, attribute queries, geoprocessing, larger datasets, and integration with ArcGIS. It is the appropriate target when the receiving application specifically requests an Esri file geodatabase.

Garmin GDB is a different, proprietary database format. Garmin MapSource and related applications may use .gdb for GPS data. An Esri file geodatabase will not open as a Garmin database; use GPSBabel or Garmin-compatible software for that destination.

Convert with ArcGIS Pro

1. Open a project in ArcGIS Pro.
2. Open Analysis → Tools and search for KML To Layer.
3. Set Input KML File to the .kml or .kmz file.
4. Set Output Location to a regular folder, not an existing geodatabase.
5. Enter an output name and run the tool. ArcGIS creates a new folder containing an Esri file geodatabase and imports available point, polyline, and polygon layers.
6. Add the resulting feature classes to the map. To move them into an existing geodatabase, use the layer's Data → Export Features command or the Feature Class To Feature Class geoprocessing tool.

The equivalent ArcPy call is:

arcpy.conversion.KMLToLayer(input_kml, output_folder, output_name)

ArcGIS Pro is the best choice when the output must preserve Esri geodatabase behavior or later participate in domains, subtypes, publishing, or enterprise workflows.

Convert with QGIS

1. Open the KML or KMZ with Layer → Add Layer → Add Vector Layer.
2. Load the point, line, and polygon layers created by the import.
3. For each layer, right-click it and choose Export → Save Features As.
4. Choose OpenFileGDB or ESRI FileGDB, depending on the GDAL drivers installed with QGIS. OpenFileGDB is the usual choice on current installations that support writing.
5. Specify a new or existing folder ending in .gdb, enter the target feature-class name, and select the required coordinate reference system.
6. Repeat the export for every geometry layer, then inspect the database in the QGIS Browser panel or ArcGIS Pro.

QGIS can convert ordinary vector layers effectively, but driver availability and support for Esri-specific capabilities vary by installation. Check the selected driver before relying on domains, subtypes, or other advanced geodatabase properties.

Convert for Garmin software

Do not use ArcGIS or QGIS if the destination is a Garmin .gdb. Install GPSBabel, verify that the installed version supports the required Garmin GDB variant, and run a conversion such as:

gpsbabel -i kml -f input.kml -o gdb -F output.gdb

Open the result in the intended Garmin application and check its supported GDB version. If GPSBabel cannot write the required variant, convert KML to GPX and import the GPX through Garmin software instead; GPX support is generally more interoperable than Garmin's proprietary database format.

Online conversion

A service such as MyGeodata Cloud advertises KML-to-ESRI-geodatabase conversion and can provide a compressed geodatabase for download. Confirm that the service produces an Esri file geodatabase, not a Garmin database or another format, and inspect the downloaded feature classes before use. Do not upload confidential, regulated, very large, or structurally complex data unless the service is approved for it; desktop conversion keeps the source data under local control.

Quality and compatibility limits

• KML styles, icons, folder hierarchy, camera views, pop-up HTML, and 3D display settings may not become geodatabase properties. Recreate symbology and pop-ups in the GIS application.
• Network links may reference live external content instead of containing the features. A converter may preserve the link or omit its current content rather than download it.
• Ground overlays and other imagery do not become ordinary vector feature classes. Export or download required raster data separately.
• Most KML is WGS 84. Reproject only when the destination project requires it, and verify the selected transformation and resulting feature positions.
• Review field names, types, dates, numeric precision, null values, descriptions, and automatically generated fields after import. XML descriptions often arrive as plain text or HTML attributes.
• Preserve the complete .gdb directory, including all internal files. Do not copy a single file from inside it; zip the entire directory when transferring it.
• Changing the extension does not convert the format. The output must be created by software that writes the intended Esri or Garmin database structure.