DB Browser for SQLite overview: a visual workbench for SQLite files
What DB Browser for SQLite is
SQLite stores an entire database in a single file, which is convenient until you need to look inside it. DB Browser for SQLite is a free desktop application that opens those files and gives them a proper interface: a database structure tree, a spreadsheet-like data browser, a SQL editor and an import and export toolset. It is released under the Mozilla Public License 2.0 and runs on Windows, macOS and Linux. Nothing is installed on a server, there is no daemon to start, and the program edits the file you point it at and nothing else.
How the main tabs fit together
The Database Structure tab lists tables, indexes, views and triggers, and provides the schema editor for creating or altering them. Browse Data shows the rows of the selected table with filters, sorting and a cell editor, which is the fastest way to fix a single wrong value or to inspect what an application actually wrote. Execute SQL accepts statements and scripts, shows results as a grid and can save a query for later. The File menu handles opening, attaching, importing and exporting; CSV and SQL dumps are supported there, and the pragma editor exposes SQLite settings through a friendly list.
Practical settings and limits
The tool works with SQLite files only. It is not a client for PostgreSQL, MySQL or other server databases, and it cannot act as a middle tier for a busy web application. SQLite itself allows one writer at a time, so an edit made while an application holds a write lock will fail or block; close the application or expect a lock error. Editing rows in the browser needs a way to identify the row, which normally means a primary key or rowid, so tables defined without either are safer to change with SQL. Very large files take noticeably longer to load in the data browser than the structure tab, and pulling a table with millions of rows into the grid is best avoided by adding a filter first.
When to choose something else
If you need one client for many server databases, a universal database tool is the right category. If your work is scripted or part of a build pipeline, the sqlite3 command-line shell fits automation far better. If you are developing an application, migrations and schema changes usually belong in code or a migration tool rather than a GUI. Choose DB Browser when you want to see, understand and correct a local SQLite file quickly.
- Best for
- Developers, testers and analysts who need to inspect or repair a local SQLite database file without writing queries first.
- Good to know
- It works only with SQLite files, and SQLite permits a single writer at a time, so edits can fail while another application holds the database open.
How to get started
- Download the Windows installer and run it, then start DB Browser for SQLite from the Start menu.
- Use Open Database to pick an existing .sqlite or .db file, or create a new one from the same menu.
- Explore tables in the Database Structure tab, then switch to Browse Data to page through rows and filter them.
- Select the Execute SQL tab to write queries; use Ctrl+Return to run the current statement and read results in the grid below.
- Write your change back with Write Changes before closing; the toolbar button only commits pending cell edits.
Questions & answers
Can it connect to MySQL or PostgreSQL?
No. It is a client for SQLite files only. For server databases you need a universal database tool that speaks those protocols.
Why did my edit fail with a database is locked error?
SQLite allows one writer at a time. Close the application that holds the file open, or wait for its transaction to finish, then write the change again.
Is it safe to edit a production database?
Editing a live file directly is risky. Work on a copy, keep a backup of the original, and remember that the application using the file caches data and will not see your change.