Convert Well-Known Text to Well-Known Binary
Free, in-browser conversion from Well-Known Text (.wkt) to Well-Known Binary. Drop a file below — the converted output downloads automatically. No account, no software install, no upload retention for direct conversions.
About Well-Known Text
WKT is the human-readable text format used everywhere in databases — PostGIS's ST_AsText, Spatialite, MySQL spatial, MS SQL Server spatial. Each line is one geometry: POINT(...), LINESTRING(...), POLYGON(...), and their MULTI* and GEOMETRYCOLLECTION variants.
About Well-Known Binary
WKB encodes the same geometries as WKT but as a binary blob — no parsing rounding, smaller payloads, faster to read. PostGIS's ST_AsBinary returns this; GeoParquet uses WKB-encoded geometry columns.
How to convert Well-Known Text to Well-Known Binary
- Drop your Well-Known Text file (.wkt) on the area above, or click to browse.
- The file is parsed server-side — geometries are normalised to a GeoJSON FeatureCollection internally, then written out as Well-Known Binary.
- The converted file downloads automatically. No retention; nothing is kept on the server.
Want to inspect the geometry before converting? Use the full 3D viewer instead — it renders the file on a MapLibre globe with toggleable layers, then lets you convert from the same toolbar.
Related conversions
FAQ
Is the Well-Known Text to Well-Known Binary converter free?
Yes. rooot viewer is free and requires no account. There are no per-conversion charges.
Do I need to install software?
No. The conversion runs server-side, the result is delivered as a download. Works in any modern browser.
Are my files kept after conversion?
Direct conversions through this page (the form above) do not persist files at all — the bytes are parsed in memory and the result returned. Persistence only happens when you use the main viewer's Open in roooute button, and persisted files are deleted within 24 hours.
What is the maximum Well-Known Text file size?
50 MB per file.
Does the converter preserve attribute properties?
Yes — feature properties round-trip through the canonical GeoJSON intermediate. Schema differences between source and target formats may force lossy coercions (e.g. shapefile DBF column-name length limits), but rooot viewer applies sensible defaults.