View an Android SQLite database

First export the database legally and safely

SQLite Viewer opens a file that you already possess; it does not extract databases from a phone. Use Android Studio’s Device Explorer, an emulator, an application backup or your own debug tooling to obtain a database you are authorized to inspect.

Android app databases commonly appear under an application-specific databases directory and may use .db or no extension. If the browser picker does not show an extensionless copy, rename the exported file to end in .db.

Open and inspect the app schema

1. Drop the exported database onto SQLite Viewer.
2. Search the table sidebar for the feature you are debugging.
3. Open likely tables and inspect recent rows.
4. Use the ER diagram to understand foreign keys and Room-style relationships.
5. Run focused SQL instead of scrolling through large event or cache tables.

SELECT *
FROM "sync_queue"
ORDER BY "created_at" DESC
LIMIT 0, 100;

Handle WAL databases correctly

SQLite may use write-ahead logging, producing -wal and -shm companion files. Copying only the main database while the app is writing can omit recent transactions. Prefer a consistent export created while the database is closed or checkpointed.

Editing Android databases

You can edit a copy and download it, but replacing an app database can violate schema expectations or corrupt application state. Keep the original, validate constraints and use supported migration or debug tooling whenever possible.