Exporting Reports

Share crash analysis as a self-contained PDF.

How to export

With a crash dump open and analysis complete:

  • Toolbar click the Export PDF button
  • File menu go to File > Export PDF
  • Keyboard shortcut press Ctrl+P

A save dialog will appear. Choose a location and filename, then click Save. The PDF is generated immediately no upload or network request is involved.

What's included in the export

The exported PDF contains a structured crash report with the following sections:

  • Summary header exception type, fault address, crash timestamp, and OS/processor info
  • Intel Engine findings crash classification, confidence score, indicators, and secondary findings
  • Stack trace the symbolicated call stack of the crashing thread, with function names, source files, and line numbers where available
  • AI explanation root cause, evidence, and suggested fix from Explain Mode, if an explanation was run before exporting
  • Thread list all threads with IDs and suspend counts
  • Module list loaded DLLs and EXEs with base addresses and versions

If you opened a UE crash folder, the UE Context section (engine version, build configuration, hardware info) is also included.

Getting Explain Mode into the export

The AI explanation is only included in the PDF if Explain Mode was run before you exported. Open the Explain tab and wait for the response to appear, then export. If you haven't set up Explain Mode yet, see the Explain Mode guide.

Common use cases

Filing a bug report

Attach the PDF to your internal bug tracker alongside the original .dmp file. The structured format makes it easy for other engineers to understand the crash without needing to open CrashCatch themselves.

Submitting to an engine vendor

When reporting a crash to Epic Games or a middleware vendor, the PDF gives their support team a complete picture of the crash context stack, modules, exception code, and your analysis in a format they can open without any special tools.

Archiving

Export and archive reports for crashes that are fixed, so you have a record of what the crash looked like and what resolved it. This is useful for tracking regressions if a similar crash reappears later.