Where Does TeamViewer Store Logs and Connection History?
TeamViewer logs, connection lists and ID storage on desktop, and the timezone trap in timestamps.
Last updated
TeamViewer splits logs by edition. Full and Host write the verbose log plus Connections_incoming.txt under Program Files; QuickSupport writes to %APPDATA%\TeamViewer instead. Outgoing history and the partner dropdown live as connections.txt and MRU files in Roaming. Settings and the ClientID sit in the registry (HKCU and HKLM TeamViewer keys).
Two details bite: incoming lists record successful sessions only (attempts need the full log), and their timestamps are UTC while the verbose log uses local time. The in app shortcut is Extras, Open Log Files on Windows and Help, Open log files on Mac. Linux has no collector UI; ziplog bundles everything for support.
Where TeamViewer stores this, by platform
C:\Program Files (x86)\TeamViewer\TeamViewer_Logfile.log
Verbose log (version number in the real name) plus Connections_incoming.txt beside it. QuickSupport logs in %APPDATA%\TeamViewer. Outgoing connections.txt and MRU history in Roaming. Settings and ClientID in HKCU/HKLM Software\TeamViewer.
~/Library/Logs/TeamViewer/
Logfile plus Connections.txt for all editions (Help, Open log files). ClientID and prefs in /Library/Preferences/com.teamviewer.teamviewer.preferences.plist; admin rights needed to read some paths.
~/.config/teamviewer/client.conf
Per user config (stop teamviewerd before editing); system wide in /etc/teamviewer<version>/global.conf. Bundle logs for support with sudo teamviewer ziplog.
Frequently asked questions
Where is the list of who connected to my TeamViewer?
Connections_incoming.txt next to the main log records successful incoming sessions with ID, name and times. Failed attempts never appear there; dig through the verbose Logfile.log instead.
Why do TeamViewer timestamps disagree between files?
Connections_incoming.txt stamps UTC while the verbose log stamps local time. Convert before correlating, or one session looks like two events an ocean apart.
Notice an outdated path? Let us know.