Convert CSV to PostgreSQL SQL

How to convert a CSV file to PostgreSQL

Getting a CSV into PostgreSQL usually comes down to two approaches: bulk-loading the raw file with COPY, or running a SQL script of CREATE TABLE and INSERT statements. SQLified does the second — it reads your CSV in the browser and writes a clean, ready-to-run Postgres script. No database access, drivers, or command line required to build the SQL; you just run it wherever your database lives.

1. Drop your CSV onto the converter above (or click to choose a file).
2. Review the schema. SQLified samples your data and infers a PostgreSQL type for each column. Adjust any type, mark columns nullable, rename them, or set a primary key.
3. Generate the SQL — a CREATE TABLE plus batched INSERT statements.
4. Run it in Postgres — paste it into psql, pgAdmin, DBeaver, or your Supabase / Neon / RDS console.

What the generated SQL looks like

A small CSV with id, name, signup_date, amount becomes:

CREATE TABLE IF NOT EXISTS "users" (
  "id" INTEGER NOT NULL,
  "name" TEXT NOT NULL,
  "signup_date" DATE NOT NULL,
  "amount" NUMERIC(18,2) NOT NULL
);

INSERT INTO "users" ("id", "name", "signup_date", "amount") VALUES
('1', 'Ada Lovelace', '2026-01-04', '120.50'),
('2', 'Alan Turing', '2026-02-11', '99.00');

Identifiers are double-quoted (the PostgreSQL standard), so mixed-case and reserved-word column names just work. CREATE TABLE IF NOT EXISTS means you can re-run the script safely.

PostgreSQL type inference

SQLified looks at the actual values in each column and maps them to the right Postgres type:

• Whole numbers → INTEGER, or BIGINT when they exceed the 32-bit range.
• Decimals → NUMERIC(18, n) sized to your data's precision.
• Dates and timestamps → DATE or TIMESTAMP.
• true/false → BOOLEAN.
• Everything else → TEXT.

Not happy with a guess? Override any column's type before you generate — useful for IDs you want as text, or numeric codes that shouldn't lose leading zeros.

COPY vs. INSERT — which should you use?

COPY (or \copy in psql) is the fastest way to bulk-load when you have direct file access to the database host. But on managed Postgres — Supabase, Neon, RDS — loading a local file with COPY is often clunky or blocked.

INSERT statements are portable: paste them into any SQL console and they run. That's what SQLified generates, and for very large files it splits the inserts into 1,000-row batches so they import reliably instead of failing as one oversized statement. For a few thousand to a few million rows loaded into a managed database, generated INSERTs are usually the path of least resistance.

Frequently asked questions