Add your GeoJSON
Drop a GeoJSON file anywhere on this page
.geojson · .json · it never leaves the browser
Options
Your WKT
Add a GeoJSON 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, lines and polygons come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude.
- Elevation (the Z ordinate) is preserved where the source has one.
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.
GeoJSON (RFC 7946)
The web's lingua franca for vector data: plain JSON, WGS84 longitude/latitude, every geometry type, and an untyped property bag per feature. It carries no styling — colour and symbology belong to the map, not the file.
.geojson · .json · application/geo+json
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 GeoJSON to WKT, step by step
- Step 1
Add your GeoJSON
Drop a GeoJSON 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.
- 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 GeoJSON to WKT?
- Geometry — points, lines and polygons come across coordinate for coordinate; nothing is reprojected, because both sides are WGS84 longitude/latitude. Elevation (the Z ordinate) is preserved where the source has one.
- What is lost converting GeoJSON 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.
- Does the file have to be a FeatureCollection?
- No. A bare geometry, a single Feature, an array of geometries or a FeatureCollection are all accepted, and a common API envelope such as { data: … } is unwrapped for you.
- 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 GeoJSON 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.