Open Geo Files Online and Export Standalone HTML Maps

Use this geo file viewer directory to open your format, inspect its tracks, points and polygons on an interactive map, then export one self-contained HTML map file. The map engine, styles and your features are inlined into a single page. Double-click the export to open it, with or without internet. No Google Earth, no QGIS, no GIS server, no account: processing stays in your browser.

NMEA & AIS tools — maps, message inspection and vessel playback.

NMEA tools

Choose the workflow that matches your NMEA log. All three tools parse locally in your browser.

Choose your format

How it works

STEP 1

Drop your file

Open the tool for your format and drop the file in. It is parsed locally — nothing is uploaded.

STEP 2

Preview the map

Features render instantly on an interactive map with popups, tooltips and a summary of what was found.

STEP 3

Export one HTML file

Download a single standalone .html map. "No basemap" mode makes it fully offline — email it, archive it, open it anywhere.

Why a standalone HTML map?

Geo files are awkward to share. A shapefile arrives as a folder of parts, KML needs Google Earth, and FIT needs Garmin software — every recipient needs their own install. A standalone HTML map inverts that: everything (the map engine, the styles, your data) is inlined into one file that any browser opens. Send it to a customer who has never heard of GeoJSON, upload it to a static host, or keep it for ten years — it will still open exactly the same.

And because every tool here processes files in the browser, sensitive locations — site plans, customer lists, field data — never pass through a server. You can watch the network tab; nothing carries your file.

FAQ

Which tool do I need for my file?

Match by extension: .kml → KML tool, .kmz → KMZ viewer, .gpx → GPX tool, .nmea or a NMEA text .log → NMEA map tool, .tcx → TCX viewer, .fit → FIT viewer, .shp or a shapefile .zip → Shapefile tool, .geojson → GeoJSON tool, .geobuf → Geobuf tool, .csv → CSV tool or the address list tool (if it contains addresses rather than coordinates), .xlsx → Excel tool.

Is anything uploaded to a server?

No files are uploaded in any of these tools. One exception to be precise about: the address list tool converts address text into coordinates via the public OpenStreetMap geocoding services, so the address text itself is sent for lookup — that page explains it in full. Coordinate rows and all other tools never touch the network.

Can the exported map really work offline?

Yes. Export with "Offline (no basemap)" and the HTML file has zero external requests: the map engine and your data are inlined, and features draw on a clean background. Basemap tiles (OSM or satellite) are an optional extra for online viewing.

The Satellite imagery option shows a blank map — what's wrong?

The satellite tiles come from Esri's free World Imagery service, which is unavailable on some networks (parts of mainland China, for example, can't reach arcgisonline.com). It is a network reachability issue, not a bug — the same view works on other networks. If you need satellite imagery in the exported file, export while your network can reach it; for a basemap that never depends on the network at all, use "Offline (embedded tiles)" or "Offline (no basemap)".

I double-clicked the exported file and the basemap tiles don't load — why?

The OpenStreetMap tile server rejects requests that come from locally opened files (file:// pages send no Referer, which their policy requires). The exported map handles this automatically: street tiles switch to a fallback source so the map still shows. To get official OSM tiles instead, serve the file over http(s) — the fastest way is a local server. Save this as serve-map.bat next to your map file, double-click it, and open the address it prints:

@echo off start http://localhost:8899/map.html python -m http.server 8899

Any static hosting (Cloudflare Pages, GitHub Pages, Netlify) works too — the export is one plain HTML file.

Is there a file size limit?

No hard limit — files are processed in your browser's memory, so the practical ceiling is your device's RAM and browser. Large files load fine on a modern machine; exports include the first 1,000 features in each file.