DB Browser for SQLite
A visual SQLite tool for inspecting schemas, editing small datasets, running SQL and importing or exporting data; this page focuses on macOS installation and safe file-based database work.
What DB Browser for SQLite does
DB Browser for SQLite opens a SQLite file to show tables, indexes, triggers and views, and provides a visual SQL editor plus import and export tools. It is useful for inspection and small controlled edits, but it does not replace a backup, a migration workflow or concurrency controls around an application that is still writing the file.
File consistency matters
SQLite may use a main database file together with WAL or SHM companions. Close the application that owns the database before making a copy, preserve the related files when needed and perform changes on a test duplicate first. SQL history, exports and copied databases may contain sensitive information.
Maintenance note
This page reviews DB Browser for SQLite 3.13.1 on macOS, schema and SQL workflows, transactions, imports, exports and complete file backups. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave DB Browser for SQLite to this cloud drive
Baidu Netdisk
Save DB Browser for SQLite to this cloud drive
DB Browser for SQLite 3.13.1 macOS and safe editing guide
Copy a test database, inspect its structure and run a read-only query before attempting an import or data change on a real SQLite file.
Before you start
- Confirm the macOS version and prepare a consistent SQLite copy with its WAL and SHM companions when present.
- Identify tables, constraints and fields that may contain personal or business-sensitive data.
- Close the application that writes the database before copying or changing the file.
Installation steps
- 01
Install the macOS DMG
Open the DMG, move the application to Applications and verify the version and macOS permission prompts on first launch.
- 02
Open a copy and inspect the schema
View tables, indexes, triggers and views in a duplicate, run a bounded read-only query and record the original file hash.
- 03
Test a transaction
Preview the rows affected by a change, use a transaction when supported and confirm constraints, row counts and rollback behavior on the duplicate.
Quick start
- 01
Preview every write
Run the same WHERE clause as a SELECT before UPDATE or DELETE, limit the sample and save the before-and-after row counts.
- 02
Import a small sanitized sample
Check CSV encoding, delimiter, headers, NULL values and column types with a small sample, then validate constraints before a larger import.
- 03
Run an integrity check
Reopen the modified copy, run an integrity check and verify that the application reading the database still sees the expected schema and data.
Usage tips
- A graphical editor reduces SQL friction but makes accidental writes easy; use copies and rollback points for important files.
- Backups should cover the main SQLite file and relevant WAL or SHM companions, not just a screenshot or CSV export.
- Query results, SQL history and exported files should be treated as sensitive until they are reviewed and cleaned.
Troubleshooting and uninstall
What should I do when the database is locked?
Close the application using the file, confirm that no write process or transaction remains, and operate on a consistent copy instead of deleting lock-related files.
Why can the application no longer open the edited file?
Stop further writes, preserve the current file and backup, run an integrity check and compare the schema. Restore the latest usable copy before analyzing the change.
- Archive the database copiesClose open files, label the original and modified copies, remove temporary sensitive exports and confirm the backup can be opened separately.
- Remove the applicationQuit DB Browser for SQLite and remove it from Applications, then clear configuration and caches only when the retained data has been reviewed.
Frequently asked questions
Can DB Browser for SQLite replace a production migration tool?
It is best for inspection, troubleshooting and small controlled edits. Production changes still need backups, transactions, review, deployment order and application-level testing.
Why should a SQLite backup include WAL and SHM files?
Depending on the journal mode and timing, recent committed state can involve companion files. Close the writer and make a consistent copy rather than copying only the main file blindly.
Is a CSV export a complete database backup?
No. CSV usually omits indexes, triggers, views, constraints and some type information. Keep a tested database copy and use exports for specific data exchange tasks.