Skip to content
Spatly

Convert WKT to GeoJSON

1

Add your WKT

Drop WKT geometry anywhere on this page

.wkt · .txt · it never leaves the browser

2

Options

≈ 11 cm on the ground
Keep every vertex
00verticesunchanged
3

Your GeoJSON

Add WKT geometry and the GeoJSON appears here, with its feature counts and anything this pair cannot carry.

Converted in this tab. Your WKT is never uploaded — reading, converting and writing all run in the browser, so this works offline once the page has loaded.
— , —
FidelityWKT → GeoJSON

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.
  • Feature order is preserved, so a row in the output is the same feature as the row in your input.

Worth knowing

  • Nothing measurable. Both WKT and GeoJSON carry geometry and a full attribute table, so this conversion is lossless apart from any coordinate rounding or simplification you ask for.

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

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

AlsoGeoJSON to WKTShapefile to GeoJSONKML to GeoJSONWKT to KMLAll conversions
HowHow it works

Convert WKT to GeoJSON, step by step

  1. Step 1

    Add your WKT

    Drop WKT geometry anywhere on the page, paste it, point at a URL, or press Sample to start from real data. Several files at once are fine.

  2. Step 2

    Set what matters

    Coordinate precision and simplification on every pair, plus the handful of settings this one needs.

  3. Step 3

    Take the GeoJSON

    Read the feature counts and the warning list, then download, copy, or open the result in the Spatly studio to style and publish it.

PrivateRuns in your browser

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.

Go furtherTurn a GeoJSON into an interactive mapRead the guide
FAQQuestions

Good to know

What is preserved when converting WKT to GeoJSON?
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. Feature order is preserved, so a row in the output is the same feature as the row in your input.
What is lost converting WKT to GeoJSON?
Nothing measurable. Both WKT and GeoJSON carry geometry and a full attribute table, so this conversion is lossless apart from any coordinate rounding or simplification you ask for.
What does the input look like?
One geometry per line, in the OGC text form — POINT (30 10), LINESTRING (30 10, 10 30), POLYGON ((30 10, 40 40, 20 40, 30 10)) — with or without an SRID prefix. Blank lines are skipped, so you can paste a column straight out of a SQL client.
Can I attach names to the geometries?
Not in WKT itself — it holds shape and nothing else. If you need attributes alongside the geometry, put the WKT in one column of a CSV and use the CSV converter instead.
Is the GeoJSON valid RFC 7946?
Yes: a single FeatureCollection, coordinates as [longitude, latitude], no CRS member — the RFC dropped it and mandates WGS84. Use the GeoJSON editor afterwards if you also want winding order and ring closure checked.
Is my file uploaded anywhere?
No. The WKT 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.