Choose a SQLite database file and see its tables and rows straight away. Search and sort the data, look at the columns and indexes, run your own SQL, and export any table or result to CSV or JSON. Everything runs in your browser, so the database is never uploaded.
For a debuggable app, run these two commands in cmd: adb shell "run-as your.package.name cp databases/app.db /sdcard/Download/app.db" and then adb pull /sdcard/Download/app.db . (this keeps the file exactly as it is). You can also use Device Explorer in Android Studio (data, data, your package, databases) and save the file. Then open it here.
Android databases usually run in WAL mode: the newest changes live in a separate file called app.db-wal until they are merged. A browser opens only the main file. Pull the -wal and -shm files too and merge them with the sqlite3 tool, or run PRAGMA wal_checkpoint(FULL); on the device before copying. The tool warns you when it sees a WAL-mode database.
Yes, in the SQL tab: tick "Allow changes" and run an INSERT, UPDATE or DELETE. Your original file is never touched - the change happens in a copy inside your browser, and you download a new database with the Download button. Without the tick the database is read-only.
No. SQLite is compiled to WebAssembly and runs on your own computer. The file is read in the browser and nothing is sent anywhere.
Up to about 150 MB, because the whole file is loaded into the browser memory. For bigger databases use the sqlite3 command line or DB Browser for SQLite.
The file must start with the SQLite header. The message tells you what the file really is - an empty file, a text file holding an error message, a copy damaged by the PowerShell redirect (>), a WAL file, or an encrypted database (SQLCipher) - together with its size and first bytes. Encrypted databases and databases of other kinds (Realm, MySQL) cannot be opened here.