Protobuf wire inspector
Read field numbers and wire types from hexadecimal bytes. Inspect boundaries without a schema; nested messages and field names are not inferred.
The example value has been entered. Check it immediately or change the value.
Input is processed in the browser. Refreshing returns a sample value.
Instructions and example
Decode the key into wire type and field number, then use a varint or length to locate the next field boundary.
08 96 01 is field 1 varint 150; 12 03 61 62 63 is field 2 with 3 payload bytes.
Wire types 0,1,2,5; at most 200 fields and 10,000 bytes. Groups are rejected; signed, ZigZag, float and string interpretations are not inferred.
Frequently asked questions
Why are length-delimited Protobuf values not decoded as strings?
The same wire type can hold strings, bytes or nested messages; a schema is needed to distinguish them.
What happens when Protobuf input is truncated?
An unfinished varint or out-of-bounds payload rejects the complete input.
Calculation criteria and reference materials
- Protocol Buffers — Encoding
Decode the key into wire type and field number, then use a varint or length to locate the next field boundary.
Verification of calculation criteria: · Calculation·verification principles · Report errors