Online Protobuf Wire Decoder (No Schema)

No. The file is read and decoded entirely in your browser using JavaScript. Nothing is uploaded, runs in your browser, so even sensitive or proprietary payloads stay on your device.

No. This decoder reads the raw wire format, which encodes a field number and a wire type for every field. It recovers the structure and values without a schema. The trade-off is that field names and exact types are not in the bytes, so it shows best-effort interpretations instead.

Without a schema some wire types are ambiguous. A length-delimited field could be a string, packed bytes, or a nested message, so the tool shows the UTF-8 text, the raw hex, and a nested-message attempt. A varint could be an int, a boolean, or a zigzag-encoded signed value, so all three readings are shown.

Protobuf uses four main wire types: 0 Varint (base-128 integers, booleans, and enums), 1 I64 (eight fixed bytes for fixed64 or double), 2 Len (a length then that many payload bytes for strings, bytes, and sub-messages), and 5 I32 (four fixed bytes for fixed32 or float).

The decoder reports an error rather than guessing. A varint that never ends, a fixed field with too few bytes, or a length-delimited field that claims more bytes than exist will all be flagged as malformed input.

ZigZag is how protobuf stores signed integers (sint32 and sint64) so that small negative numbers stay small on the wire. The tool shows the zigzag-decoded signed value next to the plain unsigned reading for every varint.