Docs Self-Managed Reference Redpanda Console Record Deserialization This is documentation for Self-Managed v23.2, which is no longer supported. To view the latest available version of the docs, see v24.2. Record Deserialization When consuming messages, Redpanda Console’s message viewer is capable of automatically deserializing messages. It identifies the correct deserialization type by trying to decode the record’s key, value, or header with all available deserialization methods. The supported deserialization methods are: Kafka’s internal binary formats (for example the __consumer_offsets topic ) JSON JSON Schema with schema registry encoding XML Avro with schema registry encoding Protobuf Protobuf with schema registry encoding Messagepack (only for topics that are explicitly enabled to test MessagePack) UTF-8 / Strings Decoded messages will be rendered as JSON objects and can also be used as JavaScript object in push filters. If none of these deserialization attempts appear to be successful, Redpanda Console will render the byte array in a hex viewer. Encoding formats that are not self-contained requires additional configuration. For additional details, see: Protobuf Schema Registry for JSON Schema & Avro deserialization Back to top × Simple online edits For simple changes, such as fixing a typo, you can edit the content directly on GitHub. Edit on GitHub Or, open an issue to let us know about something that you want us to change. Open an issue Contribution guide For extensive content updates, or if you prefer to work locally, read our contribution guide . Was this helpful? thumb_up thumb_down group Ask in the community mail Share your feedback group_add Make a contribution Redpanda Console Role-Binding Configuration Programmable Push Filters