SQLite Viewer

What "local only" precisely means

Local-only processing. This tool runs entirely in your browser using WebAssembly. Your database files are never uploaded to any server. The file is read from disk into memory in this tab, queried there, and discarded when you close it. There is no server round trip for your data, no account and no telemetry.

What it does not mean

• The code is not local. This page and the sql.js WebAssembly binary are fetched over the network from a CDN. Your data stays put; the software operating on it arrives from a third party, and a compromised or substituted script would run with full access to whatever you opened.
• Anything in the browser can see the tab. Extensions with host access, devtools, and other pages sharing the process are inside the boundary, not outside it.
• Exports leave the boundary. A downloaded CSV or SQL file lands unencrypted in your downloads folder, and from there it is an ordinary file subject to backup, sync and search indexing.
• The browser keeps things. Query text, results and page state can survive in memory, in a session restore, in the back-forward cache, or in a crash dump, after you think you are done.
• Local is about transmission, not authorisation. It says nothing about whether you are allowed to open the file you just opened.

Data safety

No warranty for data loss. This tool is provided for convenience and inspection. Always maintain backups of important databases, and never point it at your only copy. The author accepts no liability for lost or corrupted data.

A viewer that opens a database can still leave you with a bad file: an interrupted export, a partial write, or a browser crash mid-operation. Work on a copy, always.

Not for production systems

• This viewer is intended for development, testing and analysis. It is not a replacement for proper database administration tools in production environments.
• File size limitations. Large databases, above roughly 100 MB, may cause browser crashes or instability, because the whole file is held in the tab's memory. Use DB Browser for SQLite or the sqlite3 command line for real workloads.
• Nothing here manages locking, concurrency, WAL files, journals or attached databases the way a real client does.

Never use this for

• Regulated data on a machine or browser you do not control, including protected health information under HIPAA, cardholder data under PCI DSS, and personal data under GDPR.
• Forensic examination or anything that becomes evidence. There is no write blocking, no hashing and no chain of custody, and opening a file is not a defensible acquisition.
• Recovering or repairing a corrupt database.
• Production database administration, migrations, or any change you cannot undo.
• Concluding that a database is intact, complete or uncorrupted.
• Opening a file you are not authorised to read.