What CSV is
CSV is a text file where each line is a row and commas separate the fields. There is no type system, no formatting and no second sheet. Every value is text until something downstream decides otherwise.
Almost every database, analytics tool and spreadsheet can read and write it, which is why exports default to it.
What Protobuf Schema is
A proto3 message definition with numbered fields.
gRPC services and anything using Protocol Buffers.
What changes when you convert CSV to Protobuf Schema
Reading CSV means deciding three things the file does not state: which character separates fields, how quotes work, and what encoding the bytes are in. Tablizer sniffs the delimiter from the first few lines, handles quoted fields containing commas and newlines, and reads the file as UTF-8.
Field numbers are assigned in column order starting at one. Types are inferred from the values.
What carries over from CSV to Protobuf Schema
One property of the CSV has no home in Protocol Buffers, and it is worth knowing which before you convert.
Protocol Buffers wants a type for each column, and CSV does not record one, so each column is typed from what its values look like. A column of digits that should stay text - a zip code, a phone number, a leading-zero id - is the usual thing to check afterwards.
Protocol Buffers has no header row. The column names are repeated as keys on every record instead, which is why the result is bigger on disk than the table it came from.