Tablizer

Convert MySQL Output to SQL Online

Paste a MySQL Output table below, edit it if you need to, and get SQL 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 MySQL Output is

Not a file format at all. It is what the MySQL command line prints when you run a query: a box drawn with plus signs, dashes and pipes, with a line underneath saying how many rows were in the set.

Anyone who has run a query in a terminal and wants the answer in a spreadsheet.

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 changes when you convert MySQL Output to SQL

The rules and the trailing row count are dropped and the pipes become column boundaries. MySQL prints an unset value as the four characters NULL, which arrives here as an empty cell, because that is what NULL means and because a literal string of NULL in a spreadsheet is worse than a blank. Paste it as CSV instead and every row becomes one column full of pipes, which is why this is its own format.

String values are escaped by doubling any single quote. Statements are written in batches so a large table does not become one statement megabytes long, which many clients refuse. Ask for CREATE TABLE as well and column types are inferred: a column stays INT until a value does not fit, then widens to DECIMAL, then to VARCHAR.

What carries over from MySQL Output to SQL

SQL can express everything MySQL holds about a table, so this conversion is about shape rather than loss.

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

The identifier 007 comes out of the SQL 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 SQL file goes wrong.

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

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.

MySQL Output in
+-----+------------------+---------------+------------+-------+
| id  | name             | role          | started    | hours |
+-----+------------------+---------------+------------+-------+
| 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    |
+-----+------------------+---------------+------------+-------+
3 rows in set (0.00 sec)
SQL out
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');

Questions

How do I convert MySQL Output to SQL?

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

Can I paste output from psql or sqlite3 as well?

psql draws its box with different characters and is not read here. Both psql and the MySQL client can print tab-separated output instead, which is detected as TSV and is the more reliable route for either: mysql -B, or \pset format unaligned and \pset fieldsep in psql.

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.

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