SQLite Database Explorer
Look inside a SQLite database without setting up a server. Browse tables and views, inspect columns, run read-only SQL, and download the results.
Choose a database or try the example. Your original file is never modified.
No database open
Query workspace
Bound parameters (optional)
Use {":minimum": 10} with :minimum, or [10] with ?. Values may be strings, safe numbers, booleans or null. Missing bindings are NULL. Named keys need :, @ or $ prefixes.
One SELECT or WITH statement at a time, or EXPLAIN QUERY PLAN. SQLite query-only mode blocks writes. Shop examples use the built-in database; choose “Selected object” for your file.
Results
Results appear here.
Downloads contain only the displayed result batch. A query can return at most the selected row limit. NULL exports as an empty CSV field. Integers outside JavaScript’s safe range use a typed object in JSON; BLOBs use hex objects. CSV prefixes potentially active text and large integers to preserve them as text.
Selected cell
Click a result cell for its complete returned value.
Limits: 200 tables/views, 100 result columns, 1,000 query rows, 5 MiB returned text, 20,000 characters per text cell and 64 KiB per BLOB. Browsing uses batches of 100 with an offset up to 1,000,000. Queries have a 20-second timeout; cancellation closes the in-memory database, so reopen your file to continue. Browser memory may impose lower limits.
Only standalone SQLite databases are supported. Encrypted databases, other SQL database formats and separate WAL/SHM files are unsupported. Export a consistent standalone copy from your application first; an active database’s main file can omit recent WAL changes.
Database processing uses locally hosted sql.js in a browser worker. The original file is unchanged, and no database history is saved. Public pages include third-party advertising; read our privacy information.
Using SQLite Database Explorer
Inspect a standalone SQLite database in your browser without modifying the original file.
- Open an unencrypted SQLite database up to 25 MiB, or try the shop example. Choose a table or view to browse rows and inspect its columns.
- Run one read-only SELECT or WITH query. Add bound JSON parameters if needed, choose a result limit, or inspect the query plan.
- Download the displayed result batch as CSV or JSON. Close the database when finished. Cancelled or timed-out operations require reopening it.
Example
Load the shop database and choose Shop: orders with product names. The three order totals are 13.5, 24.9 and 12.
Choose the minimum-price example with {":minimum": 10} to find the desk lamp.Questions & answers
Will it change my database?
No. The file is loaded into browser memory, and SQLite query-only mode blocks write queries. There is no database save action. The original file is untouched.
Which SQL queries can I run?
One SELECT or WITH statement at a time, or EXPLAIN QUERY PLAN SELECT. Write statements, PRAGMA commands and multiple statements are unsupported. Bound parameters can be supplied as a JSON object or array.
What do downloads include?
Only the displayed result batch. Browsing uses batches of 100 rows; queries use your selected limit up to 1,000 rows. Results indicate when additional query rows are omitted. Use ORDER BY for a defined row order.
How are large integers, BLOBs and NULL handled?
JSON uses typed objects for integers outside JavaScript’s safe range and BLOBs with hexadecimal bytes. SQL NULL remains null in JSON and becomes an empty CSV field. CSV prefixes potentially active text and large integers to keep them as text.
Why does my database fail to open?
Use an unencrypted, standalone SQLite 3 database. Other database formats, encryption and separate WAL/SHM files are unsupported. Export a consistent standalone copy first; an active database main file can omit recent WAL changes.
What limits apply?
25 MiB per database, 200 tables/views, 100 result columns, up to 1,000 query rows and 5 MiB returned text. Text cells are limited to 20,000 characters and BLOBs to 64 KiB. Worker operations stop after 20 seconds.
Is the database uploaded or saved?
Processing runs in a local browser worker using sql.js. No database history is saved. Public advertising follows the website privacy policy. Closing the page or cancelling an operation clears the in-memory database.
Related tools
A useful next step for your task.
Developer & DataSQL Formatter WorkbenchFormat SQL across 21 dialect identifiers with reusable profiles, side-by-side editors, a change view, undo and local multi-file ZIP export.
Developer & DataJSON to SQL INSERT GeneratorTurn JSON object arrays into PostgreSQL or SQLite INSERT drafts with exact number tokens, safe literal quoting, batch sizes, missing-value…
Developer & DataCSV & TSV Table EditorRecommendedEdit CSV or TSV cells and headers locally. Add rows and columns, undo edits, filter, sort exact decimals, remove duplicates and export full or…
Developer & DataExcel Workbook ExplorerOpen XLSX, XLS, ODS and CSV spreadsheets locally. Browse sheets, search workbook values, inspect stored formulas and export matching rows as XLSX,…
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.