Add your GEOJSON file
Drop one or more .geojson files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
GEOJSON to WKT
Converting a .geojson font to .wkt repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
Private for supported formats — processed in your browser
Runs on your deviceConvert supported files
Drop GEOJSON files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.About converting GeoJSON to Well-Known Text geometry
Converting a .geojson font to .wkt repackages the same glyphs and metrics for a different delivery target. A .geojson file encodes geographic features as JSON: geometries such as Point, LineString and Polygon, each optionally carrying a free-form properties object, usually collected in a FeatureCollection. It is the format web mapping actually runs on.
A .wkt file holds Well-Known Text: geometry written as a compact human-readable string, such as POINT (30 10) or POLYGON ((30 10, 40 40, 20 40, 30 10)). It describes shape only — there are no attributes, no styling and no feature collection wrapper. For this route the practical draw is compact and genuinely readable for simple geometry and understood natively by every spatial database — balanced against no attributes, no styling and no way to group features, which is worth knowing before you commit a large batch.
Why convert GEOJSON to WKT?
The practical trigger for this conversion is usually a mismatch: with .geojson, verbose and large for dense geometry, with no built-in compression. Switching to .wkt buys you compact and genuinely readable for simple geometry, which is why it is the better fit for typing or reading a geometry directly in a spatial SQL query. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
GEOJSON vs WKT at a glance
| Aspect | GeoJSON (.geojson) | Well-Known Text geometry (.wkt) |
|---|---|---|
| Format type | Text-based — characters and structure, so there is no visual quality loss | Text-based — characters and structure, so there is no visual quality loss |
| How it stores data | coordinate order is longitude, latitude — the reverse of how people say it, and the single most common source of bugs | geometry types are POINT, LINESTRING, POLYGON, their MULTI- variants, and GEOMETRYCOLLECTION |
| Strongest at | rendering geographic data in Leaflet, Mapbox or OpenLayers | typing or reading a geometry directly in a spatial SQL query |
| Weak spot | verbose and large for dense geometry, with no built-in compression | no attributes, no styling and no way to group features |
| Metadata | geometry and the properties object are preserved. Styling is not part of the format, so a conversion from KML loses that presentation information rather than GeoJSON dropping it | geometry and dimensionality are preserved, along with an EWKT SRID where one is present. There are no attributes in the format to carry |
Pick WKT as the output
Select .wkt in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if WKT is selectable, the route is real and validated.
Convert on your device
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Verify and download
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid WKT file. Outputs keep the original filename with the .wkt extension.
GEOJSON to WKT questions, answered
Will converting GEOJSON to WKT lose quality?
There is no visual quality to lose — geojson is text-oriented and wkt is text-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Is it private to convert GEOJSON files here?
Yes — the .geojson file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Where will the WKT file work?
Supported by PostGIS, Oracle Spatial, SQL Server, GDAL, Shapely and JTS. Web mapping libraries expect GeoJSON. Novus Convert parses WKT and bounded EWKT locally, validating coordinates and dimensions, and converts to GeoJSON.
Will the WKT file be bigger or smaller than my GEOJSON?
It depends on the content: geometry types are POINT, LINESTRING, POLYGON, their MULTI- variants, and GEOMETRYCOLLECTION. Convert one representative file first and compare before batch-processing a large set.
What happens to the metadata in my GEOJSON file?
In .geojson, geometry and the properties object are preserved. Styling is not part of the format, so a conversion from KML loses that presentation information rather than GeoJSON dropping it. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.
Can I convert WKT back to GEOJSON?
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .geojson → .wkt → .geojson is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.