Can I decode protobuf without the .proto file?

Partially. Field numbers, wire types and values are recoverable because they are on the wire; field names and precise types are not, because protobuf never transmits them.

How do I know if a field is a nested message or a string?

Both use wire type 2, so you guess and check: try parsing the bytes as a message, and if the field numbers and lengths come out consistent it is nested; otherwise read it as a UTF-8 string.

Why does my gRPC payload fail to parse?

gRPC frames each message with a 1-byte compression flag and a 4-byte big-endian length. Strip those five bytes before decoding the protobuf body.

Protobuf Raw Decoder

Decode raw protocol-buffer wire bytes without needing the .proto schema.

on the roadmapWeb, API & Tokensfree · no sign-up

This bench is being wired up

The protobuf-decoder decoder is on the roadmap. The heavier binary and cryptographic parsers ship after the core text and token decoders — all of which are already live and working.

Browse the live decoders

Input is processed on your device. Nothing you paste is sent anywhere.

What is the Protobuf Raw Decoder?

A raw protobuf decoder parses protocol-buffer wire format directly from bytes, recovering each field's number, wire type and value even when the .proto schema that names those fields is unavailable.

Protobuf's wire format is deliberately minimal: each field is a varint key encoding a field number and a 3-bit wire type, followed by the value. Wire type 0 is a varint (ints, bools, enums), 1 is 64-bit, 2 is length-delimited (strings, bytes and nested messages), and 5 is 32-bit. Field names exist only in the .proto file — they are never transmitted.

That is why raw decoding is possible but partial. You will recover the shape of the message and its values, and length-delimited fields can often be recursively parsed as nested messages or shown as UTF-8 strings, but you have to infer meaning from context. This is the same thing protoc --decode_raw does, and it is usually enough to reverse-engineer an undocumented gRPC or mobile API.

Protobuf Raw Decoder at a glance

Wire type 0: Varint — int32/64, bool, enum
Wire type 1 / 5: Fixed 64-bit / 32-bit
Wire type 2: Length-delimited — string, bytes, nested message
Field names: Not transmitted — only field numbers are on the wire

How to use the Protobuf Raw Decoder

1Paste the raw protobuf bytes as hex or Base64 (strip any gRPC framing prefix first).
2Read the recovered field numbers, wire types and values.
3Try parsing length-delimited fields as nested messages when the bytes look structured.

When you would reach for it

Reverse-engineering an undocumented mobile or gRPC API request.
Debugging a serialization mismatch between two services.
Inspecting a stored protobuf blob when the original schema has been lost.

Protobuf Raw Decoder — frequently asked questions

Last reviewed 25 July 2026 · questions or corrections: contact@decoder.tools