Compare SQLite schemas
Open your first database, choose Compare schemas in the explorer, then select a second file. Read added, removed and changed definitions side by side in expandable sections.
Open the first databaseBefore and after, with your files kept local
- The open workspace is Before. The selected file is After.
- Review table, view, explicit index and trigger changes.
- Download a JSON comparison to keep with your migration notes.
The second database is inspected in temporary memory and then closed. It does not replace the workspace. Files must be unencrypted SQLite databases; the second file is limited to 50 MiB and combined schema text to 2 MiB.
What a difference means
This compares stored SQL definitions, including whitespace and capitalization. A formatting-only edit can appear as changed. Row data, internal SQLite objects and execution plans are not compared. A rename appears as removal and addition. No migration is generated or executed.
Use the schema designer to review deliberate schema changes, or export a SQLite dump for a portable logical snapshot.