MuhammadLab

Android logs and forensic triage

Logcat Analyzer

Paste or upload exported Android logcat text, then filter by severity, package, timestamp, tag, and forensic keywords.

LogcatSeverity filtersPackagesEventsLocal only

Fast forensic triage

Paste an exported logcat capture, surface crashes and suspicious events, then export the filtered rows for class notes or case documentation.

Logs are parsed in your browser. Nothing is uploaded.

Load exported logcat text

Paste logcat output or upload a `.txt` / `.log` export from an authorised device.

1. Capture

Export logcat from an authorised Android device using ADB, then preserve the original text file.

2. Filter

Use severity, package, tag, timestamp, and forensic keyword filters to reduce noise quickly.

3. Document

Export filtered rows to CSV and include command history, hashes, and timezone notes in your report.

Collection guide

How to export logcat

Capture logs from an authorised test device or evidence workflow. Record timezone, device state, command used, and hash the exported file.

Common ADB commands

adb devices
adb logcat -d > logcat_dump.txt
adb logcat -v threadtime -d > logcat_threadtime.txt
adb logcat -b crash -d > logcat_crash.txt
adb logcat -s ActivityManager AndroidRuntime PackageManager > focused_logcat.txt
sha256sum logcat_threadtime.txt

Teaching notes

Logcat is volatile and noisy. Treat it as timeline support rather than a complete evidence source. Cross-check important events with app databases, screenshots, system settings, and acquisition notes.

Processed Locally

Your file never leaves your device. Everything is processed in your browser — we never see or store your data.

Frequently Asked Questions