SQLite Snapshot Schema Inspector

How to use SQLite Snapshot Schema Inspector

Read schema objects and selected file-header metadata from a bounded standalone SQLite rollback-journal snapshot without executing SQL. Recover stored CREATE statements, object names and root-page metadata by parsing the sqlite_schema b-tree directly. Keep this source inventory separate from querying table data or repairing a database.

1. Provide standalone sqlite rollback-journal snapshot.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• 8 MiB complete main database file, standard pages 512–65,536 bytes, initialized schema formats 1–4 and UTF-8/UTF-16LE/UTF-16BE. Requires read/write format 1 and zero extension-reserved page bytes. WAL mode, encryption and journals are refused or unhandled; export a consistent standalone snapshot first.
• Reads only the schema table rooted at page 1. At most 1,000 schema rows and 1,024 combined b-tree/overflow pages; 128 KiB per schema payload and 256 KiB total source payload. Page pointers, overflow length and visited cell ranges are bounded before copying.
• The main file cannot prove that a separate hot journal exists or that this snapshot is current. Do not copy a live database file without its application’s safe backup/export procedure.
• Schema SQL, including virtual-table and trigger definitions, is returned as inert text and never parsed for execution. Table data, index contents, free lists, full b-tree ordering and database integrity are not validated.
• Reports can reach a separate 500,000-character output cap; reduce a very verbose schema if needed. Reading metadata neither repairs the original database nor proves it can be opened by a particular SQLite application.
• Inputs are processed on this device and are not automatically saved or uploaded.