Where macOS Stores Safari Crash Reports and Hang Logs

When the Safari web browser or a Safari Web Content process terminates unexpectedly, macOS automatically generates diagnostic files to record the state of the application at the moment of failure. This article provides a direct guide to locating these crash reports and hang logs within the macOS file system, detailing the exact directory paths, file naming conventions, and how to view them using the built-in Console utility.

Primary File Locations

macOS separates diagnostic data into user-level and system-level directories. Depending on the nature of the termination, your Safari logs will be stored in one of two locations.

1. User-Specific Crash Reports Most Safari application crashes and individual tab crashes (Web Content processes) occur at the user level. They are stored in your hidden User Library folder at the following path: ~/Library/Logs/DiagnosticReports/

2. System-Wide Crash and Hang Logs If a Safari failure causes a system-wide freeze, involves root-level processes, or generates a heavy hang log, macOS writes the file to the main System Library folder: /Library/Logs/DiagnosticReports/

How to Access the Log Folders

Because the User Library folder is hidden by default in macOS, the fastest way to reach these directories is through the Finder's navigation shortcut:

  1. Open Finder.
  2. Press Command + Shift + G on your keyboard to open the "Go to Folder" prompt.
  3. Paste ~/Library/Logs/DiagnosticReports/ or /Library/Logs/DiagnosticReports/ into the text field and press Return.

Identifying Safari and Web Content Files

Once inside the DiagnosticReports directory, you will see various files named after the processes that generated them, followed by the date and time of the incident.

Look for files starting with these specific prefixes:

  • Safari: Indicates the entire web browser crashed.
  • com.apple.WebKit.WebContent: Indicates a specific webpage or browser tab crashed without taking down the entire browser.
  • com.apple.WebKit.Networking: Indicates a crash within Safari's network loading process.
  • com.apple.WebKit.GPU: Indicates a crash related to hardware acceleration and media rendering in Safari.

File Extensions

  • .ips: Used in macOS Monterey (12.0) and newer. These are JSON-formatted crash and diagnostic reports.
  • .crash: Used in macOS Big Sur (11.0) and older for standard process crashes.
  • .hang or .spin: Generated when Safari becomes unresponsive (shows the spinning wait cursor) and is forced to quit by the user. These are most commonly found in the system-level /Library/Logs/DiagnosticReports/ folder.

Viewing Logs via the Console App

You do not need to manually navigate the file system to read these logs. macOS includes a dedicated log viewer that aggregates these files automatically.

  1. Open the Console application (located in /Applications/Utilities/).
  2. In the left sidebar, select Crash Reports to view unexpected terminations (both .ips and .crash files).
  3. Select Spin Reports in the sidebar to view logs generated by application hangs and unresponsiveness.
  4. Use the search bar in the top-right corner to type Safari or WebKit to filter the list.
  5. Right-click any report in the list and select Reveal in Finder to go directly to the raw file on your drive.