Shapefile and CSV: what actually changes
Shapefile is the Esri classic — actually three or more sidecar files pretending to be one. CSV is comma-separated plain text — one table, no types, readable by everything.
Feature attributes are exported as a flat table and geometry is written as WKT or as coordinate columns, depending on the feature type. The CSV you get back keeps the header row and every value as text, and gives up formulas, formatting, multiple sheets and column types. Reproject first if you need the coordinates in something other than the source CRS.
How it goes3 steps
-
Add your Shapefile files
Drop them onto the box above or click Select File. Add as many .shp files as you like — the whole batch converts in one go, and duplicates are ignored.
-
Confirm CSV as the output
CSV is already selected as the target format on this page. Tweak the options if you need something other than a straight CSV file.
-
Download your CSV
Hit Convert and grab the finished CSV files individually or as a single ZIP. Everything is deleted from the server once you have them.
Format facts
What each side of this conversion is good at, so you know what you are trading away.
Source
.shp
Shapefile
The Esri classic — actually three or more sidecar files pretending to be one.
- Compression
- Lossy
- Transparency
- Not supported
- Keeps
- Geometry, attributes and a projection definition
- Gives up
- Field names past 10 characters, and anything over 2 GB
Result
.csv
CSV
Comma-separated plain text — one table, no types, readable by everything.
- Compression
- Lossy
- Transparency
- Not supported
- Keeps
- The header row and every value as text
- Gives up
- Formulas, formatting, multiple sheets and column types
Send Shapefile somewhere else
Every other format a SHP file can leave as.
From .shp
5 targets