Normalized FFMI calculator

Coaches, sports-science apps, and research notebooks get both the scientific index and the height-normalized band in one deterministic JSON response. The path is pure arithmetic with no network and no random seed, so free browser checks and prepaid API clients never disagree. Missing lean mass or height, non-positive values, and heights outside a safe adult window fail with invalid_input and are not charged.

What normalized FFMI measures and which inputs you need

Raw fat-free mass index divides lean mass by height in meters squared and therefore still embeds a stature bias: shorter athletes tend to score higher and taller athletes lower for the same lean tissue density. Height-normalized FFMI corrects that bias with a linear adjustment toward a fixed reference stature of one point eight meters, using the widely cited coefficient six point one. Lean mass must already be known from DEXA, hydrostatic weighing, a quality BIA device, skinfolds, or another composition method you trust; this calculator does not estimate composition from weight and body-fat percent. Heights below zero point three meters or above three meters are rejected as outside a safe isolate window for adult standing stature. The engine first forms FFMI as lean_mass_kg divided by height_m squared, then adds six point one times one point eight minus height_m, and returns both figures in kilograms per square meter. Send lean_mass as a positive finite number in kilograms; aliases lean_mass_kg, fat_free_mass, fat_free_mass_kg, ffm, and lbm are accepted when your payload already uses those names. Send height as a positive finite number in meters; aliases height_m, stature, and stature_m are accepted, and height_cm is accepted when you prefer centimeters—the engine divides by one hundred. If lean mass or height is missing, empty, non-finite, or non-positive, the request fails with invalid_input naming the field. Identical inputs always yield identical JSON because the algorithm never touches the network, a model, a clock, or a random generator.

Reading the response fields and common pitfalls

Remember that lean mass quality dominates the result—garbage composition input produces a polished but meaningless index. Extremely large lean-mass values above the published isolate safety ceiling are also rejected. Keep expectations clinical: this is an educational and planning estimate, not a diagnostic medical device, and users with atypical body composition or medical conditions should follow professional advice rather than any single index alone. On success the response echoes lean_mass_kg and height_m, then reports ffmi, normalized_ffmi, and height_adjustment. The height_adjustment field is exactly six point one times one point eight minus height_m so UIs can show the correction term next to the raw index without re-deriving it. The reference_height_m field is always one point eight and coefficient is always six point one so clients can document the formula without hard-coding constants. The unit field is always kg/m², formula restates the full normalized expression, and method is always ffmi_normalized so downstream code can branch without sniffing shapes. Use ffmi when you want the raw scientific index for research papers; use normalized_ffmi when your coaching literature, contest prep notes, or team dashboard quotes the height-adjusted band. Do not confuse this endpoint with BMI, BMI Prime, BMR, or the weight-and-body-fat FFMI path that derives lean mass itself: those answer different questions and live on other capabilities.

API usage, pricing, coaching workflows, and practical limits

Call the free in-browser normalized FFMI calculator for quick checks, lecture demos, and client education without installing a sports-science spreadsheet. Keep requests small, document the six-point-one coefficient for your users, and you get reproducible height-adjusted lean-mass scores without standing up a full sports-science stack of your own. Send a JSON body with required lean_mass and height (or their aliases). Use the prepaid API when a fitness SaaS, team performance platform, telehealth intake form, or research notebook needs a stable contract under KIT balance at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. Pair this endpoint with a composition workflow that already stores fat-free mass—DEXA exports, BIA device APIs, or skinfold spreadsheets—then chart normalized_ffmi across a season without re-deriving lean mass from scale weight each time. Prefer kilogram lean mass and meter height that match the published formula; if your UI collects pounds or centimeters, convert or use height_cm before calling. Authors shipping SDKs can map ffmi and normalized_ffmi directly into dashboards and export CSV columns labeled lean mass index and height-adjusted FFMI—the same numbers coaches write by hand when they apply the Kouri-style correction on paper. When stature equals the one-point-eight meter reference, height_adjustment is zero and normalized_ffmi equals raw ffmi, which is a useful smoke check for integration tests.