A Shapefile is a widely supported GIS vector format originally developed by ESRI in the 1990s. Despite the name, a “Shapefile” is usually not a single file. It is a small set of files that belong together, typically including geometry, attributes, and a spatial index. This multi-file design is the source of both the format’s longevity and its biggest practical headaches.
To open one in your browser, use the free online Shapefile viewer.
Why Shapefile has multiple files
A complete Shapefile dataset consists of at least three files, and often more:
| File | Role | Required? |
|---|---|---|
.shp | Main geometry file — stores the feature shapes (points, lines, polygons) in binary format | Required |
.dbf | Attribute table — stores feature properties in dBASE format | Required |
.shx | Shape index — lets readers locate individual shapes quickly without scanning the entire .shp file | Required |
.prj | Projection definition — stores the coordinate reference system in WKT format | Recommended (data may appear in the wrong location without it) |
.cpg | Code page — tells readers which character encoding to use for the .dbf text fields | Optional (important for non-ASCII text) |
.sbn / .sbx | Spatial index — optional optimization files for faster spatial queries | Optional |
If you upload only .shp, many viewers cannot load the layer correctly because attributes or the spatial index may be missing. This is the single most common cause of “my Shapefile won’t open” errors.
For a detailed troubleshooting guide: How to Open a Shapefile Online
When Shapefile is a good choice
Use Shapefile when you need:
- Maximum compatibility with existing desktop GIS tools — Shapefile is supported by virtually every GIS application ever made, including ArcGIS, QGIS, MapInfo, and countless ETL tools
- A simple “one layer” dataset you can package as a single zip archive for email or download
- Interoperability with workflows that still expect
.shp— many government agencies, consulting firms, and data portals still require Shapefile delivery - CRS flexibility — unlike GeoJSON (which is effectively restricted to WGS 84), Shapefile can store data in any coordinate reference system via the
.prjfile
Shapefile limitations and common problems
Multi-file fragility
The biggest practical headache: if you email or copy a shapefile and forget any of the required files, the dataset is unreadable. This is why zipping Shapefiles before sharing is standard practice.
Attribute constraints
- Field names are limited to 10 characters in the
.dbftable (longer names get truncated) - No native support for dates, nulls, or complex data types — everything is stored as flat dBASE columns
- Maximum
.dbffile size of 2GB limits the number of features or attribute complexity
Single geometry type per file
A Shapefile can only contain one geometry type — all features must be points, or all must be lines, or all must be polygons. Mixed-geometry datasets (e.g., both points and polygons in the same logical layer) are not supported.
No built-in topology or relationships
Shapefile stores flat features — there are no relationships, domains, subtypes, or topology rules. For richer data models, modern formats like GeoPackage or File Geodatabase are better choices.
How to open a Shapefile online
- Go to the Shapefile viewer.
- Upload the full set of files (
.shp,.dbf,.shx, and ideally.prj). - If the dataset is multi-file, upload a single
.zipcontaining all sidecars together. - Inspect the map and attribute table to confirm features look correct.
All processing happens locally in your browser — no server uploads.
Convert Shapefile to modern formats
Modernizing your Shapefile data often starts with conversion:
- Shapefile to GeoJSON — the most common modernization path for web maps and APIs
- Shapefile to GeoPackage — a modern SQLite-based container with no sidecar headaches
- Shapefile to KML — for Google Earth and visualization workflows
- Shapefile to FlatGeobuf — a high-performance binary format for streaming and distribution
Shapefile vs modern alternatives
- Shapefile vs GeoPackage — the legacy standard vs its modern replacement
- GeoJSON vs Shapefile — web-native JSON vs legacy multi-file binary
- MapInfo vs Shapefile — comparing two legacy vector formats
Related reading
- How to Open a Shapefile Online — step-by-step tutorial
- Sidecar Files for Shapefile — detailed documentation
- Free Online Shapefile Viewer