# Protobuf wire decoder — no upload

> Decode raw Protobuf wire-format bytes into fields and types without a schema, in your browser. Nothing is uploaded — the payload stays in the tab.

Decode raw Protocol Buffers wire-format bytes into field numbers, wire types, and values — even without the .proto schema. Decoding happens in the browser, so nothing is uploaded.

When debugging a gRPC or protobuf service, you often have raw bytes but not an easy way to read them. Decoding the wire format reveals the field numbers, types, and values so you can reason about the message even without the schema.

For Base64 input use the Base64 tool first if needed; for captured traffic, the PCAP viewer.

## How to

1. **Paste bytes.** Provide the protobuf payload as hex or Base64.
2. **Decode.** See field numbers, wire types, and decoded values.
3. **Interpret.** Map fields to your schema to understand the message.

## FAQ

### Can it decode without a .proto file?

Yes. The wire format encodes field numbers and types, so the decoder can show the structure and values even without the schema — you map field numbers to names yourself.

### What input formats are accepted?

Hex or Base64 representations of the raw bytes, which is how protobuf payloads usually appear in logs and captures.

### Is the payload uploaded?

No. Decoding runs in the browser, so the message bytes stay in the tab.


## Related tools

- [Base64](https://www.safepaper.app/dev/base64)
- [Hex / ASCII / binary](https://www.safepaper.app/dev/hex-ascii)
- [PCAP viewer](https://www.safepaper.app/dev/pcap-viewer)
- [SQLite browser](https://www.safepaper.app/dev/sqlite-browser)

---

Canonical HTML: https://www.safepaper.app/dev/protobuf-decoder
Markdown: https://www.safepaper.app/dev/protobuf-decoder.md

There is no upload endpoint — your files are processed in this browser tab. Open your network tab and check.