Convert KML to GeoPackage Online — Free GIS Converter

Convert KML files into GeoPackage — the modern OGC-standard format that stores all geometry types in a single SQLite database, making it the ideal upgrade path from KML for desktop and mobile GIS workflows.

Why convert KML to GeoPackage?

KML is excellent for visualization in Google Earth but carries significant limitations when you need to do actual GIS analysis: no support for projected coordinate systems, no multi-layer storage, and no SQL querying. GeoPackage solves all of these. Based on SQLite, a GPKG file can store multiple vector layers with mixed geometry types alongside raster tiles in a single portable file. It is the default export format in QGIS and is natively supported in ArcGIS Pro, making it the modern replacement for both KML and Shapefile in professional workflows.

If you're migrating a KML-based field data collection workflow into QGIS for analysis, or preparing data for an offline mobile GIS app, GeoPackage is the right destination format.

Why use geodata.plus

• Free tier: convert up to 3 files per month at no cost
• Automatic CRS detection; reproject to any EPSG code on the fly
• Mixed KML geometry types preserved in a single GPKG file (no splitting required)
• Browser-based — no GDAL, QGIS, or Python install required
• Encrypted upload (TLS); files stored in Cloudflare R2, automatically deleted after 2 days (free) or 7 days (Pro)
• Output is a single self-contained .gpkg file

How it works

1. Upload your KML file to geodata.plus
2. geodata.plus reads all KML features and detects the WGS 84 coordinate system
3. Select GeoPackage as the output format; optionally choose a target CRS
4. Download your .gpkg file — ready to open in QGIS or ArcGIS Pro

KML format

KML is an XML-based format developed for Google Earth that encodes points, lines, polygons, and rich styling in a single human-readable document. All KML coordinates are in WGS 84. The format does not support projected coordinate systems or multi-layer storage natively.

| Property | Value | |---|---| | Extension | .kml | | Type | Vector, single-file XML | | Coordinate system | WGS 84 (EPSG:4326) only | | Geometry types | Point, LineString, Polygon, MultiGeometry | | Common software | Google Earth, Google Maps, ArcGIS, QGIS |

GeoPackage format

GeoPackage is an OGC open standard built on SQLite. A single .gpkg file can contain multiple vector feature layers and raster tile layers, supports any coordinate reference system, and has no practical file size limit for modern use cases. It replaced Shapefile as the recommended exchange format for most open GIS workflows and is supported natively in QGIS 3.x, ArcGIS Pro 2.x+, GDAL, and most mobile GIS platforms.

| Property | Value | |---|---| | Extension | .gpkg | | Type | Vector (and raster), single-file SQLite | | Coordinate system | Any CRS | | Geometry types | Point, LineString, Polygon, Multi* variants, GeometryCollection | | Common software | QGIS, ArcGIS Pro, GDAL, mobile GIS, offline workflows |

Frequently asked questions

Do KML folders become separate layers in the GeoPackage? By default, geodata.plus merges all KML features into a single layer in the output GPKG. If your KML uses distinct <Folder> elements to separate logical groups of features, those folder names are preserved as an attribute field so you can filter or re-split them in QGIS using the "Split Vector Layer" processing tool.

Can I reproject from WGS 84 to a local projected CRS during conversion? Yes. GeoPackage supports any CRS, so you can select a target EPSG code (such as EPSG:32633 for UTM zone 33N or EPSG:27700 for British National Grid) during the conversion step. geodata.plus reprojects coordinates before writing the output file, so your GPKG will open in the correct projected system without any manual reprojection in QGIS.

Is GeoPackage suitable for offline field use after converting from KML? Absolutely — this is one of GeoPackage's primary design goals. After converting, you can load the .gpkg directly into QField, Mergin Maps, or ArcGIS Field Maps for offline editing. The SQLite foundation means the file works without any network connectivity and can be synced back to the desktop after fieldwork.