WKT stands for Well-Known Text, a compact text markup for vector geometry defined by the OGC. Values look like POINT(30 10) or POLYGON((30 10, 40 40, 20 40, 10 20, 30 10)), and spatial databases such as PostGIS use it to represent points, lines, and polygons.

How is GeoJSON different from WKT?

GeoJSON expresses the same geometries as a JSON object with a type and a coordinates array, and adds Feature and FeatureCollection wrappers for attributes. Web maps and Leaflet read GeoJSON directly, whereas WKT is a plain string, so this converter translates between the two.

Does it support EWKT or an SRID prefix?

It parses standard WKT, including the Z and M dimensions. EWKT strings that carry an SRID=...; prefix in a non-WGS84 projection are not reprojected, because GeoJSON is always longitude/latitude, so convert those coordinates to EPSG:4326 first.

How does it convert a GeoJSON FeatureCollection to WKT?

WKT has no FeatureCollection concept, so a collection with several features is combined into a single GEOMETRYCOLLECTION containing each feature's geometry. A collection with just one feature is emitted as that single geometry.

Which coordinate order do WKT and GeoJSON use?

Both use longitude first, then latitude — that is, x y — not the lat/long order people often speak in. If converted points appear in the wrong spot, the input axes were probably reversed at the source.

Is my geometry uploaded when I convert it?

No. The WKT to GeoJSON conversion runs entirely in your browser, so the coordinates you paste or load from a file are processed locally on your device and are never sent anywhere.

WKT to GeoJSON Converter Online

Convert WKT (Well-Known Text) to GeoJSON and back in your browser. Your geometry stays on your device.

Your WKT and GeoJSON are converted locally in your browser and never uploaded, so spatial data from internal projects stays on your device.

Need to see a coordinate on a map? Try the Coordinate Map Viewer.

About WKT to GeoJSON

This WKT to GeoJSON converter turns Well-Known Text geometries into GeoJSON, and can also run the other direction to produce WKT from GeoJSON. Paste a POINT, LINESTRING, POLYGON, MULTIPOLYGON, or GEOMETRYCOLLECTION, or load a .wkt / .txt / .geojson / .json file, and the matching output appears beside it. WKT is the compact text format databases like PostGIS and spatial tools emit, while GeoJSON is what web maps, Leaflet, and geojson.io expect, so as a WKT to GeoJSON converter it bridges the two without a database round-trip. WKT input is wrapped as a GeoJSON Feature; GeoJSON input can be a bare geometry, a Feature, or a FeatureCollection. Everything is parsed on your device, so the coordinates you paste are processed locally and never leave your browser.

Features

Converts WKT to GeoJSON and GeoJSON to WKT with a single direction toggle
Handles POINT, LINESTRING, POLYGON, and the MULTI* and GEOMETRYCOLLECTION variants
Wraps parsed WKT geometry as a GeoJSON Feature so it drops straight into maps and geojson.io
Accepts a bare GeoJSON geometry, a Feature, or a whole FeatureCollection as input
Collapses a multi-feature FeatureCollection into one WKT GEOMETRYCOLLECTION
Load a .wkt, .txt, .geojson, or .json file with Choose file instead of pasting
Pretty-prints and syntax-highlights the GeoJSON output for easy scanning
Copy the result or download it as data.geojson or data.wkt with one click

How to use the WKT to GeoJSON

Pick a direction: WKT → GeoJSON or GeoJSON → WKT.
Paste your geometry into the input box, or use Choose file to load one.
Read the converted output in the panel on the right.
Click Copy to grab it, or download it as data.geojson or data.wkt.

Example

Input

POLYGON((30 10, 40 40, 20 40, 10 20, 30 10))

Output

{
  "type": "Feature",
  "properties": {},
  "geometry": {
    "type": "Polygon",
    "coordinates": [
      [
        [30, 10],
        [40, 40],
        [20, 40],
        [10, 20],
        [30, 10]
      ]
    ]
  }
}

A WKT POLYGON becomes a GeoJSON Feature with a Polygon geometry.

Common errors & troubleshooting

The output says "Could not parse WKT". — Check the geometry keyword and brackets — POLYGON needs a double set, POLYGON((x y, ...)), and coordinates are space-separated as x y (longitude first).
GeoJSON → WKT reports "No geometry found". — Make sure you pasted a geometry, a Feature, or a FeatureCollection. A bare properties object or a URL is not GeoJSON the converter can read.
An EWKT string with an SRID prefix will not convert. — Strip the SRID=...; prefix, or reproject the coordinates to WGS84 (EPSG:4326) first — GeoJSON is always longitude/latitude, so alternative projections are not supported here.
Coordinates look swapped on the map. — WKT and GeoJSON both order coordinates as longitude then latitude (x y), not lat/long. If points land in the wrong place, your source data likely had the axes reversed.

Frequently asked questions

What is WKT?: WKT stands for Well-Known Text, a compact text markup for vector geometry defined by the OGC. Values look like POINT(30 10) or POLYGON((30 10, 40 40, 20 40, 10 20, 30 10)), and spatial databases such as PostGIS use it to represent points, lines, and polygons.
How is GeoJSON different from WKT?: GeoJSON expresses the same geometries as a JSON object with a type and a coordinates array, and adds Feature and FeatureCollection wrappers for attributes. Web maps and Leaflet read GeoJSON directly, whereas WKT is a plain string, so this converter translates between the two.
Does it support EWKT or an SRID prefix?: It parses standard WKT, including the Z and M dimensions. EWKT strings that carry an SRID=...; prefix in a non-WGS84 projection are not reprojected, because GeoJSON is always longitude/latitude, so convert those coordinates to EPSG:4326 first.
How does it convert a GeoJSON FeatureCollection to WKT?: WKT has no FeatureCollection concept, so a collection with several features is combined into a single GEOMETRYCOLLECTION containing each feature's geometry. A collection with just one feature is emitted as that single geometry.
Which coordinate order do WKT and GeoJSON use?: Both use longitude first, then latitude — that is, x y — not the lat/long order people often speak in. If converted points appear in the wrong spot, the input axes were probably reversed at the source.
Is my geometry uploaded when I convert it?: No. The WKT to GeoJSON conversion runs entirely in your browser, so the coordinates you paste or load from a file are processed locally on your device and are never sent anywhere.

Related tools

GeoJSON to CSV — Convert a GeoJSON FeatureCollection to CSV and back — Point features become latitude/longitude columns with their properties.
GPX to GeoJSON — Convert GPX to GeoJSON and back — GPS tracks, routes and waypoints to GeoJSON features, or GeoJSON back to a GPX file.
KML to GeoJSON — Convert KML ⇄ GeoJSON — turn Google Earth KML into GeoJSON for web maps, or GeoJSON back into KML.
Coordinate Map Viewer — Plot a latitude/longitude on an OpenStreetMap map, or click the map to read coordinates back out.
JSON Formatter — Beautify, minify and validate JSON with error locations.