Every converter runs 100% in your browser, nothing is uploaded. Pick a conversion below, or start from the home page and drop a file to see the formats it can become.
Google Earth and Google Maps speak KML and KMZ. These converters move data in and out of them: pull the placemarks out of a KMZ into a shapefile or spreadsheet, or turn a shapefile, CSV or GeoJSON into a file you can double-click open in Google Earth. KMZ is just a zipped KML, typically about 16 times smaller.
The everyday GIS and web-map formats: Shapefile, GeoJSON, GeoPackage and the tabular data behind them. Convert between the desktop-GIS standard (Shapefile, a set of 5 files), the web standard (GeoJSON, always WGS84) and the modern single-file database (GeoPackage) without losing geometry or attributes.
CAD drawings (DXF and DGN) store geometry on named layers, with no attribute table and often no coordinate system. These converters bring engineering geometry into GIS and send GIS data back out as a drawing. If the drawing is not georeferenced, set its CRS first so it lands in the right place.
GPX is the language of GPS devices and fitness apps, from Garmin to Strava and Komoot. Convert tracks, routes and waypoints to and from GIS formats. GPX keeps only a fixed set of fields (name, description, elevation, time), so exporting to shapefile, GeoJSON or CSV preserves far more of a dataset's attributes.
Every format keeps some things and cannot store others. This table is the quick version; each converter page has the exact detail for that pair, and the full compatibility matrix covers all 183 combinations.
| Family | Formats | Geometry | Attributes | Styling | Coordinate system | Best for |
|---|---|---|---|---|---|---|
| Google Earth | KML, KMZ | Points, lines, polygons | Yes | Yes (icons, colours, labels) | Always WGS84 | Viewing and sharing in Google Earth |
| Vector GIS | Shapefile, GeoJSON, GeoPackage, GML | Points, lines, polygons | Yes | No (Shapefile), limited elsewhere | Any (Shapefile via .prj; GeoJSON WGS84) | Analysis in QGIS or ArcGIS, web maps |
| Spreadsheet | CSV, Excel | Points (from X/Y columns) | Yes (as columns) | No | None stored (assumed WGS84) | Tabular data, quick edits, sharing |
| CAD | DXF, DGN | Points, lines, polygons | No (layers only) | Layers and colours | Usually none (local units) | Engineering and architectural drawings |
| GPS | GPX | Points, tracks, routes | Fixed fields only | No | Always WGS84 | GPS devices, fitness and navigation apps |
Start from what you are trying to do rather than the file extension. The most common goals map to these tools:
If you are not sure which target format a program wants, the compatibility matrix shows what survives each conversion, and every converter page has a “what changes” table for that exact pair.
GISConverter is a free tool for moving geospatial data between the formats different programs speak. All 50 converters run on your device with a GDAL engine compiled to WebAssembly, the same open-source engine desktop GIS uses, so your files are converted locally and never uploaded. The tools are grouped into families you can jump to above: Google Earth (KML and KMZ), vector GIS (Shapefile, GeoJSON, GeoPackage), CAD (DXF and DGN), GPS (GPX) and spreadsheets (CSV and Excel). Each converter page explains exactly what carries over, geometry, attributes, styling and coordinate system, so you know what to expect before you download.
Yes. Every one of the 50 converters is free and unlimited, with no account, no sign-up and no watermark. There is nothing to install either.
No. Each conversion runs entirely in your browser using a GDAL engine compiled to WebAssembly. Your file is read and converted on your own device and never leaves it, which is why it also works offline once loaded.
Vector, CAD, GPS and spreadsheet formats: KML, KMZ, Shapefile, GeoJSON, GeoPackage, GML, GPX, DXF, DGN, CSV, Excel and more. Raster imagery such as GeoTIFF is not supported, it needs different handling.
Pick the one that matches your source and target format, for example Shapefile to KML. Not sure which target you need? The category hubs and each converter's 'what changes' table explain the trade-offs, and the compatibility matrix shows what survives every conversion.
Yes. Everything runs in the mobile browser the same way it does on a desktop, since the conversion happens on your device. Very large files are limited only by the memory your phone can give the browser.
