Find out what happened
on your ride.
Drop in a Zwift log file to explore graphics performance, ANT+ receive failures, Bluetooth events and network stability. No login, no uploads, no fuss.
Log.txt hereDocuments/Zwift/LogsSession analysis
How smoothly was Zwift running?
The blue line shows frames per second (FPS) over time. Higher readings mean smoother graphics; dips mean fewer frames were drawn.
This graph does not show rider crowding. It measures graphics performance. It cannot tell us whether nearby riders caused a dip.
Red dots and dashed lines mark logged network interruptions or ANT+ receive failure bursts. Click a dot for details. An event happening near a dip does not establish its cause.
What the log suggests
Evidence-based hints, not automatic root-cause claims.
System and session
Configuration recorded by Zwift.
Diagnostic timeline
Selected explicit log events, arranged chronologically. Repeated ANT+ failures are condensed into bursts.