Geo Format Converter
Convert a single geospatial file between GeoJSON, KML, GPX, CSV, WKT, TopoJSON, and Shapefile — upload one, pick the output format, and download the result. Shapefiles are automatically reprojected to WGS84 using their .prj file. Any feature the target format can't represent (e.g. a Polygon converted to GPX or CSV) is clearly counted before you download, never silently dropped. Runs entirely in your browser — nothing is uploaded.
Format is detected automatically from the file's extension.
About this tool
This tool converts a single geospatial file between GeoJSON, KML, GPX, CSV, WKT, TopoJSON, and Shapefile — upload one, pick the format you need, and download the result. It exists because these formats show up constantly in different tools that don't talk to each other: a GPS device exports GPX, Google Earth wants KML, most web mapping libraries expect GeoJSON, a database query returns WKT, and traditional GIS software (QGIS, ArcGIS) exports Shapefile bundles. Converting between them by hand means writing a one-off script or hunting for the right online tool. Shapefiles get one extra step other formats don't need: they're commonly stored in a projection other than plain lat/lon (UTM, State Plane, and similar), so this tool reads the bundle's .prj file and reprojects to WGS84 automatically — you'll see a clear note if no .prj was found (coordinates are then assumed to already be WGS84) or if the projection couldn't be read. Not every conversion is lossless either way, and this tool is upfront about that rather than silently dropping data: GPX has no concept of a polygon, and a CSV row can only hold a single point, so converting a Polygon feature to either of those leaves it out — and the exact number of excluded features is always shown before you download. It runs entirely client-side — your file is read and converted locally in your browser and never uploaded anywhere.
Supported formats
- GeoJSON (.geojson, .json) — A FeatureCollection, a single Feature, or a bare geometry — Point, LineString, Polygon, and their Multi- variants, all fully supported both in and out.
- KML (.kml) — One Placemark per feature, for opening directly in Google Earth or any GIS tool that reads KML.
- GPX (.gpx) — Points become waypoints, lines become tracks — GPX has no polygon concept, so Polygon features can't convert to it.
- CSV (.csv) — One row per point, with a lat/lon column plus every property as its own column — lines and polygons can't convert to it, since a CSV row only holds a single point.
- WKT (.wkt) — Well-Known Text — the plain-text geometry format databases like PostGIS produce via ST_AsText(). One geometry per line, no properties.
- TopoJSON (.topojson) — read only — The topology-encoded, quantized variant of GeoJSON used by D3.js and Census/data-journalism exports. Can be converted from, but not to — building valid topology from arbitrary features is a fundamentally different (and much harder) problem than decoding it.
- Shapefile (.zip) — read only — The classic GIS bundle (.shp/.dbf/.prj, zipped). Reprojected to WGS84 automatically when a .prj is present. Export to Shapefile isn't available yet.
What you can do
- Read GeoJSON, KML, GPX, CSV, WKT, TopoJSON, or a Shapefile .zip
- Convert to GeoJSON, KML, GPX, CSV, or WKT
- Format is detected automatically — just upload and pick the output
- One click to download the converted file
- Nothing is uploaded — the whole conversion happens locally in your browser
How to use
Step 1
Upload a file
Add a .geojson, .kml, .gpx, .csv, .wkt, .topojson, or Shapefile .zip — the format is detected automatically.
Step 2
Pick the output format
Choose which format to convert it to.
Step 3
Download
Get the converted file — you'll see the feature count first, and a clear warning if anything can't survive the conversion.
Example
A GeoJSON point like this one:
GeoJSON
{ "type": "Point", "coordinates": [77.5946, 12.9716] }converts to a KML <Point> with the same coordinates, a GPX <wpt lat="12.9716" lon="77.5946">, a CSV row with lat/lon columns, or a WKT POINT (77.5946 12.9716) — pick whichever your destination tool actually needs.
How your data is handled
This tool is labeled 🟢 Browser: your file is read directly using your browser's File API, converted locally, and offered back as a download. It's never uploaded to a server, and nothing about it is retained once you leave the page.
Frequently asked questions
Why does it say some features will be left out?+
The target format can't represent every shape. GPX has no polygon concept at all, and a CSV row can only hold one point — so converting a Polygon or LineString to CSV, or a Polygon to GPX, drops those specific features. The exact count is always shown before you download, never silently.
Why does it say my file is invalid?+
Check the file extension matches its actual content — a renamed file (e.g. a .json file that's really KML) will be detected as the wrong format. Otherwise, the error message names exactly what's missing.
My CSV isn't converting — why?+
It needs a header named "lat"/"latitude" and "lon"/"lng"/"long"/"longitude" to auto-detect coordinates. If your columns are named something else, two dropdowns appear listing every column in your file so you can pick the right ones manually.
Can I convert a Shapefile?+
You can convert from a Shapefile (.zip) to any other format — upload the .zip containing at least a .shp file (a .dbf for attributes and a .prj for projection are read too, if present). Converting to Shapefile isn't available yet.
Why did it warn about my Shapefile's projection?+
Shapefiles are often stored in a projection other than plain lat/lon (UTM, State Plane, etc.), declared in a .prj file. If that file is missing, coordinates are assumed to already be WGS84 lat/lon; if it's present but couldn't be read, coordinates are used as-is — either way, you're told which happened rather than getting silently mis-placed data.
Can I convert several files at once?+
Not in this tool — it's deliberately one file in, one file out, for speed and simplicity. If you want to combine several files into one output, or view them first, use the GeoJSON / KML / GPX / CSV Viewer instead — its Export feature does exactly that.
Is my file uploaded anywhere?+
No — it's read, converted, and offered back as a download entirely in your browser using the File API. It never leaves your device.