Tablizer

Convert MySQL Output to JSON Online

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

JSON is a text format for nested data: objects with named keys, arrays, strings, numbers, booleans and null. It has no date type and no comments.

Every web API, most configuration files and anything that talks to JavaScript.

What changes when you convert MySQL Output to JSON

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.

You choose the shape. An array of objects is the default and the one most code expects. A 2D array is smaller. Column arrays suit charting libraries. A keyed object suits lookups by id.

What carries over from MySQL Output to JSON

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

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

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

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

The quotes around Jonah "Jo" Pryce are escaped with a backslash in the JSON.

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)
JSON out
{
  "staff": [
    {
      "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"
    }
  ]
}

Questions

How do I convert MySQL Output to JSON?

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

Why did my zip code lose its leading zero?

Type inference turned the text 07030 into the number 7030. Tablizer leaves inference off by default for exactly this reason, and refuses to convert any value starting with a zero followed by a digit even when it is on.

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