GeoJSON to HTML Map Converter

Turn a GeoJSON file into one standalone HTML map — points become clickable markers, lines become paths, and polygons become colored areas with translucency. The exported file inlines the Leaflet engine, styles, and all features, so it double-clicks open and works offline with zero external requests. Ideal for GIS exports, QGIS work, survey files, and developer test data. Everything runs locally; your data is never uploaded.

What Properties Should My GeoJSON Include?

GeoJSON features are self-describing: their geometry defines the shape and their properties object holds your data. Geometry types are color-coded automatically, so properties are entirely up to you.

Property / part	Role	Required?
`geometry`	Any of Point, MultiPoint, LineString, MultiLineString, Polygon, MultiPolygon. Coordinates use `[longitude, latitude]` order.	✅ Yes
`properties.name` or `properties.title`	Hover label	Optional
any other keys in `properties`	Shown in the click popup (up to 12 per feature)	Optional

Download the template above (the "Download GEOJSON template" button) and replace the sample features with your own.

How to Convert GeoJSON to an HTML Map

Drop your .geojson file — FeatureCollection, single Feature, and bare Geometry objects all work. You can also paste the JSON text directly.
Check the feature summary — the status bar lists how many points, lines, and polygons your file contains. The preview table shows the first 30 features and their properties. More than 1,000 features is fine for preview; the free export takes the first 1,000.
Preview the map — points render as colored circle markers, lines as polylines, and polygons as translucent fills. The map auto-frames all features.
Click any feature — a popup shows its properties, and features with a name or title property get a hover tooltip.
Pick a basemap — "Offline (no basemap)" keeps the file fully self-contained; OSM street tiles or satellite imagery are available for online viewing.
Download single HTML — one .html file containing everything. Double-click it, email it, or serve it from any static host.

Features

All core geometry types — Point, MultiPoint, LineString, MultiLineString, Polygon, and MultiPolygon render correctly, nested coordinates and all.
Color-coded by geometry family — points are blue, lines are green, polygons are red with 25% translucency, so mixed files are instantly readable.
Auto-fit view — the map jumps straight to a bounding box around your features; no manual hunting for the data.
Properties in popups — click any feature to inspect up to 12 of its properties, with tooltips on named features.
Zero dependencies in the export — Leaflet JavaScript, CSS, and your features are inlined. No CDN, no fonts, no tracking, no expiry.
Works offline — the "no basemap" mode draws on a clean light canvas. Your geometry always renders, with or without internet.
Free, no account — unlimited preview, exports the first 1,000 features, and no data ever leaves your browser.

FAQ

My coordinates look wrong — flipped or mirrored. What happened?

GeoJSON uses [longitude, latitude] order, while most desktop GIS and databases show latitude first. A point at [-122.41, 37.77] is San Francisco; the same numbers written as [37.77, -122.41] point somewhere in the middle of the ocean. Check your source export — QGIS, ogr2ogr, and Turf.js all write correct GeoJSON.

Can it handle MultiPolygon and nested coordinates?

Yes. MultiPolygon coordinates are arrays of ring arrays, and Leaflet handles the nesting natively. Something like a state with island polygons renders every ring correctly in one layer.

Do I need to specify a coordinate reference system (CRS)?

No — GeoJSON is always WGS84 (EPSG:4326) with unprojected longitude/latitude. If your data is in UTM or State Plane, convert it to WGS84 before uploading. ogr2ogr — or the "Export" → "Save As…" dialog in QGIS — converts projections easily.

What happens to my feature properties?

They are fully preserved and inlined in the exported file. Clicking a feature shows up to 12 of them in a popup (name and title get special treatment as labels). Nothing gets stripped, aggregated, or transferred anywhere.

How large can my GeoJSON be?

Preview everything your browser can handle. The free export includes the first 1,000 features; the file stays a single HTML, so even large exports just make a bigger file — no size cap server-side.

I have WKT or shapefiles — can you help?

This tool takes GeoJSON specifically. Convert WKT with ogr2ogr -f GeoJSON (or the geojson.io-style editors), and shapefiles become GeoJSON with a one-line ogr2ogr -f GeoJSON output.geojson input.shp command.