GeoJSON, KML and GPX Converter

How to convert GeoJSON, KML, GPX, CSV and WKT

1. Drop a file on the drop zone or paste data into Input data. Files are read by your browser and never uploaded.
2. Leave From on Detect automatically, or pick the input format yourself. Detection looks at the first characters: { or [ means GeoJSON, <gpx means GPX, other XML is read as KML, a keyword such as POINT or MULTIPOLYGON means WKT, and anything else is treated as CSV.
3. Choose the output format under To. The result appears as you type; Convert runs it again.
4. Check the counts (Features, Points, Lines, Polygons, Vertices) and the preview drawing, then Copy the result or Download it with the right extension.

What each format keeps

All conversions go through GeoJSON (RFC 7946) as a common model: a list of features, each with an optional geometry and a set of properties. Points, LineStrings, Polygons (with holes), MultiPoints, MultiLineStrings, MultiPolygons and GeometryCollections are supported. Coordinates are longitude, latitude and an optional altitude, in WGS 84 degrees; the tool does not reproject.

• GeoJSON: everything is kept, including nested properties and feature ids.
• KML: each feature becomes a Placemark. The name and description properties map to the KML elements of the same name; other properties go into ExtendedData. Multi geometries become MultiGeometry. When reading, the tool walks every Folder, reads Data and SimpleData values, and also understands Google Earth gx:Track recordings. Styles, icons, ground overlays and network links are ignored. KMZ is a zipped KML: unzip it first.
• GPX: points become waypoints (wpt, with ele, name and desc), lines become tracks (trk) and a MultiLineString becomes one track with several segments. When reading, waypoints, routes (rte) and tracks are all converted, with the elevation as a third coordinate. GPX has no polygons, so polygon rings are written as track segments and a warning says so.
• CSV: when every feature is a point, the output has latitude and longitude columns (plus elevation if present) followed by one column per property. Mixed data gets a wkt column instead. When reading, coordinate columns named lat/latitude/y and lon/lng/long/longitude/x are recognised in any case, as well as a wkt or geometry column. A decimal comma such as 46,8139 is accepted. Rows without coordinates are skipped and counted.
• WKT: one geometry per line. The reader accepts Z and M variants, EMPTY geometries and a PostGIS-style SRID=4326; prefix. WKT has no attributes, so properties are dropped on output.

Tips and limits

• WKT and GeoJSON both write longitude first. If your points land in the ocean off Africa or at the wrong pole, the source probably had latitude and longitude swapped.
• The preview is a simple drawing without a base map, useful to spot swapped coordinates, stray points or unclosed shapes at a glance.
• Files up to 20 MB are accepted. Very large files may take a few seconds, since the text output is built in memory.