BYTETOOLS

WKT to GeoJSON Converter

Convert WKT geometry to GeoJSON in your browser. Supports all seven geometry types, Z and M dimensions, EMPTY geometries and EWKT SRID prefixes.

Drop a .wkt or .txt file here, or click to browseConverted locally — the file is never uploaded

What is the WKT to GeoJSON Converter?

Well-Known Text is what a PostGIS, Oracle Spatial or SQL Server query hands you when you ask for a geometry as text.

  • All seven WKT geometry types including GEOMETRYCOLLECTION
  • Z and M dimension tags and EMPTY geometries handled
  • Accepts the EWKT SRID=… prefix from PostGIS output
  • Converts many geometries at once into a FeatureCollection
  • Precise parse errors that name the offending character
  • 100% client-side — geometry is never uploaded

How to use the WKT to GeoJSON Converter

  1. 1

    Paste one or more WKT geometries into the box, one per line, or drop a .wkt file.

  2. 2

    Choose whether to wrap the result in a Feature or FeatureCollection.

  3. 3

    Click Convert to GeoJSON — any syntax error is reported with its character position.

  4. 4

    Copy the GeoJSON or download it as a .geojson file.

About the WKT to GeoJSON Converter

Well-Known Text is what a PostGIS, Oracle Spatial or SQL Server query hands you when you ask for a geometry as text. GeoJSON is what Leaflet, Mapbox, OpenLayers and every modern web map want. This converter bridges the two, parsing POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON and GEOMETRYCOLLECTION into valid GeoJSON.

It handles the awkward corners of the format too: Z and M dimension tags, EMPTY geometries, the EWKT SRID=4326; prefix that PostGIS adds, and both spellings of MULTIPOINT. Paste several geometries — one per line — and you get a FeatureCollection back. Parse errors point at the exact character that broke, instead of failing silently.

Developers use it to eyeball query output on a map, GIS analysts use it to move data between desktop and web tooling, and students use it to see how the two notations line up. Everything is parsed locally in your browser, so proprietary geometry never leaves your machine.

Frequently asked questions

How do you convert WKT to GeoJSON?

Parse the WKT keyword and its nested coordinate lists, then emit the matching GeoJSON type with the same positions in [longitude, latitude] order. Paste your WKT above and the converter does it instantly, including nested collections.

What is the difference between WKT and GeoJSON?

WKT is a compact text notation used inside spatial databases and OGC standards. GeoJSON is a JSON document format designed for the web, which additionally carries feature properties. Both use the same longitude, latitude coordinate order.

Does WKT use latitude or longitude first?

For geographic data in EPSG:4326 the convention — and what PostGIS produces — is longitude first, matching GeoJSON. So POINT (-74.006 40.7128) is New York. If your points land in the wrong ocean, the two values are swapped.

What does the SRID=4326 prefix mean?

That is EWKT, PostGIS's extension that tags the geometry with a spatial reference ID. 4326 is WGS-84 longitude/latitude, which is exactly what GeoJSON requires. This tool strips the prefix and warns you if the SRID is anything else, since GeoJSON cannot represent other projections.

Can it handle POLYGON with holes?

Yes. The first ring in a WKT polygon becomes the GeoJSON exterior ring and every additional ring becomes a hole, which is exactly how GeoJSON represents donut shapes, lakes and exclusion zones.

Is my geometry uploaded anywhere?

No. Parsing and conversion happen entirely in client-side JavaScript, so parcel boundaries, utility networks and unreleased project data stay on your device. The tool also works with no internet connection.

Related tools