Add your CSV
Drop a CSV file anywhere on this page
.csv · .tsv · it never leaves the browser
Options
Your WKT
Add a CSV file and the WKT appears here, with its feature counts and anything this pair cannot carry.
What comes across, and what cannot
Preserved
- Geometry — points come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude.
Dropped
- Attributes. WKT is a geometry notation — there is no place in it for a name, an id or any other column. Convert to GeoJSON or CSV when you need to keep the table.
CSV (comma-separated values)
A spreadsheet, not a spatial format. It becomes spatial when two columns hold longitude and latitude, or when one column holds a WKT geometry — which is how anything other than a point survives the round trip.
.csv · .tsv · text/csv
Well-Known Text (WKT)
The OGC's text notation for a single geometry — POINT (30 10), POLYGON ((…)) — and the form PostGIS, Snowflake and BigQuery accept in a SQL statement. It describes shape and nothing else: no attributes, no styling.
.wkt · .txt · text/plain
Convert CSV to WKT, step by step
- Step 1
Add your CSV
Drop a CSV file anywhere on the page, paste it, point at a URL, or press Sample to start from real data. Several files at once are fine.
- Step 2
Set what matters
Coordinate precision and simplification on every pair, plus the handful of settings this one needs — the delimiter and which columns hold the coordinates.
- Step 3
Take the WKT
Read the feature counts and the warning list, then download, copy, or open the result in the Spatly studio to style and publish it.
Your data never leaves the page
Every conversion, measurement and export happens client-side. Nothing is uploaded, logged or stored — you can even use this offline once the page has loaded. Only “Open in Studio” sends data, and only after you sign in.
Good to know
- What is preserved when converting CSV to WKT?
- Geometry — points come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude.
- What is lost converting CSV to WKT?
- Attributes. WKT is a geometry notation — there is no place in it for a name, an id or any other column. Convert to GeoJSON or CSV when you need to keep the table.
- Which columns become the coordinates?
- The tool reads the header and picks the longitude and latitude columns automatically — lon/lng/long/longitude/x and lat/latitude/y are all recognised, including the Turkish boylam/enlem. If it guesses wrong, or your file has a single WKT geometry column, change the mapping in step 2 and the preview updates immediately.
- My CSV has polygons in one column. Does that work?
- Yes. Point the WKT column at it and every geometry type comes through — POINT, LINESTRING, POLYGON, MULTIPOLYGON — instead of only the point you would get from a longitude/latitude pair.
- What about semicolons or tabs?
- The delimiter is detected from the first line, and you can override it in step 2 if your export uses semicolons (common in European Excel) or tabs.
- What exactly comes out?
- One WKT geometry per line, in the same order as the input features, ready to paste into a PostGIS, DuckDB, Snowflake or BigQuery statement. Features with no geometry are skipped rather than emitted as blank lines.
- Is my file uploaded anywhere?
- No. The CSV is read, converted and written entirely inside this page — there is no upload, no queue, no server-side copy and no size limit imposed by a plan. Large files are parsed in a background worker so the page stays responsive. The only action that transmits anything is Open in Studio, and that happens after you sign in and press it.
- Is there a limit on file size or number of files?
- There is no imposed limit; the practical ceiling is your browser's memory. Files over about 5 MB are handed to a web worker so the interface keeps responding, and you can drop several files at once — each is converted separately and the set can be downloaded as one zip.