Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenPaste binary payload bytes as hex or Base64 and see the structure inside as JSON.
Copy payloads from DevTools, Kafka, Redis, or gRPC logs.
Protobuf (schemaless), MessagePack, CBOR, or Avro schema check.
Field numbers, nested messages, and JSON views stay on-device.
Copy or download decoded output for tickets and debugging.
A Kafka consumer is choking on one message, and all you have is a hex dump from the logs. You suspect a missing field or a producer that changed a type. Wire Format Studio decodes the bytes so you can see the fields without setting up a client or compiling .proto files.
Choose a format, paste the bytes and click Decode. Input is read as hex when it contains only hex digits and whitespace with an even length, otherwise as Base64. Protobuf is decoded without a schema: you get field numbers, wire types and values, length-delimited fields are shown as text when printable and also tried as nested messages, and fixed64 and fixed32 fields appear as floating-point values. MessagePack and CBOR decode straight to JSON. The Avro option works differently: paste an Avro record schema in the schema box and a JSON record in the input, and the tool reports each field that does not match.
The decoders cover common data rather than every corner of each spec. Large Protobuf varints (above 2^31) are not decoded reliably, MessagePack binary, extension and several signed integer types are rejected, and CBOR tags and indefinite-length items are unsupported. Field names never appear for Protobuf, since they live in the .proto file. To check what the bytes are before choosing a format, view the Base64 as hex, and once you have JSON, the JSON viewer makes nested data easier to browse.
Decoding is plain JavaScript in this tab, so payloads from internal services are not sent anywhere. The Receipt button records what was processed, as explained in how privacy receipts work.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
The wire format only carries field numbers and types. Names are defined in the .proto file, which this tool does not load, so match the numbers against your schema by hand.
Both are guesses. Wire type 2 is used for strings, bytes and embedded messages alike, so the decoder tries each reading. If the string is readable text, it is probably a string; otherwise trust the nested fields.
Hex detection needs an even number of hex digits and nothing else apart from whitespace. A 0x prefix, colons or an odd digit count makes the input fall back to Base64. Remove separators and check the length.