Skip to content
| Marketplace
Sign in
Visual Studio Code>Data Science>DBScout — Android & iOS Database InspectorNew to Visual Studio Code? Get it now.
DBScout — Android & iOS Database Inspector

DBScout — Android & iOS Database Inspector

EESystems

|
54 installs
| (5) | Free
Inspect the SQLite databases of Android and iPhone apps, and .db files, without leaving the IDE.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Your phone's databases, right in your IDE

Stop pulling .db files by hand. DBScout opens the SQLite databases of the Android and iPhone apps you are developing — on the phone, in the iOS Simulator, and any .db file on this computer — in a panel inside your IDE. Browse apps, databases and tables, watch rows change while the app runs, and write SQL against the real data on the device.

Works in VS Code, Antigravity and other editors built on VS Code. Follows the IDE theme (light and dark) and language.

Features: Browse · Column filters · App preferences · Hive boxes · Encrypted databases · Schema diagram · App log · iOS Simulator · Android over Wi-Fi · SQL query tab · Saved queries and history · Snapshots and restore · What changed · AI chat and shortcuts · Components · Light and dark

More: Requirements · Privacy

In the screenshots, the yellow circle marks the button that opens each feature.

Browse apps and databases

The tree with each app as a row with a colored letter, its name and package, the databases inside it and the rows of a table in the grid; the app row is circled

Plug the phone in, open DBScout: Open (or the DBScout item in the status bar) and the panel lists every debuggable app — a colored letter, the app's name and its full package — with the databases inside it and the row count of each table. Pick a table to see its rows; with Live updates on, the grid follows what the app writes, and what just changed flashes: a green bar on a new row and an amber underline on a changed cell, with the last change summed up in the footer ("1 new row, 2 cells changed at 09:42:11"). Sorting and paging are in the grid. A double click edits a cell, and the trash button deletes a row (DBScout asks first). On the phone the app stays open, so you see the change in it; in the iOS Simulator DBScout closes the app first.

JSON in a cell. A text cell that holds a JSON object or list gets a { } button. It opens the JSON next to the grid, as a tree or as formatted text, with search over keys and values, and it follows its row while live updates read the table again. Numbers show exactly as stored, even IDs too large for JavaScript. Edit changes the JSON there: Save turns on only for valid JSON and tells the line and column of a mistake.

Column filters

The grid filtered by the text "re" typed under a column name, and the locked field that names the table's database; both circled

Type in the box under a column name to filter: the grid keeps the rows whose value contains the text (case-insensitive), and the filters stay with the tab. The locked field at the top of the tab names the database and app the table belongs to. Export saves exactly the filtered rows to CSV, Excel or TXT.

App preferences

The Preferences node of an app open in the tree, and the keys, types and values of a SharedPreferences file in the grid; the node is circled

Next to its databases, each app shows a Preferences node with its preferences files: SharedPreferences (shared_prefs/*.xml, including Flutter's shared_preferences), Preferences DataStore (files/datastore/*.preferences_pb) and, on the iPhone, UserDefaults (Library/Preferences/<bundle id>.plist). Click a file to see its keys, types and values in the grid.

On Android, a double click edits a value and the trash button deletes a key. An app keeps its preferences in memory while it runs and would overwrite the edit, so saving closes the app first (am force-stop) — DBScout asks the first time; open the app again to see the new value. On the iPhone and in the iOS Simulator, preferences are read-only.

Hive boxes

Flutter apps that store data with Hive (hive or hive_ce) get a Hive node next to their databases, with one row per box (app_flutter/*.hive on Android, Documents/*.hive on the iPhone and in the iOS Simulator). An app that uses only Hive shows up too. Click a box to see its keys, types and values in the grid; with Live updates on, it follows what the app writes. An object of the app's own classes opens in the JSON panel, with its typeId and its fields by @HiveField number — Hive does not store field names — and a value of one of the app's enums shows its index. Hive boxes are read-only.

Each box can be encrypted on its own (HiveAesCipher), so the lock is per box: an encrypted box shows its keys but not its values, with a red lock next to its name. Click the lock and paste the box's 32-byte key — 64 hexadecimal digits, base64 (as base64Encode(Hive.generateSecureKey()) saves it) or the Dart list [0, 7, 14, …]. DBScout checks the key the way Hive does, decrypts the values in its copy and turns the lock green; the same key is tried on the app's other encrypted boxes. The key is saved in the system's secure store, and the green lock locks the box again.

Encrypted databases (SQLCipher)

Databases encrypted with SQLCipher — sqflite_sqlcipher in Flutter, SQLCipher for Android, and any .db file on this computer — show up in the tree marked encrypted, with a red lock next to the name. Click the lock and type the key the app uses: the passphrase, or a raw key in hexadecimal as x'2DD29CA8…'. DBScout finds the SQLCipher version on its own (4, 3, 2 or 1), and the database then works like any other: the grid, filters, live updates, SQL, editing, snapshots. Edits stay encrypted with the same key on their way back to the phone. The key is saved in the system's secure store (Keychain on macOS, Credential Manager on Windows) only after it opens the database, and the lock turns green. Clicking the green lock asks first, then locks the database again: the key is deleted and its tabs close.

Schema diagram

The Schema tab of a database: one box per table with its columns, primary and foreign keys marked, lines for the foreign keys and the relations listed below; the diagram button on the database row is circled

The diagram button next to each database opens a Schema tab: one box per table with its columns (primary and foreign keys marked), lines for the foreign keys, and below it the relations and the indexes of each table as text. Databases created with sqflite usually declare no foreign keys; the tab shows the tables and says that no relation is declared.

App log

The Log tab of an app with coloured levels, SQLite lines highlighted and a database path turned into a link; the log button on the app row and the link are circled

The log button on an app (Android) opens a Log tab with the last 500 lines of that app's log (logcat); if the app isn't running, the lines of the system log that mention it or come from its processes, so a crash's stack trace shows up too. Levels are coloured, SQLite lines (SQLiteLog, SQLiteDatabase, SQLite…Exception) are highlighted, and a database path the tree knows, inside that app's own folder (databases/<name>.db, app_flutter/<name>.db), becomes a link that shows that database in the tree. Refresh log reads it again. The log stays on screen: it is not stored, not sent anywhere, and leaves memory when you close the tab.

iOS Simulator

The device selector showing "iPhone 16 Pro · Simulator", with a Core Data database of an app and the rows of a table; the selector is circled

On a Mac with Xcode, every booted simulator shows up in the device selector as "<name> · Simulator", next to the phones — no cable. DBScout reads the data folder of each app installed by Xcode or by flutter run, and Core Data databases are labelled as such.

Android over Wi-Fi

The Connect over Wi-Fi dialog with the pairing address, the six-digit pairing code and the connection address filled in; the Connect over Wi-Fi button is circled

Connect over Wi-Fi, next to the device selector, connects an Android 11+ phone with Wireless debugging on, no cable. The first time, fill in the address and six-digit code from "Pair device with pairing code" (adb pair); then only the IP address and port shown on the Wireless debugging screen (adb connect). The phone shows up as "<name> · Wi-Fi" and works as on the cable. Never used Wireless debugging? The i button in the dialog walks through it step by step, from turning on Developer options to each field, and Where do I find it? next to each field shows the phone screen with the value marked (pictures with example numbers). The iPhone needs none of this: on the same Wi-Fi network as the Mac, it shows up on its own.

Components

The Components list with ADB and Xcode installed; the Components button in the right-hand bar is circled

The Components list says what this computer needs to recognize the phone and what is missing. ADB installs with one click; nothing is installed without one.

Light and dark theme

The panel in the light theme, with the columns and types of a table open in the tree; the arrow that shows them is circled

The panel takes the colors of the IDE theme, light or dark. The arrow next to a table shows its columns and their types, without leaving the tree.

SQL query tab

A query tab with an SQL editor, Run and the result in the grid; New query and Run are circled

New query opens a tab with an SQL editor bound to the database you choose, with autocomplete of tables and columns. Ctrl+Enter runs it. Each query keeps its own tab, so you can compare results side by side, and results sort and page like a table. When the query reads a single table, a double click edits the result in place, and Export saves the whole result to CSV, Excel or TXT.

Saved queries and history

The Queries dialog with a saved query (Rename, Delete) and the history of the last queries that ran; the Save and Queries buttons are circled

In the query tab, Save keeps the query with a name, and Queries lists the saved ones (rename, delete) and the last 50 queries that ran, per app, with Clear history. Picking one puts the SQL in the editor; it does not run it. They are kept in a file on this computer and never leave it.

Snapshots and restore

The Snapshots dialog with two named snapshots, each with Compare with now, Restore and Delete; the Snapshots button and a Restore button are circled

Snapshots, in the table tab's toolbar, saves the whole database as it is right now — copied fresh from the device — with a name (or the date and time). Restore puts the database back the way it was: DBScout asks first, closes the app on Android, then replaces the database on the phone, in the iOS Simulator or in the .db file (on the iPhone and in the Simulator, close the app yourself first). Snapshots are kept only on this computer, in DBScout's data folder, until you delete them (uninstalling the extension does not); they never leave the machine.

What changed

A read-only comparison tab: the changed table with 2 updated and 1 deleted, and the rows with the change and each updated cell as before → after; the tab is circled

What changed?: in the Snapshots dialog, Compare with now compares a snapshot with the database as it is now, and checking two snapshots compares them with each other. The comparison opens in a read-only tab: the tables that changed, with how many rows were inserted, updated and deleted (plus new and removed tables), and the rows of the table you pick, with the change and each updated cell as "before → after". The workflow: save a snapshot, use the app, compare with now. Rows are matched by primary key (by rowid when there is none, or when it repeats); the list shows up to 500 rows of each kind per table and stops earlier on very large comparisons, while the totals always count every row. UTF-16 databases are not compared. Comparing stores nothing.

AI chat and shortcuts

A table tab with the Generate test data and Find inconsistencies buttons and the Claude Code chat open on the right with a prepared question in the draft; the two shortcuts and the Claude Code button are circled

The bar on the right opens a chat with Claude Code or Codex, the same as in the DBScout desktop app. The assistant reads the tables and the app preferences of the phone that is plugged in — starting from the database and the table on screen — and answers about them: it counts, filters and compares, draws charts and writes ready-to-run SQL.

It has no access to files, the terminal or the web, only to DBScout. It runs the CLI on your computer with your own account with Anthropic or OpenAI: sign in once from the chat, or install it with one click. DBScout has no partnership with those vendors.

Three shortcuts prepare a question for you: Write with AI in the query tab turns a request in plain language into a question for an SQL query, and the SQL that comes back has "Open in a query tab"; Generate test data (1 to 500 rows) and Find inconsistencies (orphan rows, empty required fields, impossible dates, duplicates; the question asks the assistant to only read, which is a request, not a lock) sit in the table tab. The question goes to the chat's draft, replacing what was there, and nothing is sent until you press Enter.

Requirements

  • Android: adb (DBScout installs it with one click if it is missing), USB debugging on the phone and the app installed as debuggable (a debug build).
  • iPhone (macOS only): Xcode, and the app installed by Xcode or by flutter run.
  • iOS Simulator (macOS only, no cable): Xcode, a booted simulator, and the app installed by Xcode or by flutter run. It appears in the device list as "<name> · Simulator".
  • Android over Wi-Fi (no cable): Android 11 or later with Wireless debugging on, on the same network as this computer. Connect over Wi-Fi, next to the device selector, pairs the first time with the address and six-digit code from "Pair device with pairing code" (adb pair), then connects to the IP address and port shown on the Wireless debugging screen (adb connect). The data then travels over your local network, between the phone and this computer. A phone connected this way shows up in the device list as "<name> · Wi-Fi", next to the same phone on the cable, if it is plugged in too.

adb and devicectl run on the machine where the cable is: the extension always runs on the UI side, even with a remote workspace. In a remote window, .db file mode opens only files from this computer.

Privacy

  • An app's log (Android) is shown on screen only: it is never stored or sent, and the AI only sees a log line if you paste it into the chat.
  • Nothing you open — file paths, database contents, package names — leaves the computer, except what you ask the chat: the assistant's CLI sends your question and what it reads from the databases to Anthropic or OpenAI, under your own account.
  • The extension reaches the network only to check the activation key (the key and a hash of the machine identity) and to download adb or an AI assistant when you click install. The panel itself has no network access, except for Google Fonts. No telemetry.
  • Saved queries and query history are kept on this computer, one file per app in the DBScout data folder. The SQL can contain data you typed in it; it is never sent anywhere, and uninstalling does not delete it — delete saved queries and clear the history in Queries.
  • Snapshots are full copies of a database, kept only on this computer in the DBScout data folder until you delete them; they are never sent anywhere.
  • The key of an encrypted database is kept in the system's secure store (on Linux, in a file in the DBScout data folder readable only by you), never leaves the computer, and the green lock next to the database deletes it.
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft