Stone to Pounds Converter

Most people who need a pounds figure already know their weight in stone — they see it on UK bathroom scales, hear it from their GP, or find it on a driving licence or passport application. The problem is that apps, gym trackers, airline booking forms, and US-based medical systems almost always ask for pounds, sometimes kilograms, and almost never stone. This converter closes that gap in one step.

The stone-and-pounds format is the part that catches people out. A scale that reads 11 stone 6 is not the same as 11.6 stone. The 6 refers to 6 individual pounds on top of 11 complete stone. Treating 11 stone 6 as 11.6 stone and multiplying by 14 gives the wrong answer by several pounds — enough to matter on a medical BMI calculation or a dietary plan.

This tool handles both formats: enter a decimal stone value for a single-number readout, or use the separate Additional Pounds field to handle the classic stone-and-pounds split. The stone portion and the extra pounds are converted independently and then added together, so neither format requires mental arithmetic on your part.

Use this converter when you know your weight in stone and need to enter it into a system that requires pounds — gym apps, US medical portals, airline passenger weight declarations, or nutritional tracking software. It is also useful when comparing your weight against research studies or health guidelines that publish thresholds in pounds.

The kilogram output makes this converter equally useful when switching between a UK context (stone) and a European or clinical one (kilograms). You get both outputs at once without running a second conversion.

Where this tool is not appropriate: if you need a precise clinical body composition measurement, a scale reading is always more accurate than converting a rounded stone figure. Rounding to the nearest half-stone before converting can introduce an error of up to 3 or 4 pounds — meaningful for clinical purposes. In those contexts, measure directly in the required unit rather than converting.

Mistake 1 — Treating stone-and-pounds as a decimal. Writing 11 stone 6 as 11.6 and multiplying by 14 is the single most common error. The cause is assuming the number after the decimal point represents a fraction of a stone. It does not — it represents whole pounds. The consequence is a pounds figure that is off by several pounds, which matters for BMI, medication dosing, and insurance forms.

Mistake 2 — Ignoring the additional pounds field entirely. If you only enter the stone value and leave Additional Pounds blank, the tool gives you the stone-only conversion. That is correct if your reading genuinely is a round number of stone, but incorrect if your scale showed extra pounds. Always check your source reading before deciding whether the second field applies.

Mistake 3 — Rounding the stone value prematurely. Some people round 11 stone 6 to 12 stone before converting, then wonder why the result looks high. Convert with the precise values first, then round the pounds result if needed. Rounding the input before conversion compounds the error.

The conversion has two stages. First, the stone value is multiplied by 14 — the fixed imperial constant — to get the pounds contribution from whole (or fractional) stone. Second, any additional pounds entered in the second field are added directly, since they are already in pounds. The combined total is the result shown as 160 lb.

Written out: total pounds = (stone × 14) + extra pounds. For the worked example of 11 stone and 6 pounds, that is (11 × 14) + 6 = 160 lb. The stone component alone contributes 154 lb (from 11 stone) lb; the remaining 6 pounds sit on top of that.

The kilogram figure uses the international pound definition: 1 pound equals exactly 0.453592 kg. Multiplying 160 lb by 0.453592 gives 72.57 kg. This figure is exact by definition, not an approximation — the international pound has been defined against the kilogram since 1959.

The formula assumes that your stone reading is a decimal fraction of one stone, not a compound value — a distinction that matters most when building data pipelines that ingest user-entered weight. A field that accepts free-text like '11 st 6 lb' needs parsing logic before conversion; treating the entire string as a float silently truncates the pounds component and produces a systematic undercount. The Additional Pounds field in this tool is the explicit workaround for that ambiguity in a UI context. In a code context, always validate the format before applying the multiplier.