SQLite explorer for forensic databases
Open SQLite databases from phones, browsers and apps directly in your browser: see every table, its schema and row count, browse the rows, decode raw timestamps, run your own read-only SQL and export to CSV. The database is read into your browser's memory and never uploaded.
Open a database
Loading the explorer. If it does not appear, your browser needs JavaScript and WebAssembly (any current browser).
Quick check only, provided as is. This is not validated forensic software. Work on a copy of the evidence, verify any result you will rely on with your own validated tools, and record the method you used.
Database details
Tables and views
Table definition (schema)
Decode date columns
Choose a format for any column that holds raw timestamps. The decoded UTC date appears under each value. Confirm the format from the app's documentation: the wrong choice can still give a plausible date.
Run a query
Download for offline or air-gapped use
Prefer not to trust a website? Download the tool as a single HTML file, read the code inside it, check its hash and open it in any browser on an offline machine. The tool's code makes no network requests, and the file's own security policy blocks it from loading or sending anything.
Download sqlite-explorer-v1.0.0.html (963 KB)
SHA-256: ee8b130ae730c8641ee3aa13184d2ed0b021e5985e89ebeed0eb7f08950a4ab2
Check the hash before use: sha256sum sqlite-explorer-v1.0.0.html (Linux), shasum -a 256 sqlite-explorer-v1.0.0.html (macOS) or certutil -hashfile sqlite-explorer-v1.0.0.html SHA256 (Windows). All hashes are listed in SHA256SUMS.txt. Licence: MIT.
Where you will meet SQLite databases
- Browsers: Chrome and Edge history, downloads and cookies (dates usually in Chrome/WebKit time); Firefox places.sqlite (Unix microseconds).
- iPhone and iPad: many system and app stores, often with Apple Cocoa dates (seconds, or nanoseconds in some newer databases).
- Android: most app databases, often with Unix millisecond dates.
- Desktop apps and messaging clients on every platform.
What this tool does not do
- It does not recover deleted records. Deleted data can survive in free pages and inside live pages, so use a specialist recovery tool whenever deletion matters, even if the free page count is zero.
- It does not merge a separate
-walfile. If a database uses write-ahead logging, recent changes may be in the WAL file and will not appear here. - It does not open encrypted databases.
Good practice
- Open a copy, never the original evidence. Hash the original first; the tool shows the SHA-256 of the file it opened so you can match the two.
- The rows shown are in stored order, which is not necessarily the order events happened. Sort or filter with your own SQL.
- Whole numbers larger than 9,007,199,254,740,991 are shown and exported exactly. In CSV exports, text that a spreadsheet would treat as a formula starts with an apostrophe; numbers are never changed.
Built on sql.js 1.15.2, which compiles the public-domain SQLite library to WebAssembly. sql.js is used under the MIT licence: sql.js licence and copyright notice.
SQLite explorer: questions
Is my database uploaded?
No. The file is read into your browser's memory and opened there by a copy of SQLite compiled to WebAssembly. Nothing is sent to this site or anyone else. Browser extensions and your own device are outside our control, so follow your organisation's rules for case data.
Can it change the original file?
No. A web page cannot write back to a file you open this way, and the tool works on an in-memory copy. The query box accepts only read-only statements and keeps SQLite's query-only mode on, so your SQL is not used to change the data. Still work on a copy of the evidence, as you would with any tool.
Does it recover deleted records?
No. It shows the live records only. Deleted records can survive in free pages and inside live pages, so even a database with no free pages may still hold deleted data that a specialist recovery tool can read.
Why are some recent messages or visits missing?
If the database uses write-ahead logging, the newest changes may still be in a separate file ending in -wal, which this tool does not merge. The details panel says when a database is in WAL mode.
How large a database can it open?
The whole file is loaded into memory, so it suits typical app databases up to a few hundred megabytes. It warns above 500 MB and refuses files over 1.5 GB.
Can I rely on this for a report or court?
Treat it as a quick check, not validated forensic software. Verify important results with your own validated tools and record the method you used. Nothing here is legal advice.