How to View Mac App Crash Logs Using Terminal

Illustration for How to View Mac App Crash Logs Using Terminal

When a Mac app crashes, macOS records details about what happened in a crash report. You can view recent reports in Terminal with a few built-in commands, then use the information to identify the affected app, the crash time, the macOS process involved, and possible causes.

The easiest method is to search the unified log for crash events. You can also open the saved crash-report files directly from Terminal when you need more technical detail.

Quick Answer

Open Terminal from Applications > Utilities, then run:

log show --predicate 'eventMessage CONTAINS[c] "crash"' --last 24h

This displays crash-related entries from the last 24 hours.

To list saved application crash reports, run:

ls -lt ~/Library/Logs/DiagnosticReports

To open that folder in Finder:

open ~/Library/Logs/DiagnosticReports

Look for a file whose name matches the app that crashed. Open the report with Console, a text editor, or Quick Look to inspect its details.

Before You Start

Terminal commands are generally safe when you are only viewing logs. The commands in this guide do not delete reports or change macOS settings.

However, crash reports can contain technical details about your Mac, account names, file paths, and the apps you use. Avoid posting a complete report publicly without reviewing it first. If you share a report with an app developer, remove personal information when appropriate.

If the app is still frozen, save your work if possible before closing it. Force quitting can discard unsaved changes. For help closing a frozen app, see How to Force Quit an App on a Mac.

Open Terminal on Your Mac

  1. Press Command-Space to open Spotlight.
  2. Type Terminal.
  3. Press Return.
  4. A window with a command prompt appears.

You can also open Terminal in Finder by selecting Applications, opening the Utilities folder, and double-clicking Terminal.

Commands are entered after the prompt. Press Return after entering each command. Terminal normally returns to a new prompt when a command finishes.

Method 1: Search Recent Crash Events

The log show command searches macOS’s unified logging system. The following example searches the previous 24 hours:

log show --predicate 'eventMessage CONTAINS[c] "crash"' --last 24h

What the command means

  • log show reads stored macOS log entries.
  • --predicate filters the results.
  • eventMessage CONTAINS[c] "crash" searches log messages containing “crash.”
  • --last 24h limits the search to the last 24 hours.
  • The c makes the text search case-insensitive.

The output may include more than app crashes. It can also show crash reporters, background services, or system processes that logged the word “crash.” Use the timestamp and process name to identify entries related to your app.

Search a longer period

To search the last seven days:

log show --predicate 'eventMessage CONTAINS[c] "crash"' --last 7d

You can also specify a date range:

log show --predicate 'eventMessage CONTAINS[c] "crash"' --start "2025-01-15 00:00:00" --end "2025-01-16 00:00:00"

Replace the dates with the period you want to investigate.

Search for one app

If you know the app’s process name, add it to the predicate. For example:

log show --predicate 'process == "Safari" AND eventMessage CONTAINS[c] "crash"' --last 24h

Replace Safari with the process name used by the affected app. The process name is not always identical to the app’s name. For example, an app may use a helper process or a shortened name.

You can also search for the app name in the message:

log show --predicate 'eventMessage CONTAINS[c] "Safari"' --last 24h

This broader search can return normal activity as well as errors, so review the timestamps and message text carefully.

Make long output easier to read

If Terminal displays a large amount of text, pipe the results into less:

log show --predicate 'eventMessage CONTAINS[c] "crash"' --last 24h | less

Use the Up Arrow and Down Arrow keys to scroll. Press Space to move down one screen and press Q to quit the viewer.

To save the results to a text file on your Desktop:

log show --predicate 'eventMessage CONTAINS[c] "crash"' --last 24h > ~/Desktop/mac-crash-log.txt

This creates a file named mac-crash-log.txt on your Desktop. It does not alter the original logs. Double-click the file to open it in the default text editor.

Method 2: View Saved Crash Reports

macOS often saves detailed reports in the DiagnosticReports folder in your user Library.

List the newest reports first:

ls -lt ~/Library/Logs/DiagnosticReports

The ls command lists files. The -l option shows details, and -t sorts them by modification time, with the newest files first.

Typical filenames may include the app name, a date, and a .ips or .crash extension. For example, a report might resemble:

ExampleApp-2025-01-16-103015.ips

The exact filename and format can vary.

Open the reports folder in Finder

Run:

open ~/Library/Logs/DiagnosticReports

Finder opens the folder so you can sort reports by name or date. Double-click a report to open it. Depending on its format and your Mac’s settings, it may open in Console, TextEdit, or another default application.

This method is useful when you want to browse reports visually instead of reading a long Terminal result.

Display the newest report in Terminal

To print the newest file in the folder:

latest=$(ls -t ~/Library/Logs/DiagnosticReports | head -n 1)
cat ~/Library/Logs/DiagnosticReports/"$latest"

The first line stores the newest filename in a temporary shell variable. The second line prints that file’s contents. These commands only read the report.

If the folder contains no files, Terminal may display an error or produce no useful output. In that case, the report may have been stored elsewhere, removed automatically, or not generated for that event.

Find reports for a particular app

Use grep to search filenames. For example:

ls -lt ~/Library/Logs/DiagnosticReports | grep -i "exampleapp"

Replace exampleapp with part or all of the app’s name.

To search the contents of reports instead:

grep -il "exampleapp" ~/Library/Logs/DiagnosticReports/*

The -i option ignores capitalization, and -l displays matching filenames. This can help when the filename does not clearly identify the app.

Method 3: Check the System-Wide Report Folder

Some reports are stored outside your user account. To list the system-wide DiagnosticReports folder, run:

sudo ls -lt /Library/Logs/DiagnosticReports

Terminal may ask for your Mac login password. When you type it, no characters or dots appear on screen. Press Return after entering the password.

sudo runs the command with administrator privileges. In this example, it only lets you list a folder that may require elevated access. It does not change the reports.

You can open the system-wide folder in Finder with:

open /Library/Logs/DiagnosticReports

If Finder cannot display the contents or asks for permission, use the Terminal listing instead. Do not use sudo with commands that delete or modify files unless you fully understand the consequences.

Understand the Important Parts of a Crash Report

A crash report can be intimidating, but you usually need only a few sections.

Process and date

Near the beginning, look for the process or application name and the date and time of the crash. Confirm that the report belongs to the incident you are investigating.

Exception Type

The Exception Type describes the kind of failure. Common examples include an invalid memory access or an unexpected termination. This field helps developers diagnose the problem, but it usually does not identify a simple fix by itself.

Crashed Thread

The Crashed Thread identifies the thread that triggered the failure. A thread is a path of execution inside an app. This section often includes a stack trace, which is a list of functions active at the time of the crash.

Thread State

The Thread State section contains low-level processor information. It is rarely useful for everyday troubleshooting, but a developer may request it.

Binary Images

The Binary Images section lists the app and libraries loaded when the crash occurred. This can reveal whether a third-party plug-in, extension, or helper component was involved.

macOS and hardware details

Reports often include the macOS version, Mac model, architecture, and app version. Include these details when contacting the app developer because they can help reproduce the problem.

Use a Crash Report to Troubleshoot the App

A report is most useful when combined with what happened immediately before the crash.

  1. Note the app name, version, and crash time.
  2. Check whether the crash occurs during one specific action.
  3. Look for repeated references to the same plug-in, extension, or helper process.
  4. Update the affected app if an update is available.
  5. Check for available macOS updates in System Settings > General > Software Update.
  6. Temporarily disable optional extensions or add-ons if the app supports them.
  7. Test whether the problem occurs in a new document, project, or user account.
  8. Contact the developer if the crash continues and provide the relevant report.

Avoid deleting crash reports as a first troubleshooting step. Removing a report does not fix the underlying problem and can make it unavailable for later support.

If the app repeatedly crashes, follow a broader troubleshooting process in How to Fix an App That Keeps Crashing on a Mac. If the app is unresponsive rather than closing unexpectedly, see How to Fix an App That Is Not Responding on Mac.

Troubleshooting

The command returns no results

A blank result does not necessarily mean that no crash occurred. The event may be outside the selected time range, may not contain the word “crash,” or may have been recorded in a saved report instead.

Try a longer period:

log show --predicate 'eventMessage CONTAINS[c] "crash"' --last 7d

Then check the DiagnosticReports folder:

ls -lt ~/Library/Logs/DiagnosticReports

The DiagnosticReports folder does not exist

Create no folder manually just to force a report. If macOS has not saved a report for your user account, the folder may be absent. Search the unified log or check the system-wide location instead:

ls -lt /Library/Logs/DiagnosticReports

The report is difficult to understand

That is normal. Crash reports are primarily diagnostic data for developers and support technicians. Focus on the app name, time, version, exception type, crashed thread, and any third-party component mentioned repeatedly.

Do not change lines in the report before sending it to support. Save a copy if you need to remove private information from a version you plan to share.

Terminal says “Permission denied”

Try opening your own report folder without sudo:

open ~/Library/Logs/DiagnosticReports

For the system-wide listing, use:

sudo ls -lt /Library/Logs/DiagnosticReports

Only enter your administrator password into the genuine Terminal app. Never provide it to an unknown script or paste commands from an untrusted source.

The app crashes but no report appears

Not every unexpected closure creates a traditional crash report. The app may have quit normally, been terminated by another process, or encountered a problem recorded only in the unified log.

Search for the app name:

log show --predicate 'eventMessage CONTAINS[c] "App Name"' --last 24h

Replace App Name with the name of the affected app. You can also check whether the app displays its own diagnostic or recovery information.

Frequently Asked Questions

Where are Mac app crash logs stored?

User-level reports are commonly stored in:

~/Library/Logs/DiagnosticReports

System-level reports may be stored in:

/Library/Logs/DiagnosticReports

The tilde (~) represents your home folder.

Can I view crash logs without Terminal?

Yes. Open Console from Applications > Utilities, then look for crash reports or diagnostic information. Finder can also open the DiagnosticReports folders. Terminal is useful when you need to filter results, search a time range, or export text.

Should I delete old crash reports?

Usually, no. They are useful for troubleshooting and normally occupy little space. Deleting them does not prevent future crashes. If you choose to remove files, make sure you are deleting only old reports and not other diagnostic data. Deletion is permanent unless you have a backup.

Are crash logs proof that an app is defective?

Not necessarily. A crash may result from the app itself, a plug-in, corrupted data, an operating-system issue, insufficient resources, or an interaction with another component. The report provides clues rather than a guaranteed diagnosis.

Can I send a crash report to the app developer?

Yes, and developers often find them useful. Before sending one, review it for usernames, file paths, document names, or other private information. Include what you were doing, when the crash occurred, the app version, and whether the problem happens repeatedly.

Final Thoughts

Terminal provides two practical ways to inspect Mac app crashes: search recent events with log show or open saved reports in ~/Library/Logs/DiagnosticReports. Start with the report’s app name, timestamp, and version, then use repeated crash patterns to guide updates, extension checks, or a support request.