LOCAL DATABASE CONVERTER / CSV TO SQL INSERT

CSV to SQL INSERT

Generate reviewable batched SQL INSERT statements from a rectangular CSV table without connecting to or modifying any database.

Processed in this browserOne UTF-8 .csv file up to 5 MB, 50,000 data rows, 200 columns, 1,000,000 cells, statement batches from 1 to 1,000 rows, and 20 MB output.

Step 1 / source

Choose the source

CSV - SQL script only

Drop one file here

Choose the header-based csv table you want to turn into escaped sql insert script.

Browse filesChecking publication status...

Step 2 / choices

Define the SQL script contract

Confirm the separator, destination table, SQL dialect, empty-cell rule, and rows per statement.

Column separatorChoose the character that separates cells in the source file.Destination tableEnter one safe table identifier or a schema-qualified name such as public.customers.SQL dialectChoose identifier quoting and boolean literals for the database that will review the script.Empty CSV cellsChoose whether empty cells become SQL NULL or an empty string literal.Rows per INSERTSplit the output into statements containing from 1 to 1,000 rows each.

Step 3 / convertCreates a separately named result and never writes into the source file.

After success, the selected source is cleared from this workspace.

No file upload

This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.

Original stays unchanged

The converter creates a separately named output. It never writes back into the source file.

Bounded work

One UTF-8 .csv file up to 5 MB, 50,000 data rows, 200 columns, 1,000,000 cells, statement batches from 1 to 1,000 rows, and 20 MB output.

Plain-language method

How CSV to SQL INSERT works

Nirmion parses one rectangular table, quotes every column identifier for the chosen dialect, escapes apostrophes and MySQL backslashes in string literals, maps empty cells by your rule, batches rows, and writes text only. It never opens a database connection.

01
Choose a valid source
Use a header row matching intended destination columns. All CSV values remain SQL strings unless an empty cell is mapped to NULL.
02
Review the conversion choices
Choose the target dialect before review. Table names must be safe identifiers or schema.table; batch size changes statement count only.
03
Inspect the separate result
The result ends in _nirmion_tools.sql and begins with a review reminder. Inspect it in version control or a database client before execution.

Useful when

Practical jobs this tool handles

Prepare a controlled seed-data script.
Review a small CSV migration with a DBA.
Create deterministic INSERT fixtures.

Before converting

Check the source and destination rules

Verify table and column names.
Review empty-string versus NULL behavior.
Run inside a test transaction before production.

Know the boundary

Know what the destination format cannot keep

Generated SQL is not a schema migration and is never automatically executed. Constraints, types, defaults, permissions, conflicts, transactions, and destination encoding remain your responsibility.

Quick answers

Questions before you convert

The conversion contract is deliberately explicit.

Does Nirmion connect to my database?

No. It only creates a downloadable SQL text file.

Are CSV numbers emitted as numeric literals?

No. CSV has no reliable types, so non-empty values are escaped strings.

Is the script safe to run immediately?

Review and test it first against the exact destination schema.