The shapefile has been declared dead more times than any format in GIS, and yet it remains the default way spatial data gets handed around. Sooner or later someone emails you a ZIP full of .shp, .dbf and .prj files and just wants to know: what is in this thing?

Installing QGIS or requesting an ArcGIS license is overkill for that question. Browser-based viewers can now parse a shapefile locally — the file never leaves your machine — and render it on an interactive map in seconds.

The quickest option: a browser-based shapefile viewer

Upload your zipped shapefile to this free online shapefile viewer and it renders the geometry on a map with a full attribute table. It runs entirely client-side (the processing happens in your browser via WebAssembly), so it works with sensitive data too — nothing is uploaded to a server.

A few things to check before you upload:

• Zip the whole set. A shapefile is not one file — at minimum the viewer needs the .shp (geometry), .dbf (attributes) and .shx (index) together in one ZIP. Include the .prj too, or the viewer has to guess the coordinate system.
• One layer per shapefile. If your ZIP contains several shapefiles, most viewers load the first or ask you to pick.
• Attribute encoding. Older shapefiles with non-ASCII text may need the .cpg file included to display labels correctly.

Common “it won’t open” causes

When a shapefile refuses to load in any tool, it is almost always one of these:

• The ZIP contains a folder inside a folder, and the .shp is nested where the parser doesn’t look.
• The .shx index is missing (some transfer tools strip it). Desktop GIS can rebuild it; browser viewers usually cannot.
• The .prj is missing and the data is in a projected CRS — the geometry loads but lands in the wrong place on the map. If your data draws off the coast of West Africa (latitude 0, longitude 0), this is your problem.

Beyond viewing: measuring and converting

Once the file is open, the same family of tools covers the usual next steps without ever leaving the browser: measure feature areas and lengths, or convert the shapefile to GeoJSON for use in web maps and JavaScript libraries. If you are heading the other direction — from web formats back to desktop GIS — we have a separate guide to viewing GeoJSON files online.

When you should still reach for desktop GIS

Browser viewers are for inspection, not analysis. Reach for QGIS when you need to edit geometry, join tables, run geoprocessing, or work with files in the hundreds of megabytes. For a five-second sanity check of a boundary file someone sent you — for example the kind of administrative boundaries covered in our free boundary data guide — the browser is now genuinely the fastest path.