feature layers found ·
Shapefile export warnings
of layers selected
Building Shapefile ZIP
/ features processed
Shapefile ZIP ready
features exported across layers
Layers
Features
Skipped
ZIP Size
Review these Shapefile compatibility notes
Files in the ZIP
Each exported layer includes geometry, index, attributes, CRS metadata when available, and UTF-8 encoding metadata.
· features
Conversion failed
How the GPKG to Shapefile Converter Works
Browser-Side Conversion Pipeline
The GeoPackage is opened locally with SQLite WebAssembly. Feature rows are read from the selected layers, geometry BLOBs are parsed as WKB, and the output files are zipped without sending your data to a server.
What the ZIP Contains
Shapefile is not a single file. GIS software expects a matching set of geometry, index, attribute, projection, and encoding files with the same base name.
GPKG to Shapefile Converter Guide
This GPKG to Shapefile Converter turns GeoPackage vector layers into a Shapefile ZIP directly in your browser. It is built for GIS users who need to hand off data to older software, upload shapefiles to web portals, or create a compatible export without installing QGIS or GDAL.
A GeoPackage can hold many feature layers, long field names, modern CRS metadata, and mixed content in one SQLite file. A Shapefile is more limited, but it is still widely required by government portals, environmental submissions, CAD/GIS workflows, and legacy desktop mapping systems. This converter bridges those formats while showing the compatibility warnings that matter.
The conversion happens locally. The page loads a browser SQLite engine, scans the GeoPackage metadata tables, lets you choose layers, parses WKB geometry, writes `.shp`, `.shx`, `.dbf`, `.prj`, and `.cpg` files, then packages them into one ZIP download.
GeoPackage vs Shapefile
GeoPackage is a modern OGC standard based on SQLite. Shapefile is older, but still common because it is supported by almost every GIS application. The table below explains why conversion is useful and where Shapefile limits can affect your output.
| Feature | GeoPackage | Shapefile |
|---|---|---|
| Container | Single `.gpkg` SQLite database | Multiple companion files, usually zipped |
| Layers | Multiple feature layers in one file | One geometry layer per Shapefile set |
| Field names | Long names supported | DBF field names are limited to 10 characters |
| Geometry | Modern WKB geometry, often with Z/M values | Separate point, polyline, polygon, or multipoint files |
| CRS | Stored in GeoPackage metadata tables | Stored separately in a `.prj` file |
Shapefile Export Limits to Know
Good GPKG to SHP conversion is not only about changing file extensions. Shapefile has old DBF and geometry rules, so the converter applies practical safeguards and reports every important change.
| Warning | What it means |
|---|---|
| Field names shortened | DBF names are capped at 10 characters, so long GeoPackage column names are truncated and deduplicated. |
| Z/M stripped | The browser writer exports common 2D Shapefiles, so elevation and measure coordinates are omitted. |
| CRS missing | A `.prj` file is written only when usable WKT is found in the GeoPackage CRS table. |
| Geometry skipped | Null geometries, unsupported GeometryCollections, and mixed incompatible geometry records are reported instead of silently failing. |
GPKG to SHP Conversion in QGIS and GDAL
For automated jobs, very large files, reprojection, or strict production QA, GDAL remains the professional command-line option. This browser tool is best for quick private exports, small to medium files, and one-off compatibility downloads.
| Task | Command |
|---|---|
| One layer | ogr2ogr -f "ESRI Shapefile" output_folder input.gpkg layer_name |
| Reproject | ogr2ogr -f "ESRI Shapefile" -t_srs EPSG:4326 output_folder input.gpkg |
| QGIS | Right-click the layer, choose Export, then Save Features As, and select ESRI Shapefile as the format. |
GPKG to Shapefile FAQ
Can I convert GPKG to Shapefile without uploading my file?
Yes. This converter reads the GeoPackage with the browser FileReader API and processes it locally with SQLite WebAssembly. Your file is not sent to CalculatorsUniverse or any third-party conversion server.
Does a Shapefile need to be downloaded as a ZIP?
Usually yes. A working Shapefile needs several files with the same base name, including `.shp`, `.shx`, and `.dbf`, plus optional `.prj` and `.cpg` files. ZIP packaging keeps those components together and is the format most upload portals expect.
Will this converter reproject my GeoPackage layer?
No. Coordinates are exported as stored in the GeoPackage. If you need a different CRS, reproject in QGIS or use GDAL with `-t_srs` before submitting the Shapefile to another system.
Why are Shapefile field names shortened?
Shapefile attribute data uses a DBF table, and classic DBF field names are limited to 10 characters. The converter truncates and deduplicates field names, then includes a field mapping text file when names had to change.
Can one GeoPackage contain multiple Shapefiles?
A GeoPackage can contain many feature layers, but each Shapefile stores one geometry layer. When you export multiple layers, the ZIP contains one folder per layer with its own `.shp`, `.shx`, `.dbf`, `.prj`, and `.cpg` files.
What should I do if the Shapefile does not open correctly?
First check the warnings shown after conversion, especially skipped geometries and missing CRS metadata. If the layer contains complex mixed geometry or requires reprojection, use QGIS or GDAL because those tools include mature geometry repair and reprojection engines.
Related GIS Calculators
GPKG to GeoJSON Converter
Convert GeoPackage layers to web mapping GeoJSON.
Shapefile to GeoJSON Converter
Convert SHP, DBF, and PRJ files to GeoJSON.
KML to GeoJSON Converter
Convert KML and KMZ files to clean GeoJSON.
GeoTIFF Metadata Reader
Inspect CRS, extent, pixel size, and raster tags locally.
EPSG Code Lookup
Find CRS definitions, WKT, and PROJ strings.
Coordinate Converter
Convert between DD, DMS, UTM, and MGRS coordinates.