Skip to content
geodata.plus
Sign in
Documentation

Convert GeoJSON to GeoPackage Online — Free GIS Converter

Convert GeoJSON to GeoPackage (.gpkg) instantly in your browser — the modern, single-file replacement for Shapefile, with full CRS and multi-layer support.

Updated May 2026

GeoJSON is the go-to format for sharing vector data on the web, but when you need a compact, standards-based file for offline GIS work, desktop analysis, or mobile data collection, GeoPackage is the modern choice — convert your .geojson file to .gpkg in seconds with geodata.plus.

Why convert GeoJSON to GeoPackage?

GeoPackage is the OGC-standardized, SQLite-based replacement for Shapefile, and it solves nearly every limitation of the older format. If you are moving data from a web API into a desktop GIS workflow — especially QGIS or ArcGIS Pro — GeoPackage gives you a single portable file with no field-name truncation, support for full datetime columns, and the ability to store multiple layers together. It is also the preferred format for offline mobile GIS applications that need to carry reference data into the field without a network connection.

Unlike GeoJSON, which must be fully parsed into memory before use, a GeoPackage's SQLite foundation allows spatial indexing and selective queries, making it dramatically faster for large datasets. Converting from GeoJSON to GeoPackage is a common step when a dataset that started life as a web API response needs to graduate into a serious analysis workflow.

Why use geodata.plus

  • Free tier — convert up to 3 files per month at no cost, no credit card required
  • Automatic CRS detection — reads the WGS 84 CRS from your GeoJSON and stores the correct EPSG definition in the GeoPackage metadata tables
  • Optional reprojection — reproject to any EPSG code before download, so your GeoPackage arrives in the local CRS your project requires
  • Browser-based — no QGIS, GDAL, or SQLite tools needed; works on any modern browser
  • Encrypted transfer — all uploads use TLS; files are stored temporarily in Cloudflare R2 and automatically deleted on schedule
  • Auto-deleted output — output files are automatically deleted after 2 days (free tier) and 7 days (Pro); no manual cleanup needed

How it works

  1. Upload your GeoJSON file (.geojson or .json) using the widget above
  2. geodata.plus detects the format and confirms the coordinate reference system (WGS 84 / EPSG:4326)
  3. Select GeoPackage as the output format; optionally enter a target EPSG code for reprojection
  4. Download your .gpkg file, ready to open in QGIS, ArcGIS Pro, or any GDAL-based tool

GeoJSON format

GeoJSON is an RFC 7946 standard for encoding vector geometries and their properties as JSON. Every valid GeoJSON file uses WGS 84 coordinates — the spec explicitly prohibits other CRS declarations. It is a single text file with no spatial index, which means reading large files requires parsing the entire document. Its strength is human-readability and universal web support.

| Property | Value | |---|---| | Extension | .geojson, .json | | Type | Vector, single file | | Coordinate system | Always WGS 84 (EPSG:4326) | | Geometry types | Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon | | Common software | Leaflet, Mapbox, OpenLayers, QGIS, ArcGIS, GitHub |

GeoPackage format

GeoPackage is an OGC open standard (OGC 12-128r18) built on SQLite 3. It stores vector features, raster tiles, spatial metadata, and extensions all in a single .gpkg file. The SQLite foundation means it supports proper SQL queries, spatial indexes (via RTree), and ACID transactions. Field names are not truncated, datetime columns are natively supported, and the format can hold multiple named layers in a single file.

| Property | Value | |---|---| | Extension | .gpkg | | Type | Vector (and raster), single file (SQLite) | | Coordinate system | Any CRS (stored in gpkg_spatial_ref_sys table) | | Geometry types | Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, GeometryCollection | | Common software | QGIS, ArcGIS Pro, GDAL/OGR, mobile GIS apps, offline workflows |

Frequently asked questions

Will converting GeoJSON to GeoPackage preserve all my property field types?

Yes. Unlike the DBF format used by Shapefiles, GeoPackage stores attributes in SQLite columns that support TEXT, INTEGER, REAL, BLOB, and DATETIME types without truncation or name-length restrictions. GeoJSON string properties become TEXT columns, numbers become INTEGER or REAL, and boolean values are stored as INTEGER (0/1).

Can I store multiple GeoJSON files in a single GeoPackage?

Each conversion on geodata.plus produces a single GeoPackage layer from one GeoJSON input. However, GeoPackage natively supports multiple layers in one file. If you need to combine several GeoJSON datasets into a single .gpkg, you can do so in QGIS after downloading your converted file by dragging additional layers into the same GeoPackage using the Database Manager or drag-and-drop.

Does the GeoPackage output include a spatial index?

Yes. geodata.plus automatically builds an RTree spatial index on the geometry column during conversion. This is the same index that QGIS and ArcGIS Pro use internally and means your GeoPackage will load and query significantly faster than the equivalent GeoJSON, especially for large feature counts.

geojsongeopackageconvertgis