Cardio Load
Whole-body aerobic/systemic demand
Anfold estimates calories burned from activity-specific MET values (the Compendium of Physical Activities), adjusted for how hard you went and the terrain. Strength sessions count working sets and rest separately. Training load comes out as three numbers: Cardio Load for the whole body, Muscle Load Units (MLU) for each muscle, and Total Load, which blends the two.
These are estimates, not measurements. MLU and the load scores are Anfold’s own units, so they are most useful for comparing your own days and weeks.
Whole-body aerobic/systemic demand
Anfold’s own per-muscle unit, about one hard set’s worth of load on a muscle, so running and lifting add up on the same scale
Blended recovery demand that weights systemic and muscular stress (leaning more on cardio for short-term recovery)
These metrics are designed for daily understanding and week-over-week comparisons. They are unitless points derived from duration, intensity and modality.
Anfold separates the calculation for each kind of training from the numbers you see. Strength, endurance and mobility each use their own math, then convert into one per-muscle unit (MLU), so a run and a leg day add up on the same scale.
Total Load blends whole-body cardio stress with the average load across your muscles. It leans toward cardio, which drives short-term recovery more.
Example: a 5 km run, for someone who weighs 78 kg. MET value and multipliers as Anfold uses them.
Separate formulas for strength, endurance and mobility, because each one loads the body differently.
Each kind of training converts its load into Muscle Load Units with its own conversion factor, so a run and a leg day add up on the same scale.
Weekly guidance per muscle (maintain, build, or a short harder block) plus an overall Total Load to help you plan recovery.
Separate scales avoid forcing endurance, strength and mobility into one formula. Each uses a method suited to how it loads the body, then converts to MLU so different kinds of training can be added together.
Targets are deliberately broad. They change with what you’re aiming for (maintain or build) and don’t assume elite training volumes.
When you log an exercise (text or structured entry), Anfold:
AI-generated muscle activations are normalized and validated against expected patterns, and physiologically implausible outputs are flagged.
Fallback activation profiles cover common modalities when AI context is insufficient, ensuring consistent per-muscle allocation across entries.
Anfold estimates the calories each activity burns. It starts from activity-specific MET values and adjusts them for intensity, terrain and exercise type.
Strength training counts working sets and rest separately, with a much lower rate for rest. A typical 45-minute session lands around 150–250 kcal, rather than the 350 kcal or more you get by treating the whole session as continuous work. Compound lifts count higher than isolation exercises, and hard sets a little higher than easy ones.
Activity-specific MET values are adjusted by your RPE, terrain (uphill/downhill), and elevation gain for outdoor activities.
Active work (time under tension) uses a higher MET; rest periods use a lower MET. Compounds and accessories are weighted differently. Session averages are capped at realistic values to prevent inflated estimates.
Illustration. Work and rest vary with your sets, reps and rest.
What this captures: heavier sets, more volume, slower tempos, and movements with pronounced lowering phases increase load appropriately; involved muscle groups receive their share.
Intensity estimation supports both loadxreps and reps-only cases for bodyweight. Rep tempo affects time-under-tension; eccentric emphasis increases mechanical stress. Systemic load considers active work only, excluding rest intervals.
Per-muscle distribution uses activation shares (AI or fallback) before conversion to unified MLU for cross-modality stacking.
What this captures: longer and/or harder sessions raise systemic demand; different activities and terrains stress muscles differently.
Intensity comes from your session RPE, mapped to an intensity fraction and clamped to a plausible range, with a bounded intensity curve to prevent blow-ups at maximal effort.
Terrain mechanics and impact/eccentric differences (e.g., uphill vs flat, trail vs road) shift per-muscle stress; longer single sessions accrue diminishing returns to reflect fatigue within a workout.
Muscle-specific adjustments capture that, for example, uphill running stresses hip extensors more than flat terrain.
Terrain changes both numbers: the calories and where the load lands.
The baseline.
Flat: about 350 kcal burned. Glutes 0.52 MLU, Quads 0.50 MLU, Calf Complex 0.50 MLU, Hamstrings 0.31 MLU.
Example: the same 5 km run in 26 minutes at effort 6, for someone who weighs 78 kg. Multipliers as Anfold uses them; elevation gain adds more.
What this captures: meaningful but lighter stimulus appropriate for low-intensity movement, with proper distinction between restorative and active mobility work.
Active vs passive work uses a stability-oriented intensity model suited to gentle exercise. Mobility adds small per-muscle and systemic loads and converts to MLU at lower rates, because gentle work is easy to recover from.
Your perceived effort (sRPE) maps to a sensible intensity range. Weight is required only when it materially affects a calculation (e.g., bodyweight strength).
Heart rate isn’t an input
Anfold doesn’t read heart rate from your entries or from devices. Intensity comes from the effort you describe.
Your sRPE is mapped to an intensity fraction and clamped to a physiologically reasonable range.
User weight is used for bodyweight strength estimates when it materially changes the result; if missing, those estimates are limited rather than guessed.
From your entry
Endurance distribution accounts for impact and eccentric differences across terrains (e.g., uphill vs downhill) so that local muscle stress reflects real-world mechanics.
Strength distribution uses activation shares to split per-set dose across muscles before unifying into MLU. Single-day caps catch outliers and keep weekly tallies realistic.
Where the load lands, per workout
Ran 5k in 26 min
Leg day: squats and lunges
Push-ups and pull-ups
Bouldering, 1 hour
Example workouts. Values are illustrative; the app lists them per muscle.
These are starting points, not prescriptions. If you’re training for something specific (a race, a hypertrophy block), aim higher or lower.
Tap workouts to add them to the week.
Example week. A run and a leg day add up on the same scale.
Anfold’s own guideline, not an established standard.
Weekly guidance is expressed per muscle using broad bands (maintain/build/aggressive). A single-day cap prevents outliers from skewing trends and encourages distribution over “hero” sessions.
Total Load blends systemic and muscular stress to approximate overall recovery demand; it leans toward cardio for near-term fatigue while still accounting for muscle-level stress.
These are the studies and methods the calculations draw on.
How this page is kept current
When the way Anfold calculates something changes, this page changes with it. Spotted something wrong? Write to [email protected].
Note: We avoid brand-specific devices or vendor dependencies; calculations rely on common fields you can enter manually.