Did You Know? DiagnoLog learns and adapts with every use.
Upload a log file
Drag & drop your log file here, or click to browse.
.ips.logarchive.panic.txtand more
or
QUICK ACTIONS
Your files are processed securely and never stored.
Multi-Agent Verification
Every analysis is cross-checked by our Challenger agent for maximum accuracy.
Evidence First
All findings are grounded in verifiable evidence from your log. No guessing.
Smart Insights
Key patterns, anomalies, and root causes explained in simple, clear language.
Privacy Focused
Your logs are never stored or shared. 100% private and secure analysis.
What you can analyze
Crash Reports (.ips)Application crashes and exceptions
Jetsam EventsMemory pressure terminations
Kernel PanicsSystem panics and watchdog events
Performance LogsPower, thermal and performance data
And more…Many other diagnostic logs
System description quick start
Not sure what to upload? Describe
your system and issue in your own words.
0 / 500
This helps our AI focus on what matters.
Recent analyses
Resources
Decoding diagnostic data
Please wait while we analyze your log
0%
—
CURRENTLY
Preparing…
LIVE PROGRESS
DIAGNOSIS COMPLETE
—
?
LOG TYPE
—
The Diagnosis
—
Action Required
—
Diagnostics Overview
—
Analysis Confidence
—
Battery Health—
No data available for this log type
Technical Details
Extracted Signals
DEVICE INTELLIGENCE · VERIFIEDID: —
—/100Diagnostic Confidence
Confidence: —%Hash: —
STABILITY
—/40
—
BATTERY
—/30
—
HARDWARE
—/30
—
DEDUCTION LEDGER
AI INTERPRETATION
Stop. Back up your iPhone now.
A hardware-level fault has been detected. Attempting a software update,
factory reset, or restore on failing hardware can permanently brick the device (Error 9 / 4013).
Control how DiagnoLog looks, moves, and remembers your history.
Profile
UsernameChange the name DiagnoLog uses to greet you.
Analysis Model
BasicUnlimitedFor
everyday diagnostics and general log analysis. Handles all supported diagnostic logs with fast,
straightforward explanations.
Appearance
Dark ModeQuick toggle between light and dark. For finer control, use Background
Theme below.
Loading IndicatorChoose between a modern skeleton layout or a classic spinner.
Transition SpeedHow fast the view-to-loader-to-results choreography plays out.
Background ThemeChoose the base color of the interface. Black and White each have 4
shades - tap the small arrow to pick one.
Accent ColorChanges buttons, links, highlights, and active states throughout the
app.
Assistant PositionChoose where the floating assistant appears.
Floating SidebarToggle between a modern floating sidebar or a classic edge-to-edge
layout.
Accessibility
Reduce MotionTurns off animations, transitions, and spinners throughout the
app.
Privacy & History
Auto-clear HistoryAutomatically delete saved analyses older than the selected
period.
Clear all history nowPermanently deletes every saved analysis from this device.
About
VersionDiagnoLog v3.0.0 · Not affiliated with Apple Inc.
How DiagnoLog Works
1
You provide a diagnostic log
Paste raw text, drop a file, or browse for an .ips / .crash / analytics log straight from your iPhone's
Analytics Data.
2
Local fingerprinting — instantly, on your device
Before anything is sent anywhere, DiagnoLog scans the file locally to detect its type (crash, Jetsam,
battery, thermal, kernel panic, etc.) and format.
3
Structuring & evidence verification
The relevant fields — battery cycles, exception types, panic strings, thermal levels — are extracted and
cross-checked against the raw log. Nothing is kept in the final report unless it's actually found in your
file, which prevents made-up numbers.
4
Plain-English diagnosis
Verified evidence is turned into a severity rating, a diagnosis, and concrete next steps — plus a Genius
Bar chat so you can ask follow-up questions about your specific log.
5
Nothing is stored on our servers
Your log is processed for the analysis and discarded. Anything saved to History lives only in your
browser's local storage on this device.
Log Types Explained
Crash Report (.ips)
Your app crashed. The log captures the exception type (like EXC_BAD_ACCESS or SIGABRT), which process
failed, and the code path it was on when it went down.
Jetsam Event
iOS ran low on memory and force-killed an app to free up RAM for whatever you were using. Common on older
devices or apps with memory leaks.
💥
Kernel Panic (panic-full)
The operating system itself crashed — not just an app. Comparable to a Windows "blue screen." Usually
points to a hardware fault, driver issue, or corrupted memory, and forces an unexpected reboot.
⏱️
Watchdog Termination
An app took too long to launch, resume, or respond, and iOS force-killed it for being unresponsive. Often
shows the code 0x8badf00d.
🌡️
Thermal / Performance Log
The device got too hot and iOS throttled the CPU/GPU to cool it down. Shows up as reduced performance
during heavy use, charging, or hot weather.
Battery & Power Diagnostic (Analytics-Daily)
An aggregated log covering battery cycle count, capacity degradation, temperature history, charging
behavior, and whether the battery is a genuine Apple part.
ResetCounter
Tracks kernel panics and unexpected shutdowns over time. Used to confirm whether instability is a one-off
or a recurring hardware trend.
🐢
App Hang / Spindump
The app froze and stopped responding to touches, but didn't fully crash. iOS captured a snapshot of what
every thread was doing at that moment.
Accuracy & Methodology
1
Deterministic extraction first, AI second
Before any AI sees your log, a strict local parser pulls out known fields (battery cycle count, exception
type, panic strings, etc.). The AI is told to trust these values rather than re-guess them.
2
Every claim is checked against your raw log
Anything the AI reports — a number, a timestamp, a field — is verified against the actual text of your
log. If it can't be found there, it's rejected and left out of the report rather than shown to you.
3
Rule-based Decision Engine
Extracted signals are run through fixed rules (e.g. "battery capacity below 70% = critical") to rank
findings by severity and confidence — not left purely to the AI's judgment.
4
Hallucination Guard
The AI's reported battery and crash figures are cross-checked against the scanner's own extracted values.
If they disagree, the scanner's number silently overrides the AI's — and severity is never allowed to be
downgraded below what the rules found.
5
Challenger review
A second AI pass reviews the finished diagnosis specifically looking for reasons to disagree with it
before it's shown to you.
6
Confidence score
The confidence percentage blends rule-based signal strength (60%) with the AI's own confidence (40%).
Unmistakable evidence — like a recorded kernel panic — forces confidence to stay high regardless of what
the AI says.
Desktop Required
Real-time voice and live device diagnostics require the native app. Download DiagnoLog to unlock full hardware access.