# Is it safe to delete crash reports in DiagnosticReports?

Is it safe to delete? · Library and system · Updated 21 November 2026. By Mohit Nippanikar, who makes SiftMac.

## The short answer

- **Yes.** Every file in it is a report macOS wrote after something crashed, hung or ran into trouble. Once you’ve read it, or sent it to whoever needs it, nothing on your Mac uses it.
- **What it costs you:** evidence. If an app keeps crashing and its developer asks for a report, a recent one helps, so keep those until the problem is fixed.
- **Does it come back?** Only when something fails again. A folder that refills quickly is a symptom worth fixing, not just clearing.
- SiftMac’s verdict: Safe

## 1. What it is

When an app or system process crashes, macOS writes down what was running, which part failed and where. Console sorts these reports by kind, and the file extension tells you which kind you have:

- **Crash reports** (`.ips`): an app or process quit unexpectedly.
- **Spin reports** (`.spin`): details of an app or process in trouble, such as one that stopped responding.
- **Diagnostic reports** (`.diag`, `.dpsub`): hardware resources, system response times and similar data.

Apps you run write to your own folder; system processes write to the one in `/Library/Logs`. Each report is named after the program it’s about, followed by the date and time, so the list alone shows what failed and when.

## 2. Where it is

```
~/Library/Logs/DiagnosticReports
/Library/Logs/DiagnosticReports
```

Console is the easy way in: open it from Applications › Utilities and choose Crash Reports, Spin Reports or Diagnostic Reports in the sidebar. Control-click a report and choose Reveal in Finder to find its file.

## 3. How big it gets

Reports are text files, so the folder only grows large when something fails over and over. To check its size, then list the newest reports first:

```
du -sh ~/Library/Logs/DiagnosticReports
ls -lt ~/Library/Logs/DiagnosticReports | head -20
```

Dozens of reports with the same name mean one app or process is crashing again and again.

## 4. How to delete them

1. Open Console and choose Crash Reports, or another kind of report.
2. Select the reports you don’t need and choose File › Move to Trash.
3. Empty the Trash.

Your own reports can also go from Finder, in `~/Library/Logs/DiagnosticReports`. The ones in `/Library/Logs/DiagnosticReports` belong to the system: remove those through Console as an administrator rather than from Terminal.

If an app keeps crashing, update it, and send one of its reports to the developer before deleting the rest. Developers don’t automatically see your crashes: for App Store apps, Apple passes reports on only from people who share analytics with app developers, a setting in System Settings › Privacy & Security › Analytics & Improvements.

## 5. What happens afterwards

- Nothing changes in how your Mac or apps work; reports are a record, not something they run on.
- Console’s lists are shorter, so a new crash stands out.
- New reports appear the next time something fails.
- Reports already shared with Apple or a developer stay with them; deleting your copy doesn’t recall them.

## Questions

### What are .ips files on a Mac?

Crash and diagnostic reports macOS writes when something fails. They’re readable text: open one in Console to see which program crashed and where. Old ones are safe to delete.

### Why does DiagnosticReports keep filling up?

Something is crashing or hanging repeatedly. Sort by date and look at the names: update or remove that app, or update macOS if the name belongs to a system process. Clearing the folder without fixing the cause only makes room for more.

### Should I share crash reports with Apple?

It’s your choice, in System Settings › Privacy & Security › Analytics & Improvements. Sharing helps Apple and app developers fix crashes; deleting reports from your Mac doesn’t change what was already shared.

## How SiftMac handles it

In its Old logs category, your `~/Library/Logs/DiagnosticReports` appears as **Crash reports**, with only reports older than a week picked, so one you just got stays. They’re deleted rather than shelved, and the system’s `/Library/Logs/DiagnosticReports` is left alone.

Download: https://siftmac.com/SiftMac.dmg (scanning is free, and so is the first 2 GB of cleaning).

## Sources

- [Apple: View reports in Console on Mac](https://support.apple.com/guide/console/cnsl664be99a/mac)
- [Apple Developer: Acquiring crash reports and diagnostic logs](https://developer.apple.com/documentation/xcode/acquiring-crash-reports-and-diagnostic-logs)

## Related

- [Can I delete all the log files on my Mac?](https://siftmac.com/safe-to-delete/library-logs)
- [Is it safe to delete ~/Library/Caches on a Mac?](https://siftmac.com/safe-to-delete/library-caches)
- [How to clear System Data on a Mac, safely](https://siftmac.com/guides/system-data-on-mac)
- [How to see what’s taking up space on your Mac](https://siftmac.com/guides/what-is-taking-up-space-on-mac)

Canonical: https://siftmac.com/safe-to-delete/diagnostic-reports
