Sending meeting or webinar problem report and client logs
If you are encountering an issue while in a Zoom meeting or webinar, or while using the Zoom application to chat or schedule a meeting, you can send a problem report and logs to Zoom Support. These problem reports and logs help our Zoom Support team troubleshoot the issue and arrive at a resolution. If you do not already have a request open with Zoom, we recommend contacting Zoom Support first before sending the report.
If a more detailed analysis is needed, Zoom Support may provide a special troubleshooting version that will need to be installed. Once installed, replicate the issue, and retrieve the logs using the directions below.
If you are having issues with other Zoom products, please refer to the dedicated article for submitting problem reports for Zoom Phone or Zoom Contact Center.
Note: This article covers information on how to send a problem report from the Zoom desktop client and mobile app. If you experience an issue while using the Zoom web client, you can send a problem report by contacting Zoom Support.
Requirements for sending a problem report and client logs to Zoom Support
How to send a problem report from the Zoom desktop client
How to send a problem report from the Zoom mobile app
Recover crash log for mobile app
You can manually access historical crash logs from mobile devices to submit to Zoom Support for assistance. This method is intended for specific event log retrieval and these logs can also be sent through a problem report if present within the device.
How to send a problem report from the Zoom Web App
How to retrieve logs from the troubleshooting version
Note: For these steps, you need to have a support request open, and have been given a troubleshooting version of the Zoom app from the Zoom Support team.
Desktop client advanced troubleshooting
By default, logs submitted through a problem report are not written to disk, and are held in temporary memory banks, overwritten with new data regularly. This can result in events being overwritten before being submitted in a problem report.
You can enable memory log collection within a client, which writes persistent data files to the machine’s storage, and eliminates concerns of data or core events being overwritten. There is no substantial difference between the logs generated with memory logs enabled and a problem report. However, logging should be disabled after the log files are sent to Zoom Support for review to save disk space and maintain machine performance.
Zoom memory logs generated through this process are not encrypted at the file level. When transporting client logs to Zoom Support for troubleshooting, secure transport methods for data security are highly recommended.
Note: Zoom recommends to always confirm logging is disabled after capturing to maintain machine performance, and transmit compressed logs using secure connections.
Enable desktop client memory log
Additional data that may be included in the crash report
When sending problem report and client logs, the crash data may unintentionally include memory dumps such as the following:
Current settings information, such as where files are saved, shortcut key settings, and personal images
Currently received chat message, text, image, or video
Network information like downloading activities for images, files, or other online resources
Logs that are not available in normal software versions but are present in ZR VDI versions, which may also include unencrypted data temporarily stored in memory.
Registry and disk information, such as system registry settings, disk space details, and other relevant files
User input, like search keywords, typed messages, or other text entered by the user
Binary file dump, which is a complete snapshot of data and is approximately 100–500MB in size
Screenshots of shared or recorded documents and whiteboard pages
Meeting information like audio and video data, conference ID, member list, meeting chat, invite link, and passcode
Profile details
User's meeting virtual background and meeting name