Open a database file directly
Choose a SQLite file, browse its tables, inspect metadata, and review relationships without configuring a database server.
Open a SQLite file and understand what is inside.
Browse tables, inspect metadata and relationships, run SQL, edit records, and turn useful work from a local SQLite database into shared workflows and tools.
- Type
- Embedded relational database
- Explore
- SQLite file → table
- Connect with
- A local SQLite database file
What WhoDB lets your team do with SQLite
Move from exploring SQLite to building useful workflows, shared tools, and trusted data products—all without losing the context behind the work.
Updated August 25, 2026. Available actions depend on the permissions granted to your connected account.
Run native SQLite SQL
Query the file with SQLite SQL while keeping results beside the tables and records that explain them.
Edit and prepare local data
Create tables, add and update rows, delete records, import datasets, and generate relationally aware mock data when the file is writable.
Move beyond a one-off file inspection
Connect useful SQLite data to visual transformations, lineage, shared business models, functions, and internal apps.
From connected data to a workflow people can trust
Choose the SQLite file
Open a local database file directly—there is no hostname, port, or database server to configure.
Inspect tables and relationships
Understand the file's structure and records before writing SQL or changing data.
Make focused changes
Query, insert, update, delete, import, or generate test data through one consistent workspace.
Share what the file is used for
Carry approved data into project workflows, models, functions, or apps so its purpose is not trapped on one machine.
More than a SQLite file viewer
WhoDB gives developers and data teams the familiar essentials of a SQLite browser—tables, records, SQL, and editing—inside the same environment used for wider data work.
That is useful when a local application database, export, prototype, or test fixture needs to become understandable and reusable by more than one person.
WhoDB is a strong fit for
- Developers inspecting application and test databases
- Teams reviewing SQLite exports or local datasets
- Prototypes that need a path into repeatable workflows
- Data work that begins in a file but should not stay isolated
SQLite integration questions
Straight answers about setup, everyday tasks, and how WhoDB fits into your workflow.
How does WhoDB connect to SQLite?
Select a local SQLite database file. SQLite does not require a hostname, port, or separate database server.
Can WhoDB run SQLite SQL?
Yes. WhoDB runs native SQLite SQL and keeps results beside the file's tables, metadata, and records.
Can WhoDB edit a SQLite database?
Yes. When the file is writable, teams can create tables, insert and update rows, delete records, import data, and generate mock data.
Can SQLite data be used elsewhere in WhoDB?
Yes. SQLite data can participate in project transformations, lineage, models, functions, apps, and permitted AI-assisted workflows.
Explore another source
Give your team one place to explore, understand, and build with data across the systems you already use.
WhoDB for PostgreSQL
Use WhoDB as a PostgreSQL GUI and shared data workspace for SQL, EXPLAIN ANALYZE, record editing, imports, mock data, lineage, pipelines, and AI-assisted work.
WhoDB for MySQL
Use WhoDB as a MySQL GUI and data workspace for schema exploration, native SQL, record editing, imports, mock data, visual pipelines, lineage, apps, and AI.
WhoDB for MongoDB
Use WhoDB as a MongoDB GUI for collections, documents, sampled schema metadata, editing, mock data, relationship context, visual workflows, and lineage.