Decode protobuf wire format hex bytes into readable field structure. Shows field numbers, wire types, varints, strings, nested messages, and raw hex. Everything runs locally in your browser — nothing is uploaded.
Encode special HTML characters into entities (& < >) or decode them back to readable text.
Encodes text or small files into Base64 strings and decodes them back with automatic MIME-type detection for binary safety. Everything runs locally in your browser — nothing is uploaded.
Encode text to Base32 or decode Base32 strings back to text.
Convert between plain text and binary in both directions — encode text into its base-2 representation or decode binary strings back to readable text, byte by byte. Everything runs locally in your browser — nothing is uploaded.
Clean up and restructure raw video transcription logs into readable scripts, articles, or outlines using AI. Paste a messy transcript dump and pick a target format.
Protocol Buffers (protobuf) serializes structured data into binary. Each field is encoded as a tag (field number + wire type) followed by the value. Wire types: 0=varint, 1=64-bit, 2=length-delimited (strings, nested messages), 5=32-bit.
Capture network traffic with browser DevTools or Wireshark, then copy the hex bytes from the request/response body. gRPC and HTTP/2 APIs commonly use protobuf encoding.
Field number 1 contains a length-delimited string value 'bob'. The tag byte encodes both the field number (1) and wire type (2 = length-delimited).
Yes. Length-delimited fields that contain valid protobuf structure are recursively decoded, showing nested fields indented under their parent.
No. This decodes the raw wire format without a schema. Field names are shown as numbers — to get meaningful names, you'd need the .proto definition.