Protobuf to CSV

Example: Protobuf input and real CSV output

The output below was generated by the same conversion code the converter uses, run on this sample when the page was built.

user {
  id: 42
  email: "dev@example.com"
  active: true
  roles: "admin"
  roles: "billing"
  profile {
    display_name: "Dev Ops"
    locale: "en-SE"
  }
}

The same data is 140 characters as minified JSON and 218 as pretty-printed JSON. Sizes are character counts, not tokens: token counts depend on the model's tokenizer (see the tokenizer comparison).

Protobuf to CSV: what changes

• Reading Protobuf: Input is Protobuf text format (the readable form used in .textproto files and debug output), not the binary wire format. Repeated fields are collected into arrays; no .proto schema is read, so types are inferred from the values.
• Writing CSV: CSV output needs a root-level array of flat objects; anything else fails with "CSV output requires an array of objects". Nested objects are not flattened, so extract or flatten them first.

Other Conversions