Convert JSON Lines to Protobuf Schema Online

Paste a JSON Lines table below, edit it if you need to, and get Protobuf Schema back. The conversion runs in your browser, so nothing is uploaded, there is no size limit and there is no signup.

From

From a page

The only part of this site that uses a server. The address is sent to it so the page can be fetched, because a browser is not allowed to fetch someone else's page itself. Your own files are never involved.

Nothing here is uploaded. The parsing happens on this page.

Edit

Paste or upload something above and it will appear here.

ToDataMarkupDocumentsCodeSchemasImages

Header rowDetect numbers

The output will appear here once there is a table to convert.

What JSON Lines is

JSON Lines is one complete JSON object per line, with no enclosing array and no commas between records. The file is not valid JSON as a whole, and that is the point.

Log pipelines, machine learning datasets and anything that appends records or reads them in a stream.

What Protobuf Schema is

A proto3 message definition with numbered fields.

gRPC services and anything using Protocol Buffers.

What changes when you convert JSON Lines to Protobuf Schema

Each line is parsed on its own, so a corrupt record does not take the file with it. Keys are unioned across lines in first-seen order, so a record missing a field leaves that cell empty rather than shifting the columns.

Field numbers are assigned in column order starting at one. Types are inferred from the values.

What carries over from JSON Lines to Protobuf Schema

One property of the JSON Lines has no home in Protocol Buffers, and it is worth knowing which before you convert.

An empty cell and a missing one are the same thing in Protocol Buffers, so a null and an empty string in the JSON Lines both come out blank and can no longer be told apart.

Both formats record types, so numbers, booleans and nulls survive as themselves rather than as text.

A worked example

Three rows of staff data, with an identifier that has a leading zero, a value containing a comma, a value containing quotes and one blank cell. Those are the four places formats disagree, so they are the four places to look.

JSON Lines in

{"id":"007","name":"Halima Yusuf","role":"Analyst, data","started":"2024-03-15","hours":"38.5"}
{"id":"012","name":"Jonah \"Jo\" Pryce","role":"Engineer","started":"2025-11-02","hours":""}
{"id":"104","name":"Wei Chen","role":"Manager","started":"2023-06-30","hours":"40"}

Protobuf Schema out

syntax = "proto3";

message staff {
  int64 id = 1;
  string name = 2;
  string role = 3;
  string started = 4;
  double hours = 5;
}

Questions

How do I convert JSON Lines to Protobuf Schema?

Paste your JSON Lines into the box above or drop the file onto it. Check the table in the grid, then copy or download the Protobuf Schema from the output panel. It takes one step and the data never leaves your browser.

What is the difference between JSON and JSON Lines?

JSON wraps records in an array, so a reader must load the whole document before it can use any of it, and appending means rewriting the file. JSON Lines has no wrapper, so records can be streamed and appended one at a time. Use JSON for a payload, JSON Lines for a log.

Is there a limit on file size?

No. The work happens on your own machine, so the limit is your machine's memory rather than an upload cap. A file with tens of thousands of rows converts in a second or two.

Is my data uploaded anywhere?

No. The parsing and generating are done by JavaScript running on this page. You can watch the network tab while you convert and see that nothing is sent.