Geobuf to HTML Map Converter

Turn a Geobuf file into one standalone HTML map — decode the compact binary in your browser, inspect points, lines and polygons on an interactive map, then export a single HTML file that double-clicks open and works offline. The map engine, styles and your features are inlined; nothing is uploaded. A .pbf file is only accepted if it actually decodes as Geobuf, not because of its extension.

What Is a Geobuf File?

Geobuf is a compact binary encoding for geographic data, built on Protocol Buffers and maintained by Mapbox. It stores the same information as GeoJSON — features, geometries, properties and IDs — in binary form, typically in a much smaller file. Decoding requires a Geobuf-compatible reader, which is why a plain text editor or a generic map tool cannot open it.

This page decodes Geobuf locally with the official implementation and renders the result. It is not the same thing as Mapbox Vector Tiles (MVT): both are binary and both may use a .pbf extension, but MVT is tiled, projected and stripped of most properties. If a file does not decode as Geobuf, this tool reports an error instead of guessing.

Need the reverse direction or a size comparison? Use the GeoJSON to Geobuf converter.

How to Convert Geobuf to an HTML Map

  1. Add your Geobuf file. Drop a .geobuf, .pbf or .bin file onto the upload area, or click to browse. You can also load the built-in sample to try the tool.
  2. Check the decoded summary. The tool reports how many points, lines and polygons were found. Invalid data — including files that are actually MVT — is rejected with an explanation.
  3. Inspect the map. Features are color-coded by geometry family; click one to see its properties. The map auto-frames your data.
  4. Pick a basemap. "Offline (no basemap)" keeps the exported file fully self-contained; OpenStreetMap or satellite tiles are optional for online viewing.
  5. Download the HTML map. One .html file containing the map engine, styles and your features. Open it anywhere, or host it on any static server.

What Survives the Decode?

Geobuf is designed to be nearly lossless: feature properties, feature IDs and custom members are preserved, and coordinates are stored with up to 6 decimal places (about 10 cm at the equator). Anything with more precision was already rounded when the file was encoded, so this page can only display what the file contains.

Features with a null or missing geometry are skipped for the map, because there is nothing to draw. If every feature is skipped, the tool tells you instead of showing an empty map.

FAQ

Is Geobuf the same as Mapbox Vector Tiles (MVT)?

No. Geobuf is a near-lossless binary encoding of GeoJSON-style data. MVT is a tiled, projected, display-oriented format that strips most properties and simplifies geometry. Both can use a .pbf extension, so the extension alone proves nothing — this tool only accepts files that actually decode as Geobuf.

My .pbf file is rejected. Why?

The file did not decode as Geobuf. It may be a Mapbox Vector Tile, a Protobuf file for a different schema, or corrupt. Try the original Geobuf export, or convert the source data to GeoJSON first and use the GeoJSON to Geobuf converter to produce a valid Geobuf file.

Does the exported HTML map work offline?

Yes, when you export with "Offline (no basemap)". The map engine, styles and your features are inlined, and no external requests are made. Online basemaps are optional extras for viewing the file in a browser with internet access.

Are my files uploaded to a server?

No. Decoding, validation and HTML export all run in your browser. Your file is never sent to TrueTool or any third party. The only network requests are optional basemap tiles when you select an online basemap.

Can I convert Geobuf back to GeoJSON instead?

Yes — use the GeoJSON to Geobuf converter in the "Geobuf → GeoJSON" direction. It also validates the decoded structure and reports the file-size difference.