Convert GeoPackage to GeoJSON Online — Free GIS Converter

Convert GeoPackage files into GeoJSON — the open standard for web mapping — so your data works immediately with Leaflet, Mapbox GL JS, OpenLayers, and any REST API that accepts geographic data.

Why convert GeoPackage to GeoJSON?

GeoPackage is an excellent format for desktop GIS work and offline storage, but most web mapping libraries and cloud APIs don't read GPKG files natively — they expect GeoJSON. If you've done analysis in QGIS, collected field data in QField, or received a GPKG dataset from a government agency, converting to GeoJSON is the standard first step for web publication. The output slots directly into Mapbox styles, Leaflet L.geoJSON() calls, GitHub map previews, and geospatial REST endpoints without any additional parsing libraries.

There is one important conversion consideration: GeoJSON mandates WGS 84 (EPSG:4326) coordinates per RFC 7946, so if your GeoPackage is stored in a national projected CRS (e.g., EPSG:27700 for British National Grid or EPSG:3857 for Web Mercator), geodata.plus will reproject automatically.

Why use geodata.plus

• Free tier: convert up to 3 files per month at no cost
• Automatic CRS detection and reprojection to WGS 84 (required by GeoJSON spec)
• Handles multi-layer GPKG files — select which layer to export
• Browser-based — no QGIS, GDAL, 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 human-readable .geojson file

How it works

1. Upload your GeoPackage file to geodata.plus
2. geodata.plus opens the SQLite database and lists available vector layers
3. Select the layer to convert and choose GeoJSON as the output format
4. Download your .geojson file — ready for any web mapping stack

GeoPackage format

GeoPackage is an OGC open standard based on SQLite. A single .gpkg file stores multiple vector and raster layers, supports any CRS, and enables direct SQL queries. It is the default export format in QGIS and is natively supported in ArcGIS Pro, making it a common container for authoritative spatial datasets.

| 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 |

GeoJSON format

GeoJSON is a JSON-based open standard defined by RFC 7946. It mandates WGS 84 coordinates and encodes all standard geometry types in a plain-text structure readable by any JSON parser. Its simplicity makes it the default format for web mapping APIs, GitHub spatial data, and interoperability between geospatial services.

| Property | Value | |---|---| | Extension | .geojson or .json | | Type | Vector, single-file JSON | | Coordinate system | WGS 84 (EPSG:4326) only | | Geometry types | Point, LineString, Polygon, Multi* variants, GeometryCollection | | Common software | Leaflet, Mapbox, OpenLayers, ArcGIS, QGIS, GitHub |

Frequently asked questions

My GeoPackage has multiple layers — which one gets converted? geodata.plus detects all vector layers in the GPKG file and prompts you to select the layer you want to export as GeoJSON. If you need all layers exported, convert each one separately. There is no batch layer export in a single GeoJSON file because GeoJSON represents one feature collection — it has no concept of named sub-layers.

Will my projected CRS (e.g., EPSG:28992) be reprojected to WGS 84 automatically? Yes. GeoJSON requires WGS 84 per RFC 7946, so geodata.plus automatically reprojects coordinates from whatever CRS your GeoPackage uses. You do not need to pre-reproject in QGIS — the output GeoJSON will be in valid WGS 84 geographic coordinates.

My GeoPackage has 500,000 features — will GeoJSON be practical? GeoJSON is not well-suited to very large datasets because the format is unindexed plain text — a client must parse the entire file to query it. For datasets with hundreds of thousands of features that will be served over the web, consider converting to FlatGeobuf instead, which supports HTTP range requests and baked-in spatial indexing. GeoJSON is most practical for datasets up to roughly 10,000–50,000 features depending on geometry complexity.