The Same BMI Can Look Completely Different: Visualizing What kg/m Leaves Out
If you have ever shipped a body-mass-index calculator, you have probably watched a user do this: they enter height and weight, see a single number, and then ask why that number does not match the body they see in the mir
If you have ever shipped a body-mass-index calculator, you have probably watched a user do this: they enter height and weight, see a single number, and then ask why that number does not match the body they see in the mirror β or the body they see on someone else.
The question is not rare, and it is not only asked by developers. In r/beginnerfitness, a poster asked why two people with essentially the same BMI can look βmuscularβ in one case and βonly overweightβ in another, even when neither person trains. In r/loseit, another poster who had already lost a large amount of weight asked why they still looked much bigger than other women at the same BMI. On X, the same comparison shows up in everyday replies: people with a similar BMI write that they look βway bigger,β βso much skinnier,β or βnormal on paper but overweight in the mirror.β The useful engineering question underneath all of this is simple: if your interface only returns kg/mΒ², you have thrown away every measurement that would explain the difference.
This article walks through what BMI actually computes, what a classic 3D-scan comparison showed, which extra ratios you can calculate in a few lines of JavaScript, and how a browser-based 3D body preview should be described so it does not pretend to be a scan.
BMI is a ratio, not a picture
The adult formula is short enough to memorize, which is both its strength and its weakness:
function bmiKgM(weightKg, heightCm) {
const heightM = heightCm / 100;
return weightKg / (heightM * heightM);
}
// 175 cm, 76.6 kg β 25.0
bmiKgM(76.6, 175);
That is the calculation the Centers for Disease Control and Prevention uses for adults 20 and older. CDCβs published categories are:
- underweight: less than 18.5
- healthy weight: 18.5 to less than 25
- overweight: 25 to less than 30
- obesity: 30 or greater, with further class breakdowns at 35 and 40
The same page is careful about what those labels are for. BMI is described as a screening measure. It should be considered with other factors, and it is not a substitute for professional medical advice. CDCβs broader BMI overview puts the limit even more bluntly: a high BMI can indicate high body fatness, but BMI βdoes not diagnose the body fatness or health of an individual.β
If you render that screening number as a big gauge, a red/green badge, or a 3D avatar that snaps to a new βoverweight bodyβ the moment the index crosses 25.0, you are adding meaning the formula does not contain. Two adults who are both 175 cm and 76.6 kg both have a BMI of 25.0. One of them can measure 80 cm at the waist and the other 95 cm. The index cannot tell them apart.
A 3D scan comparison made the gap visible
This is not a new observation, and we do not need a made-up statistic to show it. On 7 July 2015, the New York Times published βSame B.M.I., Very Different Beach Body,β an interactive that used 3D scans from the New York company Body Labs. The Times said the illustrations came from scans of six people who were all 5 feet 9 inches tall and 172 pounds. They therefore all had the same BMI, 25.4, which sits in the overweight screening range. Their scanned bodies still looked very different. The Timesβ short explanation was the one every fitness forum already knows: muscle and bone are denser than fat, so the same mass can occupy a different volume and sit in a different place.
The piece spread quickly into communities that already distrusted a single number. A thread in r/Fitness, β3D Body Scans of 6 adult males - each with identical BMI of 25.4,β circulated the same comparison. Commenters there made a second, more subtle point that still matters if you are building a UI: waist circumference, especially when you correct it for height, carries information that BMI does not. BMI and waist used together are more informative than either one used as a lone badge.
A companion Times piece, βHow Often Is B.M.I. Misleading?,β summarized older National Health and Nutrition Examination Survey data in which CDC had collected both BMI and DXA-derived body-fat percentages for more than 5,000 people. The Times reported a strong relationship between the two, but also disagreement for a substantial minority of adults, including people with overweight BMI and body-fat levels the article treated as normal, and people with βhealthy weightβ BMI and body-fat levels the article treated as excess. I am citing that as a 2015 journalistic summary of then-historical survey data, not as a fresh 2026 CDC statistic. The design lesson does not depend on the exact percentage: BMI and body composition can move together in a population and still disagree for a person standing in front of your form.
Show the measurements BMI cannot see
Once you accept that height and weight are not a body, the next question is which extra inputs are cheap enough to ask for and honest enough to display.
Waist-to-height ratio is the simplest upgrade:
function waistToHeightRatio(waist, height) {
// waist and height must use the same unit (cm and cm, or in and in)
return waist / height;
}
A commonly discussed adult screening boundary is 0.5 β keep waist circumference below half of height. That threshold is the one discussed in Browning, Hsieh and Ashwellβs systematic review of waist-to-height ratio as a screening tool, and it is the public message in NICEβs 2022 news announcement and in later NICE overweight-and-obesity guidance: keep the size of your waist to less than half of your height. Like BMI, this is a screening aid, not a diagnosis.
Waist-to-hip ratio adds distribution context, again from two tape measurements:
function waistToHipRatio(waist, hips) {
return waist / hips;
}
Neither ratio measures visceral fat directly. Neither one tells you whether circumference came from muscle, fat, bone, bloating, or a tape pulled too tight. They simply refuse to pretend that two people with the same height and weight are interchangeable.
The diagram below holds height, weight, and BMI fixed at 175 cm, 76.6 kg, and 25.0 β the same worked example used above β and only changes waist.
At 80 cm the waist-to-height ratio is 0.46, below the 0.5 line. At 88 cm it is 0.50. At 95 cm it is 0.54. A calculator that only prints 25.0 has no way to talk about that difference. A calculator that also prints the waist and the ratio can. A 3D preview that lets you enter the waist can show it, as long as you do not call the picture a scan.
If you want to try this with a live control instead of a static figure, the BMI visualizer on Body Visualizer is built around exactly that experiment: calculate adult BMI from height and weight, then add optional waist, hips, and other measurements and watch the estimated outline change while the BMI number stays put.
A body-fat percentage from BMI is still an estimate
Many product briefs quietly say βalso show body-fat percentage,β as if that number could be derived from the same two inputs with enough decimal places. One widely reused adult prediction formula comes from Deurenberg, Weststrate and Seidell, published in the British Journal of Nutrition in 1991:
// Deurenberg, Weststrate & Seidell, 1991
// sex: 1 = male, 0 = female
function deurenbergBodyFatPercent(bmi, ageYears, sex) {
return 1.20 * bmi + 0.23 * ageYears - 10.8 * sex - 5.4;
}
Body Visualizer documents this formula on its homepage and is explicit about an implementation choice: the 3D preview assumes age 30 when it shows the estimate, and it labels the result as estimated. That kind of label is not decoration. The equation is a population prediction from BMI, age, and a binary sex term. It inherits every limit of BMI and then adds assumptions about age and about the sample the authors used. A DXA scan, a skinfold protocol, or a circumference method can disagree with it, and two people with the same BMI, age, and sex still do not have to store fat in the same places.
If you implement this formula, show the inputs you assumed, including age. Do not let a default of 30 years silently stand in for a user you never asked. And do not style the output to look more precise than a tape measurement you did not take.
Two outputs, one form: arithmetic versus a mesh
A measurement-based 3D body visualizer is easiest to reason about if you split it into two pipelines that share a form.
On the left are the numbers a person types: a female or male reference model, height, weight, optional circumferences, optional body-fat percentage, optional goal values, and a unit system. In the middle are calculations you can unit-test to the last decimal: BMI, waist-to-height ratio, waist-to-hip ratio, and any published prediction formula you have chosen to display. On the right is an estimated silhouette. Publicly, Body Visualizer describes that preview the way a careful graphics feature should be described: it starts from a fixed female or male reference mesh, uses height for overall scale, uses weight for bounded width and depth, and uses extra measurements to refine regional proportions. The mesh is deformed. It is not reconstructed from a photograph or a depth camera, and it cannot observe muscle distribution, posture, bone structure, hydration, or real tissue arrangement.
That last sentence is the one to put next to the canvas, not in a footer nobody reads. A 3D model is persuasive. If you do not say it is a bounded estimate, users will read it as a portrait. The Timesβ Body Labs piece worked because those figures were scans of real people. A browser tool that morphs a generic mesh is doing something more modest, and more useful for scenario comparison: it can hold everything constant except the one measurement you changed.
The main Body Visualizer puts both pipelines on one page: the metrics cards (BMI, estimated body fat, waist-to-height, waist-to-hip) sit under a rotatable preview, and a goal mode lets you enter a second set of values without leaving the page. For circumference-led questions β bust or chest, waist, hips, inseam, shoulders β the body measurement visualizer is the more direct entry point, because those fields are the point of the page rather than an advanced drawer.
What to do if you are building the calculator
A few practical rules follow from the community questions and from the official definitions.
Do not let a category boundary change the avatarβs identity. If BMI goes from 24.9 to 25.1, the arithmetic crossed a screening line. A real body did not jump into a different species. Continuous, bounded deformation is more honest than swapping in an βoverweight mesh.β
Ask for waist when the userβs question is about shape or central mass. The r/Fitness discussion of the Body Labs scans, and NICEβs later public guidance on waist-to-height ratio, both point at the same gap: height and weight do not describe the midsection. You do not need a medical device to add a waist field. You do need repeatable measurement instructions, because a tilted or cinched tape will move the preview more than a real weekly change.
Keep units in one place. Almost every silent BMI bug I have had to debug came from a height in centimeters mixed with a waist in inches, or from a feet-and-inches parser that dropped the inches. Convert at the edges, compute in SI, and show the user the values you actually used.
Test the formulas as formulas. The CDC 5-foot-9 example on the adult BMI categories page is a ready-made golden case: 125 to 168 pounds falls in the healthy-weight screening range, 169 to 202 in overweight, 203 and above in obesity. Imperial wrappers should hit those bands. Metric wrappers should hit the same BMI values.
Label estimates. βBody fat 26.3%β and βbody fat ~26.3% (Deurenberg estimate, assumed age 30)β are not the same product. The second one will get fewer excited screenshots and far better trust over time.
Leave diagnosis out of the component library. CDCβs own language is that BMI does not diagnose body fatness or individual health. Your toast message, color scale, or 3D model should not overrule that. If a result raises concern, the honest next step is a qualified professional and, when composition actually matters, a method designed to measure composition.
What this does not solve
A better visualization still cannot tell you whether a high BMI is mostly muscle, whether a βhealthyβ BMI hides excess fat, or whether a waist change is clinically important for a particular person. It cannot replace DXA, a trained caliper protocol, or a clinical exam. It also cannot settle an appearance comparison someone is making on Reddit or X. Frame size, fat distribution, posture, and the camera lens will always leak out of a two-input form.
What it can do is stop lying by omission. If two people can share a BMI of 25.0 and not share a midsection, the interface should be able to say so β with the ratio, with the tape values, and, if you offer one, with an estimated 3D silhouette that is clearly marked as a model of the numbers, not a model of the person.
Sources
- CDC, Adult BMI Categories, and CDCβs BMI overview stating that BMI does not diagnose body fatness or the health of an individual.
- New York Times, βSame B.M.I., Very Different Beach Bodyβ (7 July 2015), Body Labs scans of six people at 5 ft 9 in and 172 lb, BMI 25.4; and the companion piece βHow Often Is B.M.I. Misleading?β.
- Reddit: r/beginnerfitness, βWhy does overweight people of similar height and weight looks different?β; r/loseit, βWhy do I look so much bigger than other women despite having the same/lower BMI?β; r/Fitness, β3D Body Scans of 6 adult males - each with identical BMI of 25.4β.
- Public X posts searched in mid-November 2026: repeated comparisons of βsame BMI, different look.β I am citing the pattern, not individual appearance judgments.
- NICE, βKeep the size of your waist to less than half of your heightβ; Browning, Hsieh and Ashwell systematic review of waist-to-height ratio and the 0.5 boundary.
- Deurenberg, Weststrate and Seidell, βBody mass index as a measure of body fatness: age- and sex-specific prediction formulas,β British Journal of Nutrition (1991), PubMed 2043597.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.

