Guide

THE TOOLBOX / DATA & API UTILITIES

Protobuf wire decoder,
schema-less & .proto guided.

Inspect Protobuf binary wire fields without a schema, decode Base64 gRPC envelopes, or parse with a custom .proto definition locally in your browser.

Sample Payloads
Payload Size35 B
Detected InputHEX
Top-Level Fields4
Nested Fields0
Protobuf Input & ModeLive Local Decoder

Decoded 4 wire fields (35 bytes) locally.

Decoded Output
Field #Wire TypeOffsetDecoded Value / Preview
#1Varint (0)+0 (3B)150
#2Length-delimited (2)+3 (14B)
"Grace Hopper"
hex: 477261636520486f70706572
#3Length-delimited (2)+17 (16B)
hex: 6772616365406e6176792e6d696c
#4Varint (0)+33 (2B)1
sint: -1

THE DETAILS

Understanding the Protocol Buffers binary wire format.

1. Tag & Wire Type Header

Every field begins with a LEB128 varint tag. The lowest 3 bits define the wire type, and the upper bits define the 1-based field number declared in your .proto file.

2. Wire Types Reference Table

Type 0 (Varint): Variable-length 1–10 byte integers (int32, int64, uint32, bool).
Type 1 (64-bit): Fixed 8 bytes (double, fixed64, sfixed64).
Type 2 (Length-delimited): Varint byte length prefix followed by payload (string, bytes, nested messages).
Type 5 (32-bit): Fixed 4 bytes (float, fixed32, sfixed32).

3. Schema-Free Inspection

Troubleshoot gRPC streams, Kafka events, and microservice traffic when you lack the original .proto contract. Detect string fields, numbers, and nested payloads immediately.

4. Custom .proto Schema Validation

Switch to Schema Mode and supply your syntax = "proto3"; definition to map numeric field tags directly to typed JSON keys and enums.

5. Base64 & Hex Ingestion

Paste raw hexadecimal dumps, space-delimited bytes, or Base64 strings from Envoy, Wireshark, or Chrome DevTools network panels.

6. Zero Data Egress

All binary parsing, schema compilation, and JSON formatting execute locally in browser memory. No data is sent over the network.

Frequently Asked Questions

How does Protocol Buffers serialize data on the wire without field names?

Protobuf does not serialize string field names on the wire. Instead, each message field is encoded as a key-value pair where the key is a LEB128 varint computed as (field_number << 3) | wire_type. This compact encoding keeps payloads lightweight but requires knowing the wire type to correctly skip or parse fields.

What are the Protobuf wire types and how are they distinguished?

Protobuf defines six wire types: Wire 0 (Varint for int32, int64, bool, enum), Wire 1 (64-bit fixed for fixed64, sfixed64, double), Wire 2 (Length-delimited for string, bytes, embedded messages, and packed repeated fields), Wire 3 & 4 (deprecated groups), and Wire 5 (32-bit fixed for fixed32, sfixed32, float). Wire types 0, 1, 2, and 5 can be unpacked without a schema.

Can Protobuf binary payloads be decoded without the original .proto schema?

Yes, in schema-less wire mode. The parser extracts the tag, wire type, and length of every field, unpacks varints and fixed floats, and attempts UTF-8 string decoding and recursive sub-message parsing on length-delimited fields. However, exact semantic types (e.g., distinguishing signed sint32 from uint32, or a raw byte buffer from an embedded sub-message) require the .proto schema.

How does this tool handle Base64 gRPC payloads and Envoy access logs?

The tool accepts raw hex, comma-separated byte arrays, and standard Base64 encoded strings commonly emitted by gRPC-Web proxies, Envoy access logs, Kafka topics, and GCP Cloud Logging. It strips whitespace and automatically routes the binary buffer to the LEB128 wire decoder.

Are my proprietary Protobuf payloads or schemas uploaded to external servers?

No. The decoder runs 100% locally in your web browser. Schema parsing and validation use a browser-bundled protobuf.js parser with zero network egress, keeping internal microservice payloads, authentication tokens, and API schemas strictly private.