GeoDataViewer
Menu
Launch Studio
Theme
.shp

ESRI Shapefile Viewer

Understand what ESRI Shapefile is used for, why it is still common, and where its limits show up in modern GIS workflows.

Drag and drop your .shp, .shx, .dbf files or a .zip archive containing them.
All processing runs locally in your browser.

ESRI Shapefile

Drag and drop your .shp, .shx, .dbf files or a .zip archive containing them.

How to open ESRI Shapefile online

View Shapefile (.shp, .dbf, .shx) online. No installation required. Supports zipped shapefiles. Drag and drop your .shp, .shx, .dbf files or a .zip archive containing them.

Privacy

Files are processed on your device in the browser. GeoDataViewer does not upload your datasets to a server for viewing.

Common issues

If a dataset uses multiple required sidecar files, make sure you provide the complete set together. For best results, keep all sidecars in one zip archive when applicable.

Related tools

Measure distances, areas, elevation, and radius circles using the tools menu, then come back to inspect your ESRI Shapefile layer on the map.

What is ESRI Shapefile?

ESRI Shapefile is a long-standing vector exchange format that remains common because many desktop GIS tools, data portals, and procurement workflows still expect it.

A shapefile dataset is not one file. It is a set of sidecar files that together hold geometry, spatial indexing, attributes, projection metadata, and optional encoding hints.
Even though newer formats are more capable, shapefile persists as a lowest-common-denominator handoff format across government, utilities, consulting, and vendor ecosystems.

What is ESRI Shapefile used for?

  • Sharing vector layers with legacy desktop GIS software that still expects shapefile delivery.
  • Meeting procurement, regulatory, or portal requirements that explicitly ask for shapefile exports.
  • Handing off simple point, line, or polygon layers where maximum interoperability matters more than advanced schema support.

Common use cases

  • Final delivery packages for public-sector datasets and consultant submissions.
  • Quick exchange with partners who use older ArcGIS, QGIS, or CAD-adjacent GIS workflows.
  • Download bundles for simple reference layers such as parcels, roads, service zones, or boundaries.

Strengths

  • Extremely broad software support across desktop GIS and many ETL tools.
  • Familiar workflow for users who have depended on shapefile for years.
  • Simple one-layer exchange model works for straightforward feature delivery.

Limitations

  • Shapefile is a multi-file format, so sidecars are easy to lose during email or manual copying.
  • Attribute names and schema behavior are constrained compared with modern database-backed formats.
  • A shapefile layer must fit one geometry family, which makes mixed-geometry exports awkward.

File extensions and sidecar files

.shp
Main geometry file that stores the feature shapes.
.shx
Index file that lets readers locate shapes efficiently.
.dbf
Attribute table stored in dBASE format.
.prj
Optional projection definition used to describe coordinate reference metadata.
.cpg
Optional encoding hint that tells readers which character set to use for the DBF table.

Convert ESRI Shapefile online

ESRI Shapefile Viewer FAQ

Why is shapefile still so common?

It survives because so many desktop GIS tools, portals, and contractual workflows still accept shapefile as a safe common denominator.

Why do zipped shapefiles sometimes fail to open?

They usually fail because one or more required sidecar files are missing, mismatched, or named differently from the main layer.

What are the biggest shapefile limitations?

Multi-file packaging, older attribute constraints, and one-geometry-family-per-layer rules are the most common reasons teams move to newer formats.