LazyTools

🔒 Every tool runs in your browser — the files and values you enter are never uploaded to any server. How it works

🧭 GeoJSON to WKT Converter

Paste a GeoJSON geometry (or Feature) and get OGC WKT like POLYGON ((…)) — ready for PostGIS or a spatial query, converted locally.

GeoJSON geometry → OGC WKT

Rate this tool:
Anonymous — no account, no identifier

How the geojson to wkt converter works

The tool parses your GeoJSON and serialises the geometry as OGC Well-Known Text — the format spatial databases and SQL functions (PostGIS ST_GeomFromText, spatial indexes, many GIS tools) expect. It accepts a bare geometry, a Feature (it uses the Feature's geometry), or a FeatureCollection (emitted as a GEOMETRYCOLLECTION), and it preserves X Y (longitude latitude) order and polygon holes. Point, LineString, Polygon and their Multi* variants are all supported.

This is the inverse of the WKT-to-GeoJSON tool and is handy when you have GeoJSON from a web map but need to insert it into a spatial database or pass it to a WKT-based function. Note that WKT represents geometry only, so any Feature properties are dropped in the conversion — the geometry is what carries over. It runs entirely in your browser, keeping location data on your device.

Frequently asked questions

How do I convert GeoJSON to WKT?

Paste a GeoJSON geometry, Feature or FeatureCollection (or load a .geojson file) and the tool outputs the equivalent WKT you can copy or download — for example a Polygon becomes POLYGON ((…)).

Can I paste a Feature or FeatureCollection?

Yes — a Feature is converted using its geometry, and a FeatureCollection becomes a GEOMETRYCOLLECTION of the features' geometries. A bare geometry object works too.

Is this the format PostGIS uses?

Yes — WKT is what functions like ST_GeomFromText('POINT(30 10)') expect, so this output drops straight into PostGIS and other spatial-SQL databases. Add the SRID separately if your column requires one.

What happens to my Feature's properties?

They're dropped, because WKT encodes geometry only — there's nowhere to put attributes. Keep the properties separately (e.g. in the database row) alongside the WKT geometry.

Is my GeoJSON uploaded?

No — the conversion runs locally in your browser and nothing is transmitted.

Related file converters

From the blog