Zwift riders are losing intensity minutes on Garmin Connect because of a broken integration between Zwift and Garmin devices that started around December 20, 2024. When you complete a cycling workout on Zwift and sync it to Garmin Connect, your activity shows up—but Garmin doesn’t award the intensity minutes you earned during that hard effort. A rider might complete a 90-minute Zwift race at threshold power, sync the file to Garmin, and see zero intensity minutes credited, despite maintaining high heart rate zones for nearly an hour. This is not a Zwift problem or a Garmin device problem in isolation; it’s a problem with how these two platforms talk to each other.
The root cause is architectural: Garmin calculates intensity minutes on the device itself, not from imported activity data. When you wear a Garmin watch and record a workout directly on that device, the watch continuously measures your heart rate and power data in real-time, then calculates which minutes qualify as moderate intensity or higher. But when an activity comes from Zwift—even though it contains all the performance metrics—Garmin’s system doesn’t extract or process those metrics to generate intensity minutes. This is by design, not by accident, which means the workaround requires changing how you record your rides.
Table of Contents
- When Did Zwift Stop Syncing Intensity Minutes to Garmin?
- The Technical Reality: How Garmin Actually Calculates Intensity Minutes
- Who Is Actually Affected by the Missing Intensity Minutes?
- Three Verified Workarounds That Currently Work
- The Real Cost of These Workarounds
- Why Zwift Runners Don’t Face This Problem
- The Current Status and What Might Change
- Conclusion
When Did Zwift Stop Syncing Intensity Minutes to Garmin?
The issue emerged in late December 2024 when Zwift users with Garmin devices suddenly noticed their cycling activities no longer populated intensity minutes in Garmin Connect. Running activities in Zwift continued to sync intensity minutes perfectly, which made the cycling-specific failure even more frustrating. For cyclists who rely on Garmin Connect to track their weekly intensity minutes (a key metric for training balance and recovery), this meant their hard efforts on Zwift started becoming invisible to their fitness tracking ecosystem.
The timing matters because it rules out simple explanations. Zwift had been syncing intensity minutes to Garmin for years before December 2024. The sudden cutoff suggests a backend change, API modification, or data format update that broke the integration. However, both Zwift and Garmin have been relatively quiet about the root cause, leaving riders to piece together what happened from forum posts and user experiments.
The Technical Reality: How Garmin Actually Calculates Intensity Minutes
Intensity minutes aren’t calculated by apps or synced from servers—they’re generated on your Garmin device itself. When you start a recording on your Garmin watch, the device begins collecting heart rate data (or power data if you’re using a power meter) at regular intervals. Garmin’s algorithm then determines which minutes exceeded your lactate threshold heart rate or threshold power, counting those as moderate intensity or higher. The calculation is deterministic and device-specific.
Here’s the critical limitation: Garmin’s official architecture does not import and reprocess intensity minute calculations from third-party training data. Even if Zwift sends Garmin Connect a complete record of your power output and heart rate for every second of your ride, Garmin Connect’s servers don’t use that data to retroactively calculate intensity minutes. Intensity minutes exist only on activities that were actively recorded by a Garmin device. Zwift activities imported into Garmin Connect are treated as external data, not native device recordings, which means Garmin’s intensity minute algorithm never processes them.
Who Is Actually Affected by the Missing Intensity Minutes?
This issue is narrow in scope but hits hard for a specific group: Zwift cyclists who use Garmin devices to track their weekly intensity minutes. If you ride Zwift on a stationary bike but don’t wear a Garmin watch or chest strap, you’re not affected—you probably weren’t getting intensity minutes from Zwift in the first place. If you run on Zwift, you’re not affected at all; running activities continue to sync properly.
The impact is particularly painful for cyclists following training plans that depend on Garmin’s weekly intensity minute targets. You might complete a full week of structured Zwift workouts, hit your training zones, and still fall short of Garmin’s recommended intensity minutes because none of those cycling activities were recorded by your Garmin device. Meanwhile, a 45-minute run you did outside gets recorded on your Garmin watch and contributes to your intensity minute total. This creates a frustrating asymmetry where one training platform contributes to your metrics and another doesn’t.
Three Verified Workarounds That Currently Work
The first and most reliable workaround is dual recording: start an activity on your Garmin watch simultaneously with your Zwift workout. When your watch records the activity, it collects your heart rate data in real-time and calculates intensity minutes independently. Meanwhile, Zwift records your performance data separately. When you stop the watch, the activity syncs to Garmin Connect with full intensity minute credit. This requires discipline—you can’t forget to start the watch when you jump on the bike—but it works consistently. The second workaround is using HR Broadcast mode on your Garmin watch.
Some users report that enabling HR Broadcast (which broadcasts your heart rate to nearby ANT+ devices or Bluetooth devices) and starting an activity on the watch before or during your Zwift session generates proper intensity minutes. This is less tested and reliable than dual recording, and your results may vary depending on your specific Garmin model and Zwift setup. The third workaround uses a chest strap connected to your Garmin watch. Connect an ANT+ or Bluetooth chest strap to your watch, start an activity on the watch, and begin your Zwift ride. The watch collects heart rate data from the chest strap and calculates intensity minutes as normal. This approach is particularly useful if you prefer not to wear a watch while riding, though chest straps have their own comfort tradeoffs during indoor cycling.
The Real Cost of These Workarounds
Dual recording is reliable but creates data duplication. You’ll have the same workout logged twice: once from Zwift with power and performance metrics, and once from Garmin with heart rate and intensity minutes. Reconciling or deleting duplicate activities becomes a weekly chore, and some athletes find it messy to have redundant records cluttering their training log.
The HR Broadcast and chest strap approaches come with their own limitations. HR Broadcast works inconsistently across different Garmin watch models and firmware versions, and support forums show mixed results. Chest straps are accurate but uncomfortable for many cyclists, especially during 60+ minute efforts, and they add cost if you don’t already own one. The core problem remains: you’re essentially working around the architectural limitation by forcing your Garmin watch to record the activity natively rather than relying on Zwift-to-Garmin data transfer.
Why Zwift Runners Don’t Face This Problem
Zwift running activities continue to sync intensity minutes to Garmin Connect without interruption. The difference isn’t in Zwift’s code; it’s in how running activities are processed differently by the integration. Runners wearing Garmin watches often have the watch actively recording during their Zwift run anyway, which means intensity minutes are generated by the device-level recording, not by data imported from Zwift.
Even when runners sync Zwift-only activities, the intensity minute transfer appears to work more reliably, though the exact technical reason remains opaque. This asymmetry suggests that either Garmin’s systems handle running activity data differently than cycling data, or that the integration was broken more severely for cycling on the backend. Regardless, it means cyclists are disproportionately affected while runners can rely on Zwift for full metric syncing. For training programs that mix running and cycling, this creates an awkward situation where your running efforts register fully and your cycling efforts disappear.
The Current Status and What Might Change
As of early 2025, the integration remains broken, and neither Zwift nor Garmin has issued an official fix or clear explanation. Community forums show ongoing reports of the issue, and some users have simply abandoned the idea of getting intensity minutes from Zwift cycling, instead focusing on dual recording or using other metrics to track training stress.
There’s a possibility that Garmin or Zwift could update their systems to restore the intensity minute transfer, but that would require Garmin to change its architectural approach to processing third-party activity data. Until that happens, the workarounds outlined above remain your only options. For now, dual recording is the most pragmatic solution if intensity minutes matter to your training system.
Conclusion
Zwift riders lose intensity minutes in Garmin Connect because of a fundamental mismatch: Zwift sends activity data, but Garmin only counts intensity minutes from activities actively recorded by its own devices. The integration broke around December 2024 for cycling activities (while running remains unaffected), and there’s no official fix on the horizon. Your best option is to start your Garmin watch simultaneously with your Zwift rides to ensure your hard efforts register as intensity minutes.
If you’re already invested in Garmin’s training ecosystem and you care about hitting weekly intensity minute targets, it’s worth adopting dual recording or a chest strap setup rather than hoping the integration fixes itself. Otherwise, consider whether intensity minutes are actually critical to your training, or if power metrics and heart rate zones from Zwift alone provide sufficient feedback. Either way, the workarounds work—they just require a small shift in your recording habit.
