SQLite Database Not Opening: Safe Recovery Checklist

Use file-header clues and trusted SQLite integrity checks to guide recovery.

Step-by-step troubleshooting

1. 01

   Stop writing to the database

   Back up the .db and any associated -wal and -shm files without opening them for editing.

2. 02

   Inspect the file header

   Check the SQLite format signature and page-size fields.

3. 03

   Check for a partial page

   A file size not divisible by its page size may indicate an incomplete transfer.

4. 04

   Validate on a safe copy

   Use a trusted local sqlite3 client and PRAGMA integrity_check; avoid exposing private database data.

5. 05

   Restore or use recovery tooling

   For malformed pages, use supported SQLite recovery tools on a copy or restore from backup.

What if the file is still broken?

Structural checks can identify evidence of truncation, checksum errors or a format mismatch, but a successful check does not prove every application can decode the file. If critical data is missing, restore from backup, request a new copy or use a reputable specialist with permission to access the content.

For important or sensitive files, retain a copy of the original and document each recovery attempt. Avoid tools that promise guaranteed reconstruction of missing bytes.

For a practical recovery order that minimizes accidental damage, see our safe file recovery checklist. For format-specific limits, see supported formats and test scope.