How large can each database be?

Each side is capped at 50 MB to keep memory usage safe in the browser. For larger files, dump and re-import only the tables you need to compare.

Does the SQLite Diff require a signup?

No. It is available with no signup and no usage limits. Both databases are opened in your browser with WebAssembly, and nothing is uploaded.

What file types can I open?

SQLite database files, whatever their extension: .sqlite, .sqlite3, .db or none. Drop one file into each side; the tool opens both with the SQLite WebAssembly engine and reads the schema and the rows.

How are row differences matched?

By primary key. A table with a primary key gets row-level results: added, removed, and changed rows with the changed columns named. A table without a primary key is compared at the schema level only.

Can I export the diff?

The results are shown on the page for review. Copy the table you need from the view; there is no export file at the moment.

SQLite Diff — Compare Two.db Files Side-by-Side

Developers · SQL & Databases SQLite Diff

100% local — both databases stay in your browser

Both files are loaded as in-memory SQLite instances via the official @sqlite.org/sqlite-wasm. Nothing is uploaded.

Left (before)

Right (after)

Drop a SQLite file on each side, then click Compute diff.

SQLite Diff

Drop two SQLite databases side-by-side and see exactly what changed — added or removed tables, column changes, and row-level diffs by primary key. 100% in-browser, no upload.

Are my databases uploaded?

No. Both files load as in-memory SQLite instances inside your browser tab via WebAssembly. Open your DevTools Network panel during a diff — you'll see no outbound requests carrying your data.

What kinds of differences does it detect?

Schema changes (tables added, removed, renamed; columns added, removed, type-changed) and row-level differences for any table that exists in both databases and has a primary key.

Why does it need primary keys for row diffs?

Row matching is PK-based. Without a PK we can't tell whether two near-identical rows are 'the same row, modified' or 'one deleted + one inserted'. Tables without a PK get schema-only diffs and a total row count delta.

About this tool

This tool runs two SQLite engines entirely inside your browser via WebAssembly. Drop a 'before' and an 'after'.db file (or any pair of SQLite-format files — Chrome History, iOS backups, app caches) and see a precise tree of what changed.

Schema diff shows tables that were added or removed, plus column-level details for tables that appear on both sides. Row diff matches rows by primary key and surfaces inserts, deletes, and column-level updates. Both diffs survive 50 MB-class files smoothly.

The most common use case is verifying a database migration: load before.db and after.db, see what the migration actually did, paste the diff into the PR description.

How it compares

Unlike server-backed diff tools, this one processes both databases locally via WebAssembly — no upload, no privacy leak. The engine is the official SQLite team's build, so feature parity with the desktop SQLite CLI is full.