Do COPY blocks work, or only INSERTs?

Both. editsqlite reads Postgres COPY ... FROM stdin blocks as well as INSERT statements, handling tab-separated values, \N for NULL and the standard backslash escapes. A plain pg_dump either way converts cleanly.

Do I need PostgreSQL installed?

No. You only need the .sql dump file. The conversion runs entirely in your browser with no database server, local or remote.

No. It is read in the browser tab and the .sqlite is written there. There is no server behind this site, so nothing is uploaded and it works offline.

What about Postgres-only types and extensions?

Data and table structure convert. Postgres-specific features — stored procedures, custom types, extensions — are named and set aside rather than mistranslated, so you know exactly what the SQLite copy holds.

Converters · Postgres → SQLite

Convert a Postgres dump to SQLite — in your browser

A pg_dump file is the portable form of a PostgreSQL database, but it only speaks Postgres. To get a .sqlite out of it the usual way, you'd restore the dump into a running Postgres and then convert. editsqlite reads the dump straight — COPY blocks and all — and hands you a SQLite file, without a database server anywhere in sight and without the data leaving your machine.

How to convert Postgres to SQLite

Produce the dump. A plain-format dump works either way: pg_dump --inserts mydb > mydb.sql, or a default COPY-format dump.
Open it here. Click Open a database and choose the .sql file, or drop it on the page. The parser handles COPY ... FROM stdin data, \N nulls and Postgres escapes.
Review the tables. Each table opens in the grid; edit cells or run a SELECT to check the import.
Export the .sqlite. Click ⬇ .sqlite (certified) to download the fresh database.

Convert a Postgres dump now →

COPY blocks, handled the way pg_dump writes them

Most browser converters choke on a default pg_dump because the rows aren't INSERT statements at all — they're a COPY block of tab-separated lines terminated by a lone \.. editsqlite reads that block directly: tabs split the fields, \N becomes NULL, and \t, \n, \r and \\ are un-escaped the way Postgres wrote them. So you don't have to re-dump with --inserts just to get it to read.

Good to know

No Postgres install required — only the dump file. Nothing uploads; it works offline once loaded.
Large dumps are bounded by browser memory, since the whole database lives in the tab.
Postgres-only features are named and set aside, not mistranslated — the copy is honest about its contents.
Want to go back out to a Postgres-flavoured dump after editing? See SQLite → SQL dump.

Other conversions

MySQL → SQLiteThe same trip from a mysqldump file. CSV → SQLiteStart from a spreadsheet export instead of a dump. All convertersEvery direction the tool handles.