Saving, exports and limits
Browse, then choose whether to edit
The database starts in Read only mode. Browse Data shows records; Database Structure shows tables, relationships and SQL definitions; Execute SQL runs statements. To edit, open Editing settings and turn off Read only. Stage row changes and use Apply or Revert. Unstaged cell edits stay in the inspector until you stage or explicitly discard them; resolve them before paging, switching tables or saving. New rows can be cancelled explicitly.
Save the database
Use Save a copy to write a complete SQLite file. A supporting browser asks where to write it; other browsers offer a download. Check the output before closing. A copied export does not overwrite the original selected file or clear its unsaved mark. To replace the working database after saving a copy, review the unsaved-changes prompt and choose Discard. New databases have their own primary save action.
Create a new file
Create a database starts a named blank SQLite file or a Tasks table with no records. It opens in inspection mode; turn off Read only in Database settings when you want to add data or change its structure. Save as keeps a complete local copy.
Export complete results
Export CSV opens the existing export tools. Select a table, choose All rows CSV and review the active filter and sort. Query export accepts one read-only statement. Preview exports contain only the displayed result. Export JSON preserves exact tagged values and positional columns; CSV is for spreadsheet use and guards formula-like text.
Limits and browser disk storage
Small files use an in-memory copy up to 100 MiB. Larger files require supported browser disk storage and isolation, enough free quota and temporary snapshot space. Query previews retain up to 1,000 rows per statement and the latest 20 results. A script contains up to 100 statements. Complete text exports in this site are capped at 32 MB. Larger database files can still use the supported disk path.
CSV/TSV imports accept UTF-8 files up to 5 MB and 10,000 rows with explicit column mappings. Unsupported encrypted databases, WAL-mode browser files and unavailable SQLite extensions produce errors. Export a standalone database in the source application first.
Recovery and errors
Save before refreshing or closing. Short-lived entry storage can reopen the original selected file; it does not recover later edits. When an export fails, keep the editor open, check storage and permissions and retry. Cancelled queries and failed reviewed changes preserve the working database.