GIS file formats
| Format | Best practical use | Watch for |
|---|---|---|
| GeoPackage | local editable vector/raster database | one file can contain many layers; coordinate metadata matters |
| Shapefile | legacy interchange | field-name/type/Unicode limitations; multiple sidecar files |
| GeoJSON | web/API interchange | often large; CRS usually WGS84 in web use |
| KML/KMZ | Google Earth sharing | styling/attributes simplified; not a working cadastral database |
| CSV | simple tables/point exchange | no native geometry/CRS metadata unless conventions are documented |
| GeoTIFF | raster analysis | can be very large |
| COG | cloud/HTTP raster access | needs compatible clients for range-read benefits |
| File Geodatabase | Esri multi-layer data exchange | proprietary ecosystem though widely readable |
| MBTiles | packaged map tiles | tile package, not source feature database |
| LAS/LAZ/COPC | LiDAR point clouds | huge data; classification/CRS must be preserved |
Default choices
For a small QGIS project, GeoPackage is usually stronger than Shapefile. For Google Earth, export a purpose-built KML/KMZ. For analytical imagery/elevation, keep GeoTIFF/COG. For raw LiDAR, use LAZ/COPC when the workflow supports them.
Choose the format for the next use, not because it is the format you first received.
Last reviewed: 26 August 2026