TrueTool
GeoJSON to Geobuf Converter
Convert GeoJSON to Geobuf and back in your browser. Compare actual file sizes, inspect conversion results, preview the geometry on a map, and download your data without uploading files. Both directions use the official Mapbox Geobuf implementation, so the binary files work with any compatible Geobuf reader.
Conversion result
| Format | Size | Notes | Download |
|---|
Byte counts come from this conversion. Size change varies by dataset — GeoJSON with many repeated attribute names usually shrinks more than coordinate-heavy data. The gzip rows are compressed copies for comparison; Geobuf itself is not gzip-compressed.
About the .pbf name: the official Geobuf CLI and many community tools write Geobuf data to files named .pbf. It is just a filename convention — the bytes are still Geobuf, not Mapbox Vector Tiles (MVT). Both names are offered below; they are identical files.
Conversion checks
Map preview
Preview only. Basemap tiles come from OpenStreetMap when enabled — your data is never sent. For a standalone map file, use Geobuf to HTML Map or GeoJSON to HTML Map.
Decoded GeoJSON preview
Does Geobuf Reduce GeoJSON File Size?
The size table above reports actual byte counts for your own data. Geobuf usually produces a smaller file than raw GeoJSON because it stores coordinates as integers and moves repeated property keys into a shared dictionary — but the result depends on the dataset, and this tool shows the real numbers instead of a fixed claim.
For context, the table also shows the same data after gzip compression. Geobuf and gzip are different techniques: Geobuf is a binary encoding, while gzip is a general-purpose compression step that can be applied on top of either format. Don't read the gzip numbers as a Geobuf "compression ratio" — they simply tell you how each format behaves when compressed.
How to Convert GeoJSON to Geobuf
- Add your GeoJSON. Drop a file onto the upload area, choose one from disk, or paste the JSON text.
- Check the input summary. The converter validates the GeoJSON structure and reports the object type, feature count, and geometry types before encoding.
- Convert. Click "Convert to Geobuf". The file is encoded locally with the official Geobuf encoder, then decoded again to verify the output.
- Review the real size change. You get the exact GeoJSON and Geobuf byte counts, the difference in bytes and percent, a gzip comparison, and a map preview of the geometry.
- Download what you need. The .geobuf file is the primary output; the size table also offers the original GeoJSON and both gzip variants as real files.
How to Convert Geobuf to GeoJSON
- Switch the direction to "Geobuf → GeoJSON".
- Choose a Geobuf file (.geobuf, .pbf, or .bin). The tool checks the decoded result — a file with a .pbf extension is not automatically treated as Geobuf, because that extension is also used by Mapbox Vector Tiles and other formats.
- Decode. The file is decoded locally and validated as GeoJSON.
- Copy or download. Copy the JSON to the clipboard or download it as a .geojson file.
What Is Geobuf?
Geobuf is a compact binary encoding for geographic data, built on Protocol Buffers and maintained by Mapbox. It encodes GeoJSON-style objects (FeatureCollections, Features, and geometries) into binary data that a compatible Geobuf reader can decode back into GeoJSON.
Geobuf aims for nearly lossless compression rather than tiling or projection. The official implementation stores coordinates with up to 6 decimal places (about 10 cm at the equator), so coordinates with more precision are rounded. Feature properties, feature IDs, and custom members are preserved by the encoder.
Geobuf is not Mapbox Vector Tiles (MVT). Both are binary formats and both may use a .pbf extension, but they are different specifications. A Geobuf decoder cannot read MVT, and this tool reports an error instead of guessing.
Geobuf vs GeoJSON
| Aspect | GeoJSON | Geobuf |
|---|---|---|
| Encoding | Human-readable JSON text | Protocol Buffers binary |
| Editing by hand | Easy — any text editor | Needs a Geobuf encoder/decoder |
| Coordinates | Full JSON number precision | Up to 6 decimal places (official encoder) |
| File size | Often larger | Often smaller — the exact result depends on the data |
| Tool support | Universal in GIS software | Requires a compatible implementation |
For display and interchange GeoJSON remains the safest choice; Geobuf is useful when you need a more compact binary representation and control both ends of the pipeline. This tool lets you test the actual size difference on your own data before switching formats.
FAQ
How do I convert GeoJSON to Geobuf?
Paste GeoJSON or load a file in the converter above, click "Convert to Geobuf", and download the generated .geobuf file. The conversion and validation run entirely in your browser.
How do I convert Geobuf to GeoJSON?
Switch the direction to "Geobuf → GeoJSON", choose your .geobuf file, and click "Convert to GeoJSON". You can copy the decoded JSON or download it as a .geojson file. Files that are not valid Geobuf are rejected rather than guessed at.
What is the Geobuf format?
Geobuf is a compact binary encoding for geographic data built on Protocol Buffers, maintained by Mapbox. It encodes GeoJSON-style objects into binary data that a compatible decoder can read back into GeoJSON. It is not a text format and cannot be inspected in a text editor.
Is Geobuf smaller than GeoJSON?
Often, but not always. The official Geobuf README reports typical reductions of roughly 6–8× on large datasets, while small files or coordinate-heavy data can shrink less. This tool measures the actual byte counts for your input, including whether the Geobuf file comes out larger.
Is Geobuf lossless?
Nearly. Properties, feature IDs, and custom members are preserved, but coordinates are encoded with up to 6 decimal places, so digits beyond that are rounded (about 10 cm at the equator). The converter's round-trip check reports the maximum coordinate difference and flags any feature, property, or geometry mismatch it detects.
Is Geobuf the same as Mapbox Vector Tiles?
No. Geobuf is a near-lossless encoding of GeoJSON-style data. Mapbox Vector Tiles (MVT) are a tiled, projected, display-oriented format that strips properties and simplifies geometry. Both can use a .pbf extension, so the extension alone tells you nothing — this tool only accepts files that actually decode as Geobuf.
The official Geobuf CLI also writes Geobuf data to files named .pbf, so a .pbf filename is normal for Geobuf too. It is a naming convention, not a format marker; this page offers both .geobuf and .pbf names for the same bytes.
Can I convert GeoJSON to Geobuf online?
Yes — this page runs the official Geobuf implementation entirely in your browser. No files are uploaded, and no account is required.
Are my GeoJSON files uploaded to a server?
No. File reading, encoding, decoding, size calculation, and downloads all happen locally in your browser. Your data is not sent to TrueTool or any third party.