Tablizer

Convert SQL to LaTeX Online

Paste a SQL 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 SQL is

SQL here means the statements that move a table into a database: INSERT INTO with a VALUES list, and optionally the CREATE TABLE that defines the columns.

Anyone seeding a database, moving a spreadsheet into an application, or writing a migration.

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 SQL to LaTeX

Column names come from the INSERT column list, or from a CREATE TABLE if one is present. Quoted strings are unquoted, doubled quotes are collapsed, and NULL becomes an empty cell.

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 SQL to LaTeX

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

SQL 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 SQL both come out blank and can no longer be told apart.

A line break inside a cell ends the row in LaTeX, so line breaks are replaced rather than carried through.

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

SQL in
INSERT INTO `staff` (`id`, `name`, `role`, `started`, `hours`) VALUES
  ('007', 'Halima Yusuf', 'Analyst, data', '2024-03-15', '38.5'),
  ('012', 'Jonah "Jo" Pryce', 'Engineer', '2025-11-02', NULL),
  ('104', 'Wei Chen', 'Manager', '2023-06-30', '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 SQL to LaTeX?

Paste your SQL 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.

Are the generated INSERT statements safe to run?

Quotes in your data are escaped, so the statements are syntactically correct. They are not parameterised, which is fine for a one-off import you are running yourself and not fine as a pattern for application code that takes user input.

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

One of my cells has a line break in it - what happens?

A line break would end the row in LaTeX, so it is replaced instead of carried through. The rest of the cell stays where it belongs.

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