Do I need a local MySQL install?

No. You only need the .sql dump file. editsqlite parses mysqldump output directly in the browser — there is no database server to run, local or remote.

Is the dump uploaded anywhere?

No. The file is read in your browser tab and the .sqlite is written there too. This is a static site with no server, so there is nowhere to upload to; it works offline.

What parts of the dump are converted?

Table structure and data: CREATE TABLE, single and multi-row INSERT statements, backtick identifiers, doubled and backslash string escapes, and hex blob literals. Engine-specific extras like stored procedures, triggers and MySQL-only types are named and set aside rather than mistranslated.

Is the result a valid SQLite file?

Yes. It is written by our own SQLite writer and passes the official engine's PRAGMA integrity_check, so any SQLite tool can open it.

Converters · MySQL → SQLite

Convert a MySQL dump to SQLite — in your browser

You have a mysqldump file and you want a single, portable .sqlite — for a local app, a test fixture, a phone, or just to poke at the data without standing up a MySQL server. The usual route is installing MySQL, importing the dump, then running a second tool to convert. Here you skip all of it: open the .sql file in a browser tab and download a working SQLite database. The dump never leaves your device.

How to convert MySQL to SQLite

Produce the dump. If you don't have one yet: mysqldump mydb > mydb.sql. A dump of a single table works too.
Open it here. Click Open a database and pick the .sql file, or drop it onto the page. The parser reads the CREATE TABLE and INSERT statements the way mysqldump actually writes them.
Review the tables. Each table opens in the grid with its rows and columns. Edit anything, or run a SELECT to spot-check.
Export the .sqlite. Click ⬇ .sqlite (certified) and the fresh database downloads.

Convert a MySQL dump now →

What carries across — and what's set aside

Structure and data make the trip: table definitions, single and multi-row inserts, backtick-quoted names, MySQL's backslash and doubled-quote escapes, and X'...' hex blobs. What doesn't cross is named honestly rather than half-translated — stored procedures, triggers, and engine-specific types are listed as "set aside" so you always know what the SQLite copy does and doesn't contain. A conversion you can trust is one that tells you where it stopped.

Good to know

No MySQL server is involved — only the dump file. Nothing is uploaded, and it works offline once loaded.
Very large dumps are bounded by your browser's memory, since the whole database is held in the tab.
Indexes and views ride along as a one-click recreate script rather than being rebuilt into the file — safer than a half-right index.
Need the other direction, or a Postgres-flavoured dump out? Use SQLite → SQL dump after editing.

Other conversions

Postgres → SQLiteThe same trip from a pg_dump file, COPY blocks and all. SQLite → SQL dumpExport back out in SQLite, MySQL or Postgres dialect. All convertersEvery direction the tool handles.