Skip to content
geodata.plus
Sign in
Documentation

Convert FlatGeobuf to GeoPackage Online — Free GIS Converter

Convert FlatGeobuf (.fgb) files to GeoPackage (.gpkg) in your browser — move from streaming binary to a portable SQLite database compatible with QGIS and ArcGIS Pro.

Updated May 2026

FlatGeobuf is ideal for streaming and cloud queries, but GeoPackage is the better choice when you need a portable, editable, multi-layer database for desktop GIS — convert your .fgb file to .gpkg with geodata.plus.

Why convert FlatGeobuf to GeoPackage?

FlatGeobuf and GeoPackage are both modern, open-standard vector formats, but they serve different purposes. FlatGeobuf is optimized for read-only streaming and HTTP range request access — it is not designed for editing or multi-layer storage. GeoPackage, built on SQLite, supports full read-write editing, multiple feature layers in a single file, attribute-only tables, and raster tile storage, making it the better choice for desktop GIS workflows, field data collection, and offline use on mobile devices.

When you have processed a dataset in a cloud pipeline using FlatGeobuf and need to hand it off to a QGIS user or store it as a long-term working dataset, GeoPackage is the natural landing format.

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 CRS from the FlatGeobuf header and preserves it in the GeoPackage layer definition
  • Optional reprojection — reproject to any target EPSG code before download
  • 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 FlatGeobuf file (.fgb) using the widget above
  2. geodata.plus reads the FlatGeobuf header to confirm the CRS, geometry type, and attribute schema
  3. Select GeoPackage as the output format; optionally choose a target EPSG for reprojection
  4. Download your .gpkg file containing the converted layer in a portable SQLite database

FlatGeobuf format

FlatGeobuf is a binary, row-oriented vector format built on the FlatBuffers serialization library. It includes a Hilbert R-tree spatial index at the start of the file for fast range queries. The CRS is stored in the file header. FlatGeobuf is single-layer per file, optimized for read performance, and is not designed for in-place editing. It is primarily used in cloud-native GIS pipelines and high-throughput spatial APIs.

| Property | Value | |---|---| | Extension | .fgb | | Type | Vector, single file (binary) | | Coordinate system | Any CRS (stored in header) | | Geometry types | Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, GeometryCollection | | Common software | GDAL, QGIS, Mapbox, cloud-native GIS, web APIs |

GeoPackage format

GeoPackage is an OGC open standard built on SQLite. A single .gpkg file can contain multiple feature layers (each with its own geometry type and CRS), raster tile pyramids, and attribute-only tables. It supports full UTF-8 field names with no length limit, read-write editing, and files well beyond the 2 GB Shapefile limit. GeoPackage is the recommended format for offline mobile GIS and is natively supported in QGIS, ArcGIS Pro, and GDAL.

| Property | Value | |---|---| | Extension | .gpkg | | Type | Vector, single file (SQLite database) | | Coordinate system | Any CRS (per layer) | | Geometry types | Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, GeometryCollection | | Common software | QGIS, ArcGIS Pro, GDAL, mobile GIS, offline workflows |

Frequently asked questions

Can I add more layers to the GeoPackage after conversion?

Yes. GeoPackage is a standard SQLite database, and QGIS, ArcGIS Pro, and GDAL can all add, remove, and modify layers in an existing .gpkg file. You can use it as a growing project database, adding additional FlatGeobuf conversions or other vector layers over time.

Is there a performance difference between reading from FlatGeobuf vs. reading from GeoPackage?

FlatGeobuf is generally faster for pure read operations due to its binary columnar layout and embedded spatial index. GeoPackage is slower on initial spatial queries but supports write operations and multi-layer access. For desktop GIS editing, GeoPackage is the better choice; for serving data to a web API, FlatGeobuf has the edge.

Will my attribute data types be preserved in the GeoPackage output?

Yes. FlatGeobuf stores a typed attribute schema in its header (integers, floats, strings, booleans, dates), and geodata.plus maps each type to the equivalent GeoPackage column type. No type information is lost during the conversion.

flatgeobufgpkgconvertgis