Tablizer

Convert JSON Lines to LaTeX Online

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

From

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

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 LaTeX is

A LaTeX table is a tabular environment: a column specification, ampersands between cells and double backslashes at the end of each row.

Academic papers, theses and anything typeset with LaTeX or written in Overleaf.

What changes when you convert JSON Lines to LaTeX

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.

Rules are drawn with booktabs by default, which is what most journal templates expect. The characters LaTeX treats as special, & % $ # _ { }, are escaped so a value like 50% compiles instead of ending the line.

What carries over from JSON Lines to LaTeX

JSON Lines records 5 things about a table that LaTeX has no way to hold.

JSON Lines distinguishes a number from the text of a number; LaTeX does not, so every value arrives as text and has to be re-parsed by whatever reads it next.

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

JSON Lines can hold a value that is itself a list or an object. LaTeX has only flat cells, so nested values are flattened into one cell rather than being spread across columns.

LaTeX marks header cells differently from data cells, so the keys are lifted out and written once as a marked header row rather than repeated on every row.

JSON Lines can be read one record at a time. LaTeX has to be complete before it means anything, so the whole table is held in memory while it is written and a file that gets cut off part way through is not partly usable - it is unusable.

LaTeX is the end of the line for this data. Reading the table back out of it is a separate and much harder problem than writing it, so keep the JSON Lines if you will need the values again.

The identifier 007 comes out of the LaTeX as 007. Reading it as a number would have made it 7, and an id that changes value is worse than one that stays text.

The role "Analyst, data" survives with its comma, in one cell rather than split across two. That is the first thing to check in any converted table, and the usual place a LaTeX file goes wrong.

The quotes around Jonah "Jo" Pryce are left as a plain quote character in the LaTeX.

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"}
LaTeX out
  \begin{tabular}{lllll}
    \toprule
    id & name & role & started & hours \\
    \midrule
    007 & Halima Yusuf & Analyst, data & 2024-03-15 & 38.5 \\
    012 & Jonah "Jo" Pryce & Engineer & 2025-11-02 &  \\
    104 & Wei Chen & Manager & 2023-06-30 & 40 \\
    \bottomrule
  \end{tabular}

Questions

How do I convert JSON Lines to LaTeX?

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 LaTeX 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.

Why does my table not compile?

The usual cause is a missing package. Booktabs rules need \usepackage{booktabs} in the preamble. Switch the rules option off and the output uses plain \hline instead, which needs nothing.

Can I convert the LaTeX back to JSON Lines afterwards?

Not mechanically. LaTeX keeps how the table looks, not what it held, so going back means reading the values off the page again. Keep the JSON Lines if you will need it.

Will my numbers still be numbers?

They will read the same, but LaTeX stores them as text. Anything that sorts or sums the result will need to parse them first, and a leading zero or a currency symbol is the usual place that goes wrong.

What happens to nested values?

LaTeX has no nested cell, so a list or object inside a JSON Lines value is flattened into a single cell rather than expanded into extra columns. Split it before converting if the parts need to be separate.

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.

Related conversions