Keep the database together
Browse tables, views, indexes and triggers. Saving a database keeps its structure and data together; exporting CSV creates a separate table of values.
Browse your tables, inspect their structure and run SQL. Your database stays on this device.
Small files open in memory. Larger files need supported browser disk storage and enough free space. Encrypted and WAL-mode browser files are not supported.
Browse tables, views, indexes and triggers. Saving a database keeps its structure and data together; exporting CSV creates a separate table of values.
Browsing shows 100 rows at a time. Query previews show up to 1,000 rows per statement. Use All rows CSV or a complete read-only query export for the full result.
Files are processed in this browser. Save changes before closing or refreshing. Browser storage can be cleared and does not provide crash recovery.
The fictional sample has books, authors and 3,001 loans, with relationships and a useful view. Browse tables, try a join, or export all loans to check a complete result.
Download sample SQLite databaseSELECT books.title, COUNT(*) AS loans FROM loans JOIN books ON books.id = loans.book_id GROUP BY books.id ORDER BY loans DESC;
No. File contents and SQL stay on this device. Ordinary page and asset requests reach the website host. This site does not provide remote AI access.
Yes, when it contains a supported SQLite 3 database. The .db extension is also used by other formats. Open the database, switch off Read only and review changes before saving a complete copy.
Files up to 100 MiB use an in-memory copy. Larger files need browser disk storage, isolation support and available quota. Exports can need extra free space. An unsupported browser shows a capability error.
No. CSV does not preserve tables, relationships, indexes, triggers or SQLite types. Formula-like text is guarded for spreadsheets. Save the complete SQLite database to retain its database structure.
The browser accepts one database file and cannot safely reconstruct its WAL companions. Use the source application to checkpoint and export a standalone database first. Do not delete sidecar files manually.