Fitbit vs MFP calorie discrepancy

Andiebeanluvsu
Andiebeanluvsu Posts: 105 Member
edited December 2024 in Social Groups

Can someone please explain this to me?? I have a Fitbit one. My MFP calories are set to not very active (apparently sedentary isn't an option any more?).

Why is there such a big difference between the two?? From the looks of it, I basically have to walk a 5k daily with my Fitbit just to match what MFP says I burn just by sitting on my behind all day.

j7byfnqkad7a.png

Replies

  • NancyN795
    NancyN795 Posts: 1,134 Member
    When I look on the website under Settings -> Update diet/fitness profile, it still shows Sedentary as an option, but I do see in my phone app that it is now labeled "Not Very Active" there.

    Bottom line... it looks like your Fitbit says you're not even as active as a typical sedentary person. How many steps are you taking a day? Is your stride calibrated in Fitbit? Are all your stats correct in both programs? Are you doing any exercise (swimming, weight lifting, etc.) that your Fitbit doesn't track that should be logged manually?

    (You should probably enable negative adjustments if your Fitbit is giving an accurate calorie burn. Otherwise, you're not going to achieve the calorie deficit you've selected.)
  • heybales
    heybales Posts: 18,842 Member
    Interesting info - no Sedentary.

    Makes sense because the MFP levels were never the same as the standard TDEE tables and their names - they should have used something different from the start.

    So is the new order:
    Not Active
    Not Very Active
    Active
    Very Active

    ;-)
  • heybales
    heybales Posts: 18,842 Member
    To OP - for MFP setting of Sedentary, it seemed most folks had to get over about 4000 steps to move above Sedentary and get positive adjustment.

    I never heard much on how few steps you had to get to start getting negative.

    Curious how few steps you are getting?
    Even though the new name is Not Very Active, which could have different value than Sedentary too.
This discussion has been closed.