Format comparison
Shapefile vs FlatGeobuf: Legacy vs Modern Binary
Shapefile has been the GIS standard for decades but shows its age: multi-file format, 10-character field name limit, no null geometry support. FlatGeobuf is a modern binary format designed for fast streaming and HTTP range requests.
Advertisement (728×90)
Bottom line
Use FlatGeobuf for high-performance web delivery and large dataset streaming. Use Shapefile when legacy tool compatibility is required.
Shapefile vs FlatGeobuf: feature comparison
| Feature | Shapefile | FlatGeobuf |
|---|---|---|
| Age | 1990s (Esri) | 2020 (modern) |
| File count | Multiple (.shp, .dbf, .shx, .prj) | Single .fgb file |
| Field name limit | 10 characters | Unlimited |
| Streaming support | No | Yes (HTTP range requests) |
| Spatial index | None built-in | Yes (Hilbert R-tree) |
| Null geometry | Not supported | Supported |
| Tool support | Universal | GDAL, Tippecanoe, modern tools |
ShapefileWhen to use Shapefile
- Any workflow requiring legacy GIS tool compatibility
- Sharing data with ArcGIS, QGIS, or MapInfo users
- Government data exchange where SHP is mandated
FlatGeobufWhen to use FlatGeobuf
- High-performance web map delivery via CDN
- Large datasets requiring spatial indexing
- Modern pipelines using GDAL or cloud-native tools
Convert between Shapefile and FlatGeobuf
Frequently asked questions
Q.Is FlatGeobuf faster than Shapefile?
Yes — FlatGeobuf includes a built-in Hilbert R-tree spatial index enabling fast bounding-box queries. It also supports HTTP range requests for streaming partial data without downloading the full file.
Q.Can I open FlatGeobuf in QGIS?
Yes, QGIS natively supports FlatGeobuf via GDAL. Simply drag the .fgb file into QGIS.