WordPress Fatal Error Investigator
Group PHP failures and locate the recorded plugin, theme or core file.
Manual analysis on this device. Your selected reports stay in this browser.
Start with a manual evidence export from your site, a supported diagnostic report, or the labelled example below.
Try a worked example
Synthetic data illustrates a failure, a control and insufficient evidence. Loading an example replaces the current form inputs.
Analysis results
Preparing the local analyzer.
Download the derived report with its measurement details. It does not include the original input file.
Prepare your evidence
Use a recent sanitized PHP error log or an evidence report containing errors. The file and stack trace identify where a failure was recorded, not necessarily its original cause.
The manual WordPress exporter collects supported site metadata. Runtime investigations can need a separate trace or controlled test. Each result lists missing evidence. A public website address alone cannot reveal internal database work or plugin behavior.
Read the result and check the repair
Start with the observed failures and their evidence. Follow the next action for the affected item, then collect a new report using the same scope. Use the earlier report when this tool supports comparison. Differences between sites, collection windows or test conditions can prevent a meaningful comparison.
Local processing and limits
Files and pasted evidence are analyzed in your browser. They are not uploaded, added to the page address or saved in browser storage. Each input is limited to 2 MiB, with further limits shown by the analyzer. Closing or clearing this page removes its report from the page.
Exports contain the derived findings and measurement details. Review names, paths and text before sharing. A successful check describes the supplied evidence; it does not certify a whole website or replace a staging test.