Convert Apache Avro files (.avro) to readable JSON locally - the embedded schema is read along, no upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
Apache Avro is a compact binary data format from the big-data world (Kafka, Hadoop, data pipelines). An .avro Object Container File (OCF) bundles the records together with their schema (as JSON) in the file header - so it is fully self-describing. The binary form is space-saving but unreadable in a text editor. This tool reads the container along with its embedded schema and turns every record into clear, readable JSON.
Everything runs entirely locally in your browser (pure JavaScript, no upload, even offline, no third-party library). The tool reads the OCF header, evaluates the embedded Avro schema and decodes each record against it - records, arrays, maps, unions, enums and primitives. The null and deflate block codecs are supported (deflate via the bundled fflate); the rarer snappy codec is rejected honestly. Bytes and fixed fields become base64, and 64-bit integers beyond the safe JavaScript range are emitted as strings so no precision is lost.
You will meet this when a data pipeline, a Kafka topic export or an analytics job produced an .avro file and you want to view it, feed it into a tool that speaks JSON, or simply read it. JSON is universal and human-readable. Note: this is a one-way view (Avro to JSON); it does not serialize back to Avro, and logical types (date, timestamp, decimal) appear as their underlying base value.
| Input formats | AVRO |
|---|---|
| Output format | JSON |
| Batch processing | Yes |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Avro Object Container Files with codec null or deflate are supported; the snappy codec is rejected with a clear error. Bytes/fixed are shown as base64, large 64-bit integers as strings (precision), unions as the respective branch value, logical types as their base value. The conversion is one-way (no JSON back to Avro). The schema is read from the file header; bare single Avro records without an OCF container are not supported.
A compact, self-describing binary data format from the big-data world (Kafka, Hadoop). The schema travels in the file header.
No. The conversion happens entirely locally in the browser - even offline.
The null and deflate block codecs. The rarer snappy codec is rejected with a clear message rather than mis-decoded.
64-bit integers beyond the safe JS range are output as strings; bytes and fixed fields as base64.
No, this tool is one-way (Avro to JSON) - for inspecting and reusing the data.