GIS & Map Data: GeoJSON, KML & Shapefiles
Geographic coordinates, vector layers, and spatial mapping standards.
Files are processed locally in your browser with WebAssembly and HTML5 APIs. They never leave your device, so there are no server uploads or third-party file storage.
Start converting immediately on your own device - no upload wait, no download queue, and no throttling by a remote server.
Use every available tool without creating an account, paying for a plan, or hitting an artificial file-size limit. Convert as often as your browser and device can handle.
Format Comparison & Technical Specifications
| Output Format | MIME Type | Specification | Type |
|---|---|---|---|
| GeoJSON GeoJSON | application/geo+json | RFC-7946-GEOJSON | Geographic JSON Standard |
| KML Google | application/vnd.google-earth.kml+xml | OGC-KML-SPEC | Keyhole Markup Language |
| GPX GPS Track | application/gpx+xml | TOPOGRAFIX-GPX-SPEC | GPS Exchange Format |
| SHP ESRI Shapefile | application/x-esri-shapefile | ESRI-SHAPEFILE-SPEC | ESRI Spatial Vector Shape |
| TopoJSON TopoJSON | application/json | RFC-7946-GEOJSON | Topological Geographic JSON |
Technical Specifications & Codec Breakdown
GeoJSON vs. Google Earth KML
GeoJSON models geographic boundaries, points, and paths using standard web JSON syntax, making it the favorite for interactive web maps like Leaflet and Mapbox. KML is XML designed for Google Earth, bundling 3D terrain and camera angles.
The Longitude/Latitude Ordering Trap
While humans say 'Latitude, Longitude' (Y, X), computer geometry standards (including GeoJSON and GeoTIFF) strictly require '[Longitude, Latitude]' (X, Y). Reversing this coordinate order can place your map pins in Antarctica instead of New York.
0 bytes uploaded to external servers. All processing occurred locally in your browser sandbox.