Inspect Avro binary data

Inspect supported fields and container metadata in a base64 or hexadecimal Avro payload.

freeworks offlinenothing uploaded
ToolAvro Viewer
Input
Output
—
Put this on your own site

The frame below runs the same code as this page, in the reader's own browser. Nothing is sent to us, and nothing is sent to you.

Pick a dark background and the text and panels follow it, so the frame stays readable on a dark page.

Preview

How it works

Bytes are decoded with Avro variable-length zigzag integers, length-prefixed strings and bytes, and block counts. The report is a best-effort view of supported primitive patterns and cannot reconstruct an arbitrary writer schema.

  • Base64 is a practical transport form for binary records.
  • The summary stays bounded when schema information is absent.

Worked example

Inspect raw Avro binary bytes
View hex dump and byte length of base64-encoded binary data
Input
											AQID
Output
												Hex: 01 02 03
Byte length: 3
Is object container: no
Summary: 3 bytes of data (not an Avro Object Container File - may be raw Avro data without header)

When to use this

Kafka captures, Avro object-container files, and data-pipeline replay debugging inspect binary records.

Edge cases

  • Without the writer schema, ambiguous bytes cannot be fully typed.
  • A negative Avro block count is followed by a block-size field.
  • A truncated length-prefixed string is rejected instead of partially decoded.

References