Convert SQL to AsciiDoc Online

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

AsciiDoc tables are delimited by |=== and take a cols attribute describing the columns.

Antora documentation sites, and technical writing teams that outgrew Markdown.

What changes when you convert SQL to AsciiDoc

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.

The header option is set so the first row renders as a header row rather than data.

What carries over from SQL to AsciiDoc

SQL records 2 things about a table that AsciiDoc has no way to hold.

SQL distinguishes a number from the text of a number; AsciiDoc 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 AsciiDoc, so a null and an empty string in the SQL both come out blank and can no longer be told apart.

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

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

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');

AsciiDoc out

[cols="1,1,1,1,1",options="header"]
|===
| id | name | role | started | hours
| 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
|===

Questions

How do I convert SQL to AsciiDoc?

Paste your SQL into the box above or drop the file onto it. Check the table in the grid, then copy or download the AsciiDoc 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.

Will my numbers still be numbers?

They will read the same, but AsciiDoc 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.

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.