GeoJSON to WKT Converter
Turn GeoJSON features into Well-Known Text for SQL inserts and PostGIS — one WKT per line, ready for ST_GeomFromText. Client-side, free.
Paste data or open a file
Everything parses in your browser — files are never uploaded.
Field guide: GeoJSON to WKT Converter
The last meter of many geo pipelines is an INSERT statement: the API handed you GeoJSON, the table wants geometry, and ST_GeomFromText wants WKT. This converter emits exactly that — one WKT literal per feature, POINT/LINESTRING/POLYGON with the spec's X Y (longitude latitude) ordering, paste-ready inside ST_GeomFromText('…', 4326) for PostGIS, MySQL or SQL Server spatial alike.
The CSV export pairs each feature's WKT-relevant coordinates with its properties, which covers the other common destination: a staging table loaded via COPY where geometry gets constructed in SQL. Everything converts in the browser; the preview-and-count step before export catches the empty-geometry and swapped-axis surprises that otherwise surface as constraint violations at 5 p.m.
Field tips
- Wrap output as ST_GeomFromText('POINT (77.209 28.6139)', 4326) — supplying the SRID explicitly avoids the 'mixed SRID' errors that haunt new PostGIS tables.
- Multi-feature collections export one WKT per line — pair with properties via the CSV export when each geometry needs its attributes in the same INSERT.
- Validate after load: SELECT ST_IsValid(geom) — hand-drawn polygons occasionally self-intersect, and catching it at load beats finding it in a JOIN.
Records are stored only in this browser (localStorage) — export regularly. This tool aids field documentation; it does not replace your agency's official inspection procedures or engineering judgment.
GeoJSON to WKT Converter — Turn GeoJSON features into Well-Known Text for SQL inserts and PostGIS — one WKT per line, ready for ST_GeomFromText. Client-side, free. Free, offline-first and GPS-aware: open it on any phone, log in seconds, and hand your GIS team clean GeoJSON.
About GeoJSON to WKT Converter
The last meter of many geo pipelines is an INSERT statement: the API handed you GeoJSON, the table wants geometry, and ST_GeomFromText wants WKT. This converter emits exactly that — one WKT literal per feature, POINT/LINESTRING/POLYGON with the spec's X Y (longitude latitude) ordering, paste-ready inside ST_GeomFromText('…', 4326) for PostGIS, MySQL or SQL Server spatial alike.
How to use GeoJSON to WKT Converter
- 1Open the tool — it loads instantly and runs entirely in your browser.
- 2Enter or import your field data; everything stays on your device.
- 3Review the computed results and flagged items.
- 4Export to CSV/GeoJSON or print a report for stakeholders.
Why use GeoJSON to WKT Converter?
- ✓100% free, no sign-up — built for crews, not per-seat licences
- ✓Offline-first: records save to your device instantly and survive dead zones
- ✓One-tap GPS tagging with accuracy capture on every record
- ✓Exports CSV for asset systems, GeoJSON for GIS, and print-ready reports
- ✓Checklist and guidance aligned with OGC 06-103r4
Frequently asked questions
What's the coordinate order in the output?+
X Y — longitude then latitude — per the OGC Simple Features WKT spec and PostGIS convention. GeoJSON uses the same lon-first order, so the conversion is direct with no axis swapping. (The lat-first confusion belongs to GPS-display and some legacy WMS conventions, not WKT.)
How do I bulk-insert the results into PostGIS?+
Two well-worn paths: (1) wrap each line — INSERT INTO t(geom) VALUES (ST_GeomFromText('…',4326)); — easily templated in any editor with multi-cursor; (2) load the CSV export into a staging table via \copy, then INSERT … SELECT ST_GeomFromText(wkt_column, 4326). Path 2 wins past a few hundred rows.
Are MultiPolygons and holes handled?+
Multi-geometries are flattened to individual single geometries (one WKT line each) and polygons export their outer ring — predictable behavior for the dominant use cases. Geometry needing full multi-part/ring fidelity should travel as GeoJSON into ST_GeomFromGeoJSON instead, which PostGIS also speaks natively.
GeoJSON vs WKT — why do databases prefer WKT?+
History and SQL ergonomics: WKT predates GeoJSON, is enshrined in the SQL/MM standard, and embeds cleanly in SQL strings. Modern PostGIS accepts both (ST_GeomFromGeoJSON exists), so the real answer is: use whichever your codebase already passes around — this converter exists for when that answer is WKT.
Embed GeoJSON to WKT Converter on your website
Want GeoJSON to WKT Converteron your own site? Paste this snippet into any HTML page — it's free, with no API key or sign-up. The tool loads in an iframe and keeps working exactly as it does here.
<iframe src="https://tooljolt.com/tools/geojson-to-wkt" width="100%" height="640" style="border:1px solid #e5e7eb;border-radius:12px;max-width:680px" title="GeoJSON to WKT Converter — ToolJolt" loading="lazy"></iframe>Related GIS tools
Shapefile to GeoJSON Converter
Convert ESRI shapefiles (.shp + .dbf or zipped) to GeoJSON in your browser — attributes preserved, nothing uploaded. Free, no size games.
● LiveShapefile Viewer
Open and inspect ESRI shapefiles online without ArcGIS or QGIS — feature counts, attributes and GeoJSON preview, 100% in your browser.
● LiveKMZ to KML Converter
Extract the KML from any KMZ file in your browser — see bundled icons/overlays too. No upload, no Google Earth install needed.
● Live