Tablizer

Convert CSV to SQL Online

Turn a CSV into INSERT statements, with a CREATE TABLE if you want the schema too. Column types are inferred from the values.

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

CSV is a text file where each line is a row and commas separate the fields. There is no type system, no formatting and no second sheet. Every value is text until something downstream decides otherwise.

Almost every database, analytics tool and spreadsheet can read and write it, which is why exports default to it.

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

Reading CSV means deciding three things the file does not state: which character separates fields, how quotes work, and what encoding the bytes are in. Tablizer sniffs the delimiter from the first few lines, handles quoted fields containing commas and newlines, and reads the file as UTF-8.

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.

Single quotes in your data are doubled, which is how SQL escapes them. A value like O'Brien becomes 'O''Brien' and runs correctly.

Statements are written in batches rather than as one enormous INSERT. A single statement holding fifty thousand tuples is legal and many clients refuse it, so the default batch is a hundred rows.

Column types are widened as the data demands. A column starts as INT, falls back to DECIMAL when it meets a value with a decimal point, and falls back to VARCHAR when it meets anything else. The VARCHAR length is rounded up from the longest value present.

What carries over from CSV to SQL

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

SQL wants a type for each column, and CSV does not record one, so each column is typed from what its values look like. A column of digits that should stay text - a zip code, a phone number, a leading-zero id - is the usual thing to check afterwards.

SQL marks its header cells differently from its data cells, so the first row is written with that marker.

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.

CSV in
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
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 CSV to SQL?

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

Why does my CSV open with all the data in one column?

The file uses a delimiter your spreadsheet did not expect. Exports from European locales often use semicolons because the comma is the decimal separator there. Change the delimiter in the export options and the columns split correctly.

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 the generated SQL safe against injection?

Quotes are escaped, so the statements are syntactically correct and will run. They are not parameterised. That is fine for a one-off import you are running yourself, and it is not a pattern to copy into application code that handles 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