About WKT Studio
WKT Studio is a browser-based GIS map editor for people who work with spatial data in code — backend engineers debugging a PostGIS query, data engineers checking a pipeline's output, analysts who need to look at a geometry once without installing anything.
Why it exists
The usual way to check whether a geometry is correct is to open QGIS, create a project, set up a PostGIS connection, and load a layer. That is a reasonable workflow for cartography and a disproportionate one for answering “did ST_Buffer do what I expected?”
WKT Studio started as the shortest path between a SELECT ST_AsText(geom) result and a map you can look at. It grew into a full editor — layers, an attribute table, spatial analysis, a REST API and team sharing — but that original constraint still drives it: paste something, see it immediately, no setup.
Standards we follow
- OGC Simple Features for WKT parsing and output — all seven geometry types, with ring-closure and axis-order rules enforced as the specification defines them.
- RFC 7946 for GeoJSON, including the longitude-then-latitude coordinate order that trips up most people coming from a lat/lng API.
- EPSG:4326 (WGS 84) as the working coordinate reference system for every stored and exported geometry.
- PostGIS compatibility for SQL output — generated statements use
ST_GeomFromTextwith an explicit SRID and quoted identifiers.
How your data is handled
The free tools — the WKT viewer, the converter, the GeoJSON and Shapefile viewers — parse files entirely in your browser. Nothing is uploaded to a server unless you sign in and explicitly save a project.
Saved projects are private by default. Making one public is an explicit action, and public projects are the only ones that appear in the gallery. Full detail is in the privacy policy.
Who writes this
Fidel Roman
Founder & Engineer, WKT Studio
I build and maintain WKT Studio, and I write every guide on this site. The tool came out of my own work with spatial data in PostgreSQL and PostGIS — the guides cover the problems I hit there first-hand: axis order, invalid rings, choosing between ST_AsText and ST_AsGeoJSON, and getting geometry out of a database and onto a map without a desktop GIS in the way. Every SQL and Python snippet published here has been run before it shipped.
Contact
Questions, bug reports, and feature requests all go to support@wktstudio.com. Pro subscribers get priority. Billing is handled by Paddle as merchant of record — see the refund policy and terms of service.