Converters · SQLite → SQL dump

Export a SQLite database as a SQL dump — three dialects, in your browser

A .sqlite file is perfect until you need the data somewhere else — in MySQL, in Postgres, or as a plain .sql you can read and diff. editsqlite exports a dump in whichever of the three dialects you choose, with the right quoting and escapes for that engine, all in a browser tab. Files are the interface here: no server credentials, nothing uploaded.

How to export a SQLite database as a SQL dump

1. Open the database. Click Open a database and choose your .sqlite / .db file, or drop it on the page.
2. Choose the dialect. In the export bar, pick sqlite, mysql or postgres.
3. Export the dump. Click ⬇ .sql dump. A dump written for that engine downloads — CREATE TABLE plus INSERT statements with the correct quoting.

Open a database now →

Why a dump instead of a direct connection

It's tempting to want a tool that just logs into your MySQL or Postgres and pushes the data across. A browser can't do that — it can't speak those wire protocols, and it has no business holding your database password. The honest workflow is older and safer: export a dialect dump here, then load it with the engine's own import (mysql < dump.sql, psql -f dump.sql). Your credentials never touch this page, and the file is something you can inspect before you run it.

Good to know

• String and blob escapes are written for the chosen engine — MySQL backslashes, Postgres \x hex, SQLite X'...'.
• Edit before you export: fix rows in the grid or run SQL, and the dump reflects your changes.
• Indexes and views are offered as a separate recreate script rather than being force-fit into every dialect.
• Prefer a fresh binary database instead of a text dump? Use the certified .sqlite export on the editor.

Other conversions