Wireless Diagnostics can analyse your Mac’s Wi-Fi connection and create a report for support. Use it to preserve information about a specific problem before changing several settings. Generating a diagnostic report is a different task from deleting network configuration, resetting a router or proving that an ISP is at fault.
This workflow is useful when you can describe an incident but cannot explain it: a recurring disconnection, a location-dependent problem or an application that becomes unusable while the Wi-Fi icon remains present. For a general sequence of checks, use the Mac internet troubleshooting guide; here the goal is a useful diagnostic record.
Prepare a short incident note
Record the date, approximate time and timezone, the application affected and the network you intended to use. Describe the visible behaviour: “video froze while audio continued” is more useful than “bad Wi-Fi.” Note whether you moved rooms, resumed the Mac or connected a dock around that time.
Write down what you did not observe too. If you do not know whether other devices failed, leave that question open. A report becomes harder to interpret when remembered possibilities are written as facts. Avoid rebooting everything before collecting the information you wanted to preserve, unless immediate recovery is more important.
Open Apple’s diagnostic tool
Follow Apple’s Wireless Diagnostics instructions for the macOS version selected in its guide. Try to join the affected network, hold Option, open the Wi-Fi status menu and choose Open Wireless Diagnostics. Follow the onscreen analysis and review the information buttons in the summary.
Apple documents a compressed report in /var/tmp, with a name beginning WirelessDiagnostics and ending .tar.gz. Finder’s Go → Go to Folder can open that location. Use the report’s actual name and creation time; do not assume that an older archive in the same folder belongs to today’s run.
If the menu or workflow differs, check the guide for your installed release. On a managed Mac, use the organisation’s support process if diagnostics are restricted. Do not install a replacement “Wi-Fi repair” utility merely because the built-in menu does not look like an online screenshot.
Read the summary before opening every log
Start with the tool’s summary and the problem you recorded. Save the wording of a recommendation without upgrading it into a certainty. A recommendation is a lead for further investigation, not proof that replacing a router or buying a mesh system will solve the complaint.
The archive can be useful to someone familiar with the relevant software and network. This guide does not assign meanings to undocumented log codes or promise that a particular file contains the answer. If you cannot confidently explain an entry, preserve it with context and ask the support recipient what they need.
Apple’s separate Mac Wi-Fi connection guidance distinguishes joining Wi-Fi from reaching internet services and points to built-in diagnostic tools. That distinction helps when the summary and the symptom seem inconsistent: a wireless connection and a working remote application are not the same observation.
Choose a comparison that preserves the question
If the complaint follows a location, compare the same Mac and normal activity in another room. Keep the network and other conditions recorded. The Wi-Fi dead-zone guide offers a wider coverage investigation if that pattern repeats.
If the complaint affects one application, first compare another ordinary task at the same time. Do not add a large bandwidth test while attempting to observe a fragile call. If you later run a browser internet speed test, label its time and treat it as separate evidence to its own endpoints.
If another device remains usable, note that comparison without declaring the Mac defective. The two devices may be using different interfaces or routes. If several devices fail together, keep that fact in the incident report; it can change the most useful next question.
Build a support package you would want to receive
- Include the short incident note and the Mac model/macOS version.
- Identify the report by creation time and filename so it can be matched to the complaint.
- State the diagnostic summary separately from your own interpretation.
- Describe one controlled comparison, including what stayed the same and what changed.
- Ask whether the recipient needs the full archive or only selected information before sending it.
Review screenshots and files for personal or network information. Share them through the intended private support channel rather than posting a complete archive publicly. Do not remove an entry from your private original merely because it looks confusing; send a separate explanation or a carefully redacted copy when appropriate.
What counts as progress?
The tool does not need to produce a dramatic verdict to be useful. Establishing that an incident happened at a known time, that the Mac remained associated, or that the pattern changes in one location can make the next investigation much smaller.
Keep the report alongside the outcome of any supported change you later make. If the problem returns, note the new time rather than reusing the old archive as current evidence. A clear sequence of observations is more useful than repeated resets with no record of the conditions between them.