Heart Rate Spikes During Strength Training Not Detected – Strong Filtering in Strength Trainer Mode?

Hi everyone,

I recorded my training sessions using the Strength Trainer mode on Whoop, with the band worn on my biceps exactly at the spot recommended by Whoop Support and shown in their official placement graphic. At the same time, I tracked my heart rate with an Apple Watch on the same arm and synchronized the data for direct comparison.

During training, there are frequent, sudden, and short spikes in heart rate, which are typical for intense phases of strength workouts. The Apple Watch clearly displays these peaks. However, the Whoop band either does not show these short-term spikes at all or only displays them in a very dampened way. Instead, the Whoop heart rate reading often remains at a lower value or reacts with a noticeable delay.

According to Whoop’s own documentation, the band measures heart rate 52 times per second, so technically it should be impossible for the device to miss these sudden increases in heart rate. The only plausible explanation is that the raw data is being heavily smoothed or filtered, so that short, training-relevant peaks are suppressed. I specifically used the Strength Trainer mode, hoping that filtering would be minimized in this setting.

Because of this filtering, Whoop registers less time in higher heart rate zones, especially zone 3 and zone 4, compared to the Apple Watch. This could negatively affect the strain score and even the Whoop Age, since the actual training intensity is underestimated.

Especially in strength training and interval workouts, it’s crucial that short-term heart rate spikes are accurately detected to realistically reflect training intensity and load. The current filtering means that these peaks are not recognized, and the actual training intensity is underestimated. This issue has occurred with both my Whoop 4.0, WHOOP 5.0 (which was declared defective and replaced), and the replacement device, so a hardware defect can be ruled out. It seems to be a systematic issue with Whoop’s data processing.

A direct comparison of the time series, see attached plot, shows that the Apple Watch correctly displays the peaks, while the Whoop band does not. I’ve also found numerous reports from other users in this forum describing exactly the same issue, during intense strength training, Whoop fails to display heart rate spikes, while other devices do. This appears to be a widespread, systematic problem.

Is it possible to reduce or disable the heart rate data filtering, especially in Strength Trainer mode? Are there any plans to adjust the algorithms for strength training? Has anyone found a workaround or received feedback from support?

I want to emphasize that I’m generally very happy with Whoop, it motivates me to train more and pay attention to my sleep. That’s why this issue is so frustrating for me, it impacts my training experience and sometimes makes me question whether I want to continue using Whoop. I’m convinced that this problem could be solved relatively easily, especially in Strength Trainer mode, by reducing or disabling the filtering. I would really appreciate it if you could prioritize this topic so that Whoop can provide the best possible support for strength athletes and interval training.

5 Likes

Exact same issue and frustration. Upgraded to MG hoping it would accurately capture strength training HR, never does. Extremely frustrating bc the new features we are paying for rely on accurately accounting for the strain we are producing and when using the strength training mode, which accounts for 90% or more of my physical activity, it is not being accurately captured.

Likely will not renew if this issue is not addressed…

3 Likes

Hi everyone,

I conducted a detailed analysis today comparing WHOOP vs Apple Watch heart rate data across three consecutive training phases:

1. Cardio (Crosstrainer) - 17:49-17:54:

  • Correlation: 0.985 (EXCELLENT AGREEMENT)
  • WHOOP measures only +0.1 bpm higher than Apple Watch
  • Maximum deviation: only 9 bpm
  • Both devices show practically identical curves

2. Strength Training - 17:57-19:04:

  • Correlation: 0.480 (SIGNIFICANT DISCREPANCIES)
  • WHOOP measures average -9.6 bpm lower than Apple Watch
  • Maximum deviation: up to 51 bpm
  • Measurements only partially agree
  • I specifically used the Strength Trainer mode, hoping that filtering would be minimized in this setting.

3. Cycling - 19:07-19:21:

  • Correlation: 0.915 (GOOD AGREEMENT)
  • WHOOP measures only -0.9 bpm lower than Apple Watch
  • Maximum deviation: 21 bpm
  • Both devices show similar curves

The data clearly shows that:

  • WHOOP works excellently for cardio and cycling activities
  • There are systematic issues specifically during strength training
  • The problem is NOT related to device placement (same placement for all activities)
  • The discrepancies are significant enough to affect strain calculation and heartzone time

During strength training, WHOOP consistently underreports heart rate by an average of 9.6 bpm, with peaks up to 51 bpm lower than Apple Watch. This means:

  • Strain calculation is significantly underestimated
  • Time in higher heart rate zones is underreported
  • Training intensity appears lower than actual

Because of this filtering, WHOOP registers less time in higher heart rate zones, especially zone 3 and zone 4, compared to the Apple Watch. This could negatively affect the strain score and even the WHOOP Age, since the actual training intensity is underestimated.

Especially in strength training and interval workouts, it’s crucial that short-term heart rate spikes are accurately detected to realistically reflect training intensity and load. The current filtering means that these peaks are not recognized, and the actual training intensity is underestimated.

TECHNICAL DETAILS

  • WHOOP placement: 1 finger width above wrist bone, snug fit
  • Same placement used for all activities
  • Data recorded continuously during the same session
  • Apple Watch used as reference (known for accurate HR monitoring)

A direct comparison of the time series shows that the Apple Watch correctly displays the peaks, while the WHOOP band does not. I’ve also found numerous reports from other users in this forum describing exactly the same issue - during intense strength training, WHOOP fails to display heart rate spikes, while other devices do. This appears to be a widespread, systematic problem.

QUESTIONS FOR THE COMMUNITY

  1. Has anyone else experienced similar issues specifically during strength training?
  2. Are there any known workarounds or settings adjustments?
  3. Has WHOOP acknowledged this as a known issue?
  4. Is it possible to reduce or disable the heart rate data filtering, especially in Strength Trainer mode?
  5. Are there any plans to adjust the algorithms for strength training?

I’ve contacted WHOOP support with this data, but wanted to share with the community to see if others have similar experiences. The fact that cardio and cycling show excellent correlation suggests this might be a specific algorithm issue with strength training data processing.

Would love to hear from others who might have done similar comparisons!

6 Likes

Hi everyone,

I wanted to provide an update on my ongoing analysis of WHOOP vs Apple Watch heart rate measurements during strength training. After conducting additional systematic tests on August 2nd and 3rd, 2025, I can now confirm with even more data that there is indeed a systematic filtering issue specifically during strength training activities.

Latest Technical Findings (August 3rd, 2025):

Overall Data Analysis:

  • Total data points: 1,021 measurements
  • Correlation between devices: 0.851
  • Maximum deviation: 49 BPM difference between WHOOP and Apple Watch
  • Average deviation: -1.52 BPM (WHOOP consistently lower)

Activity-Specific Breakdown:

  • Strength Training (Weightlifting): 960 data points, correlation 0.847, average deviation -1.55 BPM
  • Cardio Training (Cross Trainer): 49 data points, correlation 0.976, average deviation -0.49 BPM

Most Concerning Discovery - Training Phase Analysis:
The most significant finding is what happens during different phases of my training:

  • Beginning Phase (first 20%): Correlation 0.929, average deviation -0.51 BPM
  • Middle Phase (60%): Correlation 0.901, average deviation -0.74 BPM
  • End Phase (last 20%): Correlation drops to 0.579, average deviation increases to -4.85 BPM

What This Means in Simple Terms:
The problem becomes dramatically worse as my training intensity increases. During the final phase of my workout, when my heart rate reaches 160-170 BPM during intense strength training, WHOOP “smooths” these peaks and shows significantly lower values - sometimes up to 49 BPM less than what the Apple Watch measures.

This is particularly problematic because:

  1. WHOOP misses the most important moments of my training - the intense phases where I’m pushing my limits
  2. These missed peaks are crucial for accurate training assessment and recovery calculation
  3. If WHOOP doesn’t recognize these spikes, it cannot properly evaluate how intense my training actually was

Why This Confirms a Systematic Issue:
The fact that measurements work perfectly during cardio activities (cross trainer, cycling) proves that the hardware and placement are correct. The problem only occurs during strength training, indicating that WHOOP uses specific filters or algorithms that don’t work properly for strength training activities.

Next Steps:
I have shared this comprehensive data analysis with WHOOP support and requested contact with their technical development team. I’m willing to provide additional data or conduct further tests to help resolve this issue.

The complete analyses and graphs are available for anyone interested in the technical details.

Has anyone else experienced similar issues during strength training? I’d be interested in comparing notes and potentially building a case for WHOOP to address this systematically.

August 3rd, 2025

4 Likes

August 2nd, 2025

2 Likes

I have consistently had the exact same issue; first with the 4.0 and now with the MG, of during strength training the whoop is dramatically different in HR than my Apple Watch. I do not have any of the fancy charts but it’s happening. And it is extremely frustrating bc all of the extra features rely on accurate hr zones and times and it’s not being captured. Hopefully we can get this figured out.

2 Likes

At first, I was told that we would look into the problem together and that I would be contacted by the relevant department as soon as possible. According to WHOOP Support, my analyses and diagrams were forwarded to the responsible department, and an internal bug report was created.

After a few days, I sent another analysis and asked the support team when I would be contacted by the department. I found the reply somewhat harsh and admonishing in tone. In addition, I was informed that WHOOP would not be reaching out in this open case and would not be keeping me updated. The case would be handled in the background without any further direct contact. I was also advised not to make any further reports on the matter, as additional inquiries would not speed up the process.

2 Likes

Also have an issue where whoop just drops my heart rate down immensely. Also have it on snuggly, maybe too snug, one finger width from my wrist bone. I have fat fingers, so I know it’s far enough away. I had the issue with the 4.0 and now the 5.0. One would think for the price of the device it could do the most basic function of health monitors. I’ve topped out over my max heart rate a few times and had my machine emergency stop when the whoop catches up. Thinking I’m doing 150 bpm and I’m almost at 200 bpm. This needs to be fixed before someone gets hurt

2 Likes

You would think that releasing a feature - Pace of Aging - that literally incentivizes the wearer to 1) increase time in higher HR zones and 2) increase steps, Whoop would give more attention to ensuring that these data measurements are accurate instead of wildly off base.

4 Likes