Android messaging artifacts
SMS and MMS Database Viewer
Inspect Android mmssms.db messaging artifacts locally with thread views, timestamps, participants, SMS, MMS, and CSV export.
Safe classroom workflow
Open a copy of Android messaging evidence, inspect threads and MMS parts, then export only the rows needed for a lesson or report.
The selected file is processed in your browser. It is not uploaded to MuhammadLab servers.
Load Android mmssms.db
Export the database from an authorised device or evidence image, then open it here for local inspection.
1. Export
Work from an authorised Android device, forensic image, or lab sample. Keep the original evidence untouched.
2. Open locally
Choose a .db, .sqlite, or .sqlite3 file. MuhammadLab reads it in the browser and does not upload it.
3. Analyse
Review SMS, MMS, participants, timestamps, attachments, and missing tables before exporting CSV.
Evidence preparation
How to get mmssms.db safely
Use only devices and images you are authorised to examine. Always work on a copy, record the source, and hash exported evidence before analysis.
Rooted or forensic image workflow
adb devices
adb shell su -c "cp /data/data/com.android.providers.telephony/databases/mmssms.db /sdcard/mmssms.db"
adb pull /sdcard/mmssms.db ./evidence/mmssms.db
sha256sum ./evidence/mmssms.dbWhat this viewer extracts
The tool reads common Android tables such as sms, pdu, addr, part, and threads. Vendor schemas can differ, so use the artifact status panel to explain what was present or missing.
Processed Locally
Your file never leaves your device. Everything is processed in your browser — we never see or store your data.