Connecting to OmniTools before opening this tool…
Only a temporary connection check is sent. Your files and tool inputs stay in your browser.
How SQLite Database & SQL Query Runner works
The SQLite Database Viewer loads and queries SQLite database files entirely within the browser using sql.js, a WebAssembly port of the SQLite C library. When a .db, .sqlite, or .sqlite3 file is uploaded, the FileReader API loads it into an ArrayBuffer which sql.js initializes as an in-memory SQLite virtual machine. The full SQLite query engine—including JOIN operations, subqueries, window functions, CTEs, aggregate functions, and index utilization—executes natively in WebAssembly without any server-side database infrastructure.
The interface provides dual functionality: a schema explorer that queries sqlite_master to enumerate tables, views, indexes, and triggers with their column definitions and data types; and a SQL console accepting arbitrary SELECT, INSERT, UPDATE, and DELETE statements executed against the loaded database. Query results render as interactive HTML tables with sortable columns and row counts, exportable to CSV format for downstream analysis.
Since sql.js runs the genuine SQLite engine compiled to WebAssembly, all SQL dialect features, pragma statements, and built-in functions behave identically to desktop SQLite installations. Critically, the entire database exists only in volatile browser memory—no data is uploaded to remote servers, making it suitable for inspecting sensitive production database snapshots, personal finance records, and proprietary application data stores.
How to use SQLite Database & SQL Query Runner
1. Upload SQLite Database File
Select a .db, .sqlite, or .sqlite3 file. The FileReader loads the binary into an ArrayBuffer and initializes the sql.js WebAssembly SQLite virtual machine.
2. Explore Table Schemas
Browse the sidebar listing all tables, views, and indexes. Click any table to inspect its column definitions, data types, primary keys, and row count without writing queries.
3. Execute SQL Queries
Type custom SQL statements into the query console. Execute SELECT queries with JOINs, WHERE filters, GROUP BY aggregations, ORDER BY sorting, and LIMIT pagination against your data.
4. Export Query Results
Download query result sets as CSV files for import into spreadsheet applications, data analysis notebooks, or reporting pipelines. Copy individual cell values directly to clipboard.
Key features and technical specifications
sql.js WebAssembly Engine
Authentic SQLite C library compiled to WebAssembly delivers full SQL dialect support including window functions, CTEs, JSON operators, and pragma statements natively in browser.
Schema Introspection Explorer
Automatic sqlite_master querying enumerates all tables, columns, data types, indexes, triggers, and views with organized hierarchical navigation without manual catalog queries.
Interactive SQL Console
Full query editor accepts arbitrary SQL statements with instant tabular result rendering, row count display, and execution timing feedback for performance analysis.
CSV Export Pipeline
Query result serialization to RFC-compliant CSV format enables seamless data extraction for downstream analysis in Excel, pandas, R, or business intelligence platforms.
Inspecting a database with a limited query
Start by reviewing table names and columns, then use a small SELECT result with a LIMIT when exploring unfamiliar data. Large result sets can consume browser memory. Treat modifying statements separately from read-only inspection, and keep the original database file before exporting or relying on a changed copy.
Mobile App Developers
Inspect SQLite databases extracted from iOS and Android application sandboxes during debugging, verifying local data storage schemas, cached API responses, and offline sync state.
Data Analysts
Query portable SQLite data exports from enterprise systems without installing desktop database clients, running ad-hoc analysis on distributed dataset snapshots shared as .db files.
Backend Engineers
Debug application SQLite databases during local development, verify migration scripts, inspect seed data integrity, and test complex JOIN queries before deploying to production environments.
Digital Forensics Investigators
Examine seized device database artifacts including browser history, messaging app stores, and application caches in isolated browser environments without contaminating evidence files.
Frequently asked questions
What SQLite file formats are supported?
The viewer supports standard SQLite 3 database files with extensions .db, .sqlite, .sqlite3, and any valid SQLite 3 binary format regardless of extension. Legacy SQLite 2 files are not supported as sql.js implements the SQLite 3 engine. Encrypted databases (SQLCipher) require decryption before loading since sql.js expects standard unencrypted SQLite page format.
Can I modify data in the database?
Yes. The sql.js engine supports INSERT, UPDATE, DELETE, CREATE TABLE, ALTER TABLE, and DROP TABLE statements executed through the SQL console. Modifications apply to the in-memory database instance. However, changes are volatile—they exist only in browser session memory and are lost when you close the tab or refresh the page unless you export the modified database.
How large of a database file can I load?
The practical limit depends on available browser RAM since the entire database loads into an ArrayBuffer and the sql.js virtual machine operates in memory. Databases up to 100MB load reliably on modern devices. Larger files may encounter browser heap allocation limits. For massive databases, server-side SQLite clients with disk-backed storage are more appropriate.
Does it support complex SQL features like window functions?
Yes. sql.js compiles the full SQLite C library to WebAssembly, supporting all SQLite SQL features including window functions (ROW_NUMBER, RANK, LAG, LEAD), common table expressions (WITH clauses), JSON functions (json_extract, json_each), full-text search (FTS5), and recursive queries.
Do I need an internet connection, and are my inputs uploaded?
An internet connection is required to open tools and refresh a temporary session. Processing stays on your device; the handshake sends a random challenge, not files or text inputs. Libraries, fonts or models may download. Local processing cannot remove risks from an untrusted device or extension.