Open, browse and edit SQLite databases (.db / .sqlite / .sqlite3) in VS Code with a native-feeling UI.
Features
Open a database file as a custom editor with three tabs: Data, SQL Console, Structure.
Native sidebar tree: database → tables / views → columns (type, primary key). Click a database node to open it.
Token-themed paginated table that follows the active theme, with a per-page selector (50 / 100 / 200 / 500 / 1000 / Show all).
Double-click a cell to edit (an unchanged value does not mark the file dirty), Ctrl+Z undo, Ctrl+S writes back to disk, and a reload prompt appears when the file changes externally.
Search across all columns with LIKE pagination; wildcards (% / _) are escaped to match literally.
SQL Console: run arbitrary SQL (Ctrl+Enter), see the result grid, affected rows, or errors; non-read-only statements mark the file dirty and refresh the table list.
Structure editing: inspect columns (type / PK / not null / default); create a table, add or drop a column, or drop a table via native dialogs.
Export the current table (or the search results) to CSV / JSON via a save dialog.
Language: set sqlite.language — auto (follow VS Code display language), en, or zh (default English). Applies across the web UI and host dialogs.
Views are read-only; BLOBs shown as a byte length; NULL values shown in italics.
Driver is sql.js (WebAssembly): self-contained, cross-platform, no native compilation.
Usage
Install the extension, then right-click a .db / .sqlite / .sqlite3 file → Open Database (or run SQLite: Open Database from the command palette).
Browse a table in the Data tab; double-click a cell to edit; search, or sort by clicking a column header.
Run SQL in the SQL Console tab, edit the structure in the Structure tab, and export from either tab.
Development
npm install
npm run compile # build the extension + bundle webview/sql.js
npm run watch # watch mode (node/npm must be on PATH; scripts/with-node.ps1 helps)
npm test # headless driver integration test
npm run package # build the .vsix
Press F5 in VS Code to debug in the Extension Development Host.
Dev build tasks locate node/npm via scripts/with-node.ps1 (compatible with fnm and regular Node installs).