Convert shapefile to CSV and free the attribute table from its .dbf container for Excel, Python or R. The layer is read wholly inside the browser, useful when the data is confidential as much as when it is big.
Drop a file here, or click to browse
KML, KMZ, SHP (.zip), GeoJSON, GPKG, GML, GPX, DXF, CSV, Excel, and more
No Shapefile file to hand? Download a sample Shapefile file (100 points) and drop it above to see the conversion.
Every format stores different things, so a conversion is never perfectly loss-free. Here is exactly what carries over when you convert Shapefile to CSV, and what to watch for.
| What | Shapefile → CSV | |
|---|---|---|
| Geometry | Changes | Point features become X and Y columns; lines and polygons are written to a WKT geometry column, so no shape is lost in the table. |
| Attributes | Kept | Every column and full field name moves from Shapefile into CSV untouched. |
| Styling & labels | Kept | Neither Shapefile nor CSV stores visual styling, so there is nothing to lose, the geometry and data carry straight over. |
| Coordinate system | Changes | CSV stores raw coordinates without a CRS tag, so note the coordinate system separately for whoever opens the file. |
| Elevation (Z) | Changes | Z values, if present, appear as an extra column rather than 3D geometry. |
| File structure | Kept | A single, self-contained .csv file you can move around on its own. |
People convert Shapefile to CSV when they want to leave desktop GIS and work with the attributes as plain rows. A shapefile keeps geometry in the .shp and attributes in the .dbf, which is awkward to read outside ArcGIS or QGIS. CSV opens instantly in Excel or Google Sheets, so you can edit fields, sort records and clean data. Also, scripts and APIs love CSV. For example, pandas reads it in one line, and point coordinates can feed straight into a mapping or analysis pipeline without touching the original layer set.
Shapefile records its own coordinate system (in a .prj sidecar or embedded metadata), and the converter reads it automatically, so it knows where your data belongs on the globe.
CSV stores raw coordinates without a CRS tag, so make a note of the coordinate system for whoever opens the file next. A quick CRS check before you download saves the classic "my Shapefile data is in the wrong place" surprise; the guide on coordinate systems and EPSG codes goes deeper.
Check that your Shapefile holds point geometry. CSV stores coordinates as columns, so points map cleanly to latitude and longitude. Lines and polygons have no single X/Y, so their geometry may collapse or export as WKT text instead. Also remember shapefile field names are capped at 10 characters, so those truncated headers carry straight into your CSV. Rename columns afterward if you need readable labels.
Shapefile files typically come out of ArcGIS, QGIS, GeoServer, MapInfo. Once you convert to CSV, the file opens in Microsoft Excel, Google Sheets, LibreOffice Calc, and any script or database import. The CSV output follows the standard specification exactly, so those programs read it without any special import settings.
A Shapefile arrives as a bundle of parts, with geometry in the .shp and the attribute table in the .dbf. CSV flattens all of that into one plain-text sheet. In practice, people convert a Shapefile to CSV to open its records in Excel or feed them to a pandas script. Each feature becomes a row. Point geometry lands in latitude and longitude columns, while lines and polygons are written as WKT text. The pairing turns a GIS-only layer into something any spreadsheet reads.
Yes. Every field in the .dbf becomes a column in the CSV, so all attributes travel with their rows. Just note the 10-character field names carry over unchanged.
Yes. The CSV is plain text, so Excel and Google Sheets open it directly, and pandas reads it with read_csv. If it holds coordinate columns, QGIS can also load it back as points.
Point features get their coordinates split into latitude and longitude columns. Lines and polygons cannot fit two tidy columns, so their vertices are written as WKT text in a single geometry column. The attribute fields from the .dbf fill the remaining columns.
Yes. Provide the full set together, ideally zipped, because each part carries something the CSV needs. The .shp holds the shapes, the .dbf holds the attribute values that become your columns, and the .prj records the coordinate system. Without the .dbf, the CSV loses its data fields.
A CSV file opens in Excel, Google Sheets, LibreOffice and any database. Because the output follows the standard specification, any tool that supports CSV will read it without special settings.
No conversion is perfectly loss-free because each format stores different things, but nothing important is lost: point coordinates become X/Y columns and any lines or polygons are saved as WKT text, so the geometry survives in the table.
