free · in-browser · no upload
Drop your WKT file. We'll convert it to GeoJSON right here in your browser, your file never leaves your device.
Select your file here to get started
or drop your file here.
Accepts .wkt, .txt
How it works
Click the dropzone above or drag a WKT from your desktop. Files of any size, there's no upload, so there's no upload limit.
The conversion runs entirely in this tab using JavaScript and WebAssembly. Your file never touches our servers, we don't have any.
Get your GeoJSON the moment the conversion finishes. Convert another, or close the tab.
Your file is never uploaded. The entire conversion runs in your browser using WebAssembly. We can't see what you convert because we have no server to see it.
Server converters cap free users at 1-2 GB and gate larger files behind a paid plan. Since nothing uploads, our limit is whatever your browser can handle.
No account required. No watermark on the output. No queue. Drop a file, get a converted file.
Why convert WKT → GeoJSON
WKT (Well-Known Text) is the OGC standard text encoding for geometry, used by PostGIS, Oracle Spatial, SQL Server, and GeoPandas. GeoJSON is what every web map (Leaflet, Mapbox, OpenLayers) actually consumes. This converts one to the other so you can take a literal pulled from a database column and plot it on a map.
You copied a POLYGON((...)) literal out of a PostGIS query and want to verify it visually. Paste it into a .wkt file, convert here, drop the resulting GeoJSON into geojson.io or your Leaflet build.
"Could not parse the input as WKT" error.
WKT must start with a geometry type keyword (POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, GEOMETRYCOLLECTION). EWKT prefixes like SRID=4326; are not part of WKT proper, strip them first.
Formats involved
WKT is a file format we support converting. Detailed format information is being added, for now, drop your file in the converter above and you'll get the conversion you came for.
How to open
Most operating systems open this format with a default application; if not, search for a free reader/viewer for the format.
GeoJSON encodes geographic features (points, lines, polygons) as JSON objects following RFC 7946 (2016). Coordinates are always [longitude, latitude] in WGS84. Supported natively by Leaflet, Mapbox GL, OpenLayers, ArcGIS, QGIS, and PostGIS — the default exchange format for web mapping. Lighter and easier to inspect than KML or shapefile (.shp).
How to open
GitHub renders GeoJSON files inline as interactive maps. geojson.io provides an in-browser editor + validator. QGIS opens .geojson directly. Leaflet/Mapbox apps consume it programmatically.
You may also need
Related tools
FAQ
Yes. No signup, no watermark, no daily file count limit. Every conversion runs in your browser, your file never touches our servers because there are no servers.
Nowhere. The conversion runs entirely in your browser using JavaScript and WebAssembly. Your file is never uploaded to our servers. We don't have any servers handling files, there's nothing for us to log, store, or accidentally leak.
Whatever your browser can hold in memory. Practically, this means a few hundred MB on most computers, significantly larger than the 1-2 GB caps that server-upload converters charge for. Very large files (multi-GB) may require closing other browser tabs first.
File interchange. Web mapping data exchange (Leaflet, Mapbox, ArcGIS). The most common reason to convert is compatibility, GeoJSON works in places where WKT doesn't, or vice versa.
Most operating systems open this format with a default application; if not, search for a free reader/viewer for the format.
Once the page is loaded, the conversion itself runs entirely offline. The first time you use a tool, your browser downloads the conversion library (a one-time cache). If you reload while offline, the page won't load, but you can install the site as a Progressive Web App for full offline use.
Single file at a time for now. Batch conversion is on the roadmap, for now, drop one file, download the result, then convert the next.
